Plex on QNAP TVS-1282T random crashing

Plex Media Server NAS & Devices
1

Server Version#: multiple, latest
Player Version#: multiple

Hi, I’m again having trouble with the plex server crashing on my QNAP 1282T. Last time it was related to UPnP, but that was fixed.

I don’t know how to reproduce it. Sometimes it takes days before it crashes, other times it can happen several times in an hour. One user claims that it happens when he is trying to scrub through the intro of a TV-show, but i couldn’t verify that that is the case.
Every single time it crashes I cannot restart the plex server just by stopping the plex app and starting it again, I have to reboot the whole NAS. I have one Tautulli instance on my internal network and one running on AWS, both fail to report that the server is down so I suppose the service is still listening even though you can’t use it, same with uptimerobot checking myip:32400.

Any help would be very appriciated!

Attached are the logs, last crash happened 15 minutes ago, at least that’s when I noticed that it was down.Plex Media Server Logs_2018-11-01_15-36-28.zip (4.1 MB)

2

PMS did not crash.
QTS lost networking.

Were you changing your Network settings at the time?

Nov 01, 2018 15:28:00.328 [0x7f97bc7ff700] DEBUG - HTTP requesting PUT https://plex.tv/devices/93e5144ce3d5afe3f81b6cb5e4cc2cf309f78a2a?httpsEnabled=1&httpsRequired=0&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Nov 01, 2018 15:28:00.328 [0x7f97bc7ff700] ERROR - Error issuing curl_easy_perform(handle): 6
Nov 01, 2018 15:28:00.328 [0x7f97bc7ff700] WARN - HTTP error requesting PUT https://plex.tv/devices/93e5144ce3d5afe3f81b6cb5e4cc2cf309f78a2a?httpsEnabled=1&httpsRequired=0&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (0, No error) (Couldn't resolve host 'plex.tv')
Nov 01, 2018 15:28:00.329 [0x7f97bc7ff700] WARN - MyPlex: Updating device connections failed, retrying in 20 seconds.
Nov 01, 2018 15:28:01.971 [0x7f97cc3ff700] WARN - NetworkServiceBrowser: Error sending out discover packet from 192.168.0.105 to 239.255.255.250: Invalid argument
Nov 01, 2018 15:28:01.971 [0x7f97cc3ff700] WARN - NetworkServiceBrowser: Error sending out discover packet from 10.0.5.1 to 239.255.255.250: Invalid argument
Nov 01, 2018 15:28:01.971 [0x7f97cc3ff700] WARN - NetworkServiceBrowser: Error sending out discover packet from 10.0.3.1 to 239.255.255.250: Invalid argument
Nov 01, 2018 15:28:01.971 [0x7f97cc3ff700] WARN - NetworkServiceBrowser: Error sending out discover packet from 169.254.7.65 to 239.255.255.250: Invalid argument
Nov 01, 2018 15:28:04.000 [0x7f97c8223700] WARN - NetworkServiceBrowser: Error sending out discover packet from 192.168.0.105 to 192.168.0.255: Invalid argument
Nov 01, 2018 15:28:04.000 [0x7f97c8223700] WARN - NetworkServiceBrowser: Error sending out discover packet from 10.0.5.1 to 10.0.5.255: Invalid argument
Nov 01, 2018 15:28:04.000 [0x7f97c8223700] WARN - NetworkServiceBrowser: Error sending out discover packet from 10.0.3.1 to 10.0.3.255: Invalid argument
Nov 01, 2018 15:28:04.000 [0x7f97c8223700] WARN - NetworkServiceBrowser: Error sending out discover packet from 169.254.7.65 to 169.254.255.255: Invalid argument
Nov 01, 2018 15:28:04.031 [0x7f97c9335700] WARN - NetworkServiceBrowser: Error sending out discover packet from 192.168.0.105 to 192.168.0.255: Invalid argument
Nov 01, 2018 15:28:04.031 [0x7f97c9335700] WARN - NetworkServiceBrowser: Error sending out discover packet from 10.0.5.1 to 10.0.5.255: Invalid argument
Nov 01, 2018 15:28:04.031 [0x7f97c9335700] WARN - NetworkServiceBrowser: Error sending out discover packet from 10.0.3.1 to 10.0.3.255: Invalid argument
Nov 01, 2018 15:28:04.031 [0x7f97c9335700] WARN - NetworkServiceBrowser: Error sending out discover packet from 169.254.7.65 to 169.254.255.255: Invalid argument
3

I run several services (home assistant for one) on the NAS and all those services are up and running when the crash happens. I can also log in to the gui without any issues, and I run a PRTG instance which monitors the NAS with ping every minute, and it reports 0% downtime and 0% packet loss when the Plex server was down. No network settings were changed. PRTG runs on a seperate esxi-host not dependant on the NAS of course. Both the host and the NAS are connected to a XS1920-12 switch which I haven’t touched in probably 200 days.

I find it very unlikely that this is network related.

PRTG packet loss monitor last 24 hours (the spike is when I rebooted the NAS):

nas%20ping
nas%20ping1416×353 45.3 KB

Also, the time in the log snip you attached are after I tried to stop / start the plex app on the nas, so they are probably false errors since the nas was rebooting at the time to fix plex. as you can see from the QNAP logs I tried stopping Plex at 15:25 so the crash happend before that

qnap
qnap1353×369 65.1 KB
:

4

As I showed above, the DNS error 6, is 100% network name resolution related.
This error may not have originated on your LAN but with your ISP. (most of us forward DNS lookup to our ISP for final resolution) That failure caused PMS to stop responding.

I do see and recognize you are using Container Station. That’s never been an issue provided the default gateway is so indicated and has DNS resolution.

I also have a 1282T and have not encountered this error before (even with PMS test builds)

As a test, I would like to suggest we back down to a lower version (simply install on top of the current installed one).

Is PMS currently installed on CACHEDEV1 ?

5

Thank you for the reply! You are correct that I am using ISP DNS. Would love to try an older version, I think I’ve had the problem both on current / latest and at least two versions before the one I updated to today.

PMS is installed on CACHEDEV1, yes. Two SSDs in RAID1.

6

PMS 1.13.4 X86_64
https://drive.google.com/open?id=1wx_0bHmagQJo0eGk4HvQbyAjxbxoUOMX

Manual install and presto.

7

Thanks alot for the quick response, I’ll install it now and hopefully things will be more stable :slight_smile:

8

Seems the older version did the trick. Any idea when I can update to a newer version and expect it to work as 1.13.4?

9

No. The root cause must first be identified.

10

OK. If you could give me a reply if / when you find the cause so I can upgrade that would be great. Thanks again :slight_smile:

11

Will do.

1.13.4 will be 100% viable for some time. There may be some minor changes but unless you are on the bleeding edge of new features, I would think 1.13.4 is enough as a daily production driver.

12

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