Recently (I think the version I have and the one before it) my server appears to be crashing or stalling somehow. It has just happened again. The logs stop at 20:10, but I noticed it at 21:00. I have kept all the logs, but only uploaded the PMS.log file.
I have suspicion that it happens whenever Plex authentication is down, but that may be my imagination.
A simple stop/start fixes it, but of course I have lost anything that was recording at the time and since the crash/stall
Is this still happening? Your logs closes with a lot of connection failed, probably due to Plex API being down as you already said. But this issue should have been resolved, shouldn’t it?
It last happened yesterday just before I posted. The server seems to freeze and not recover until I manually stop/restart it.
I do have “use Plex without internet” settings set, so this really shouldn’t be happening.
Notice how the logs stop at 20:10? …well I stopped/started at 21:00 so nothing was happening those final 50 mins but the server was “officially” running.
Does it always stall around the same time? Is there any repetitive task running on the Syno? Is it running out of memory? Are any other apps on the syno affected?
I’m not sure if it helps but, I have been having problems with the latest Plex server releases.
I have disconnected my QNAP from the internet logically (not air-gaped).
Whenever I downgrade to my latest stored copy 1.18.2.2058 it works and I can connect, every time for weeks on end. Whenever I attempt to upgrade to any newer version of PMS I always will loose connections on my local network after a period of time between a few hours to a day at most.
Given that it only happens with the newer versions of PMS I assume that it is a design change and it will not be “fixed” by Plex.
As an alternative I did find an article from How to Geek that I will be trying out to see if it helps. I hope it helps.
@MSPMP thanks. I am not sure if it is a new v old version problem. I have implemented the “use without internet” settings a while back but my server still crashes.
Mar 21, 2020 18:50:12.603 [0x7f3157fff700] DEBUG - HTTP requesting GET http://127.0.0.1:37184/:/plugins/com.plexapp.system/messaging/function/X0FnZW50U2VydmljZTpVcGRhdGVJbmZv/Y2VyZWFsMQoxCmxpc3QKMApyMAo_/Y2VyZWFsMQoxOApkaWN0Cmxpc3QKZGljdApsaXN0Cmxpc3QKbGlzdApkaWN0Cmxpc3QKbGlzdApsaXN0CmRpY3QKbGlzdApsaXN0Cmxpc3QKZGljdApsaXN0Cmxpc3QKbGlzdAoyCnMyNwpjb20ucGxleGFwcC5hZ2VudHMuZmFuYXJ0dHZzMTAKaWRlbnRpZmllcnIxCnMxMAphZ2VudF9pbmZvNApyMgpyNgpyMTAKcjE0CjEwCnIzCnMxMQptZWRpYV90eXBlc25zMTIKYWNjZXB0c19mcm9tbnMxNApmYWxsYmFja19hZ2VudHI0CnMxNApjb250cmlidXRlc190b3I1CnM5Cmxhbmd1YWdlc2IxczIwCnBlcnNpc3Rfc3RvcmVkX2ZpbGVzaTAKczcKdmVyc2lvbmIwczE2CnByaW1hcnlfcHJvdmlkZXJiMXM1CnByZWZzczkKRmFuYXJ0LnR2czQKbmFtZTEKczUKTW92aWUyCnMyMwpjb20ucGxleGFwcC5hZ2VudHMuaW1kYnMyOQpjb20ucGxleGFwcC5hZ2VudHMudGhlbW92aWVkYjEKczIKeG4xMApyNwpzMTEKbWVkaWFfdHlwZXNuczEyCmFjY2VwdHNfZnJvbW5zMTQKZmFsbGJhY2tfYWdlbnRyOApzMTQKY29udHJpYnV0ZXNfdG9yOQpzOQpsYW5ndWFnZXNiMXMyMApwZXJzaXN0X3N0b3JlZF9maWxlc2kwCnM3CnZlcnNpb25iMHMxNgpwcmltYXJ5X3Byb3ZpZGVyYjFzNQpwcmVmc3M5CkZhbmFydC50dnM0Cm5hbWUxCnM3ClRWX1Nob3cyCnMyNgpjb20ucGxleGFwcC5hZ2VudHMudGhldHZkYnMyOQpjb20ucGxleGFwcC5hZ2VudHMudGhlbW92aWVkYjEKczIKeG4xMApyMTEKczExCm1lZGlhX3R5cGVzbnMxMgphY2NlcHRzX2Zyb21uczE0CmZhbGxiYWNrX2FnZW50cjEyCnMxNApjb250cmlidXRlc190b3IxMwpzOQpsYW5ndWFnZXNiMXMyMApwZXJzaXN0X3N0b3JlZF9maWxlc2kwCnM3CnZlcnNpb25iMHMxNgpwcmltYXJ5X3Byb3ZpZGVyYjFzNQpwcmVmc3M5CkZhbmFydC50dnM0Cm5hbWUxCnM2CkFydGlzdDEKczI1CmNvbS5wbGV4YXBwLmFnZW50cy5sYXN0Zm0xCnMyCnhuMTAKcjE1CnMxMQptZWRpYV90eXBlc25zMTIKYWNjZXB0c19mcm9tbnMxNApmYWxsYmFja19hZ2VudHIxNgpzMTQKY29udHJpYnV0ZXNfdG9yMTcKczkKbGFuZ3VhZ2VzYjFzMjAKcGVyc2lzdF9zdG9yZWRfZmlsZXNpMApzNwp2ZXJzaW9uYjBzMTYKcHJpbWFyeV9wcm92aWRlcmIxczUKcHJlZnNzOQpGYW5hcnQudHZzNApuYW1lMQpzNQpBbGJ1bTEKczI1CmNvbS5wbGV4YXBwLmFnZW50cy5sYXN0Zm0xCnMyCnhucjAK
Mar 21, 2020 18:50:12.613 [0x7f3155c07700] DEBUG - HTTP 502 response from GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Mar 21, 2020 18:50:12.616 [0x7f3157fff700] DEBUG - HTTP 200 response from GET http://127.0.0.1:37184/:/plugins/com.plexapp.system/messaging/function/X0FnZW50U2VydmljZTpVcGRhdGVJbmZv/Y2VyZWFsMQoxCmxpc3QKMApyMAo_
The other concern here I see immediately are all the ‘pruning’ statements.
It’s running out of space. ( It will delete already played segments to keep the transcoder temp from filling up )
f3a72a37-6ec6-4f92-95ec-8c179938d39d/05407.ts (13 live) Signed-in
Mar 21, 2020 19:20:08.880 [0x7f3116e6b700] DEBUG - Content-Length of /share/CACHEDEV1_DATA/Public/DVR downloads/Transcode/Sessions/plex-transcode-3ebe31d0-b582-43c1-b5d9-aa2b8a4cafd3/media-05407.ts is 246656 (of total: 246656).
Mar 21, 2020 19:20:08.880 [0x7f31579a2700] DEBUG - Completed: [127.0.0.1:54266] 200 GET /livetv/sessions/3ebe31d0-b582-43c1-b5d9-aa2b8a4cafd3/f3a72a37-6ec6-4f92-95ec-8c179938d39d/05407.ts (13 live) 0ms 246656 bytes (pipelined: 830)
Mar 21, 2020 19:20:08.881 [0x7f31579a2700] DEBUG - Removed transcode data consumer, active count 1 => 0
Mar 21, 2020 19:20:09.771 [0x7f3157fff700] DEBUG - Transcoder segment range: 0 - 5408 (5408)
Mar 21, 2020 19:20:09.772 [0x7f3157fff700] DEBUG - Pruning segments older than 7, view offset is 5406.838379, min was 0, max is 5408, last returned is 5407.718556
Mar 21, 2020 19:20:09.776 [0x7f3157fff700] DEBUG - Pruning segment 6
Mar 21, 2020 19:20:09.809 [0x7f3157fff700] DEBUG - Pruning segment 2
Mar 21, 2020 19:20:09.813 [0x7f3157fff700] DEBUG - Pruning segment 4
Mar 21, 2020 19:20:09.843 [0x7f3157fff700] DEBUG - Pruning segment 3
Mar 21, 2020 19:20:09.852 [0x7f3157fff700] DEBUG - Pruning segment 1
Mar 21, 2020 19:20:09.854 [0x7f3157fff700] DEBUG - Pruning segment 0
Mar 21, 2020 19:20:09.861 [0x7f3157fff700] DEBUG - Pruning segment 5
Mar 21, 2020 19:20:09.863 [0x7f3116b7d700] DEBUG - Transcoder segment range: 7 - 5409 (5408)
Mar 21, 2020 19:20:09.863 [0x7f3116e6b700] DEBUG - buildLiveM3U8: min 7 max 5408 ended 0
Mar 21, 2020 19:20:09.866 [0x7f3155919700] DEBUG - Request: [127.0.0.1:35862 (Loopback)] GET /livetv/sessions/3ebe31d0-b582-43c1-b5d9-aa2b8a4cafd3/c58abd93-8e1c-4c2e-b8e8-1929e444f70c/05408.ts (13 live) Signed-in
Mar 21, 2020 19:20:09.866 [0x7f3155919700] DEBUG - Content-Length of /share/CACHEDEV1_DATA/Public/DVR downloads/Transcode/Sessions/plex-transcode-3ebe31d0-b582-43c1-b5d9-aa2b8a4cafd3/media-05408.ts is 174276 (of total: 174276).
Mar 21, 2020 19:20:09.867 [0x7f3157d11700] DEBUG - Completed: [127.0.0.1:35862] 200 GET /livetv/sessions/3ebe31d0-b582-43c1-b5d9-aa2b8a4cafd3/c58abd93-8e1c-4c2e-b8e8-1929e444f70c/05408.ts (13 live) 0ms 174276 bytes (pipelined: 71)
Mar 21, 2020 19:20:09.867 [0x7f3157d11700] DEBUG - Removed transcode data consumer, active count 1 => 0
Mar 21, 2020 19:20:09.886 [0x7f3157fff700] DEBUG - buildLiveM3U8: min 7 max 5408 ended 0
Mar 21, 2020 19:20:09.895 [0x7f3116b7d700] DEBUG - Request: [127.0.0.1:54266 (Loopback)] GET /livetv/sessions/3ebe31d0-b582-43c1-b5d9-aa2b8a4cafd3/f3a72a37-6ec6-4f92-95ec-8c179938d39d/05408.ts (13 live) Signed-in
it’s pruning VERY quickly after being played. This isn’t a good sign.
I’m in the same boat as MSPMP. I’ve been having occasional Plex server “stalls” on my QNAP TS453Be, over the last few releases. The QNAP server itself if functioning but when I try to access the Plex server, it doesn’t respond and no other divices can access it either. I end up having to stop the Plex server and restart it.
I had logging turned off but have turned it on, so next time it stalls, I’ll grab the log.
Create a share, named Transcoding, on a volume which you know has enough space. For me, CACHEDEV2_DATA (the main array) has 30TB free.
Point Plex’s transcoder temp directory to /share/CACHEDEV2_DATA/Transcoding
See how that behaves. If you run out of space there, all kinds of QNAP alarms should go off about the volume being full too.
Make certain to have DEBUG logging enabled with VERBOSE logging disabled.
This way, when it does fail, we’ll have the right type of info in the log files.
Hi@ChuckPa - thanks, but that was what I was already doing.
My transcode temp directory was pointed to a directory in my public share. I did have my QNAP space alarm go off a couple of weeks ago, but it still had 1TB available even then and I since freed up another 1TB (before the crash with the pruning info in the logs).
