Server unavailable/Service still running

Server:
OS: Debian GNU/Linux 10 (buster) x86_64
Kernel: 4.19.0-16-amd64
Uptime: 23 hours, 20 mins
CPU: AMD Ryzen 7 2700X (16) @ 3.700GHz
GPU: NVIDIA NVIDIA Corporation GP106GL
Memory: 2337MiB / 32156MiB

Server Version#: 1.22.3.4392
Player Version#: 4.56.4

In the last 23 hours My server has shown the server unavailable or the server can’t connect securely. when I check the service status, it shows PMS as active and running. When I check htop, I can see PMS PID’s moving to the top of the CPU usage is selected. I have also looked through the logs and nothing stands out to me .

The weirdest part is to fix it, I mean to put a band-aid on it, is to restart the service. Plex works for a few hours then, all of a sudden, nothing. Then again, nothing out of the ordinary in the logs.

Now I do know, I may very well have missed something in the logs, or I may have something miss configured.

Any suggestions for a starting point would be greatly appreciated.

Thank-you,
Eric

1 Like

Same here. I smell outage.

Did you try the 1.23.0-4438/4459?

And if you are using external clients it can help to clear cache/data within the apps and/or re-link them to the account (afterwards). Not sure why, but it did with me (only showing “recommended” sections e.g. not loading anything else during the time i could reach the plex-instance)

I pull from Plex’s public stable repository and had no idea, until not, there was a newer update available.

I have tried this a couple times now, but will try again.

When I do have this issue, my remote clients seam to not have this issue.

If the server is on your machine,

terminal session: curl http://127.0.0.1:32400/identity confirm it still is ‘claimed’

If claimed, check Preferences.xml and verify ownership info.

If good to here,

  1. Restart server
  2. Wait 2 minutes
  3. Stop
  4. Manually create tar.gz of “Logs” directory
  5. Attach here for review

I confirmed that the server does state it is claimed and that preferences.xml does have my information within it.

I performed the requested steps and have attached the logs for the 2ish minutes.
I did notice, looking at them, that there where quite a few “(6, Couldn’t resolve host name) (Could not resolve host: plex.tv)”

logs.tar.gz (34.8 KB)

Thank you for the logs.

I found the issue immediately.

CURL error 6 = DNS lookup failure.

[chuck@lizum qa.528]$ perror 6
Exit code(6): error "No such device or address"
[chuck@lizum qa.529]$ 

The server can’t resolve names to IP addresses.
Time to check the network configuration.

May 04, 2021 16:27:44.758 [0x7fa2d0ff9700] ERROR - Error parsing XML: Error parsing file.
May 04, 2021 16:27:44.759 [0x7fa2bbfff700] DEBUG - HTTP requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
May 04, 2021 16:27:44.759 [0x7fa2bbfff700] ERROR - Error issuing curl_easy_perform(handle): 6
May 04, 2021 16:27:44.759 [0x7fa2bbfff700] WARN - HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
May 04, 2021 16:27:44.759 [0x7fa2bbfff700] ERROR - Error parsing content.
May 04, 2021 16:27:44.759 [0x7fa2bbfff700] ERROR - Error parsing XML: Error parsing file.
May 04, 2021 16:27:44.759 [0x7fa2ec3a6780] DEBUG - MyPlex: username is erich_7719, login is erich_7719@live.com, home is 1, has pin
May 04, 2021 16:27:44.759 [0x7fa2bbfff700] DEBUG - HTTP requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
May 04, 2021 16:27:44.759 [0x7fa2bbfff700] ERROR - Error issuing curl_easy_perform(handle): 6
May 04, 2021 16:27:44.759 [0x7fa2bbfff700] WARN - HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
May 04, 2021 16:27:44.759 [0x7fa2bbfff700] ERROR - Error parsing content.
May 04, 2021 16:27:44.759 [0x7fa2bbfff700] ERROR - Error parsing XML: Error parsing file.
May 04, 2021 16:27:44.760 [0x7fa2bbfff700] DEBUG - HTTP requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
May 04, 2021 16:27:44.760 [0x7fa2bbfff700] ERROR - Error issuing curl_easy_perform(handle): 6
May 04, 2021 16:27:44.760 [0x7fa2bbfff700] WARN - HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
May 04, 2021 16:27:44.760 [0x7fa2bbfff700] ERROR - Error parsing content.
May 04, 2021 16:27:44.760 [0x7fa2bbfff700] ERROR - Error parsing XML: Error parsing file.

Also cat /etc/hosts

Plex portion of my network
Plex Layout

 cat /etc/hosts 

etc host

 nano /etc/network/interfaces

interfaces

Your mask is wrong. It should be .224.

Is the DNS correct in resolv.conf?

1 Like

Routes, too. You’ve got a lot of interfaces. Is your default route pointing towards the Internet?


Is 127.0.1.1 a systemd thing?

This looks correct since each of these line is for my PFSense machine.

In the host file the 127.0.1.1 must have bead done at setup. I have never edited this file.

In the interface file the enp36s0 is defined, but not in use.

If enp35s0 is supposed to be the default, how would I set/check this?

ip route show

Can the machine make other connections to the Internet?

Does curl http://app.plex.tv work? It should say “Moved Permanently”.

$ip route show
default via 192.168.1.1 dev enp35s0
192.168.1.0/24 dev enp35s0 proto kernel scope link src 192.168.1.6
192.168.88.0/28 dev enp1s0 proto kernel scope link src 192.168.88.3

Apt-get update doesn’t seem to have an issue.
Just tried curl www.google.com there was no apparnt issue getting the webpage.

Yes, curl http://app.plex.tv does show “Moved Permanently”

@CostaHT
Sorry, I miss typed the 10g network is 192.168.88.0/28.

I did double check that all there machines do have the same subnet.

@ChuckPa
Just tried using curl for https://plex.tv/media/providers and received this responce

<?xml version="1.0" encoding="UTF-8"?>
<errors>
  <error code="1001" message="User could not be authenticated" status="401"/>
</errors>

Is this what it should be if a token is not included?

@erich_7719

Yes, that’s because the token was omitted. “401” = permission denied.

But you did receive a response. That confirms a couple good things -

  • DNS worked when you used curl from the command line.
  • Curl could contact plex.tv and got a response.

If you stop Plex, confirm that no Plex processes are running, and then restart Plex … has the situation changed?

Yes stopping the service, all Plex processes do stop.

In the last 19 hours, I have tried accessing the server through Roku and the web app and there have not bean any apparent issues.

Update… It has been 7 days since I’ve had any issues with plex showing it is unavailable and still be running on the server. No setting have been changed in Plex or for the server itself and there fore there is no definitive reason noted for this issue.

Upon closer inspection of system logs, the server was getting it’s DHCP information while it was unable to connect to plex.tv (in post #6)

I will report back if this happens again.
Thank you all, for your time.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.