Plex Server constantly freezes after update from Ubuntu 16.04 to 18.04

Plex Media Server Desktops & Laptops
1

Server Version#: 1.14.0.5465
Player Version#:

Last week I updated the computer which hosts my plex media server from Ubuntu 16.04 to 18.04. This happened to coincide with the release of the new Samsung TV UI. Performance was horrible. I couldn’t watch a show for more than 2 minutes without what I thought was the TV app freezing. The only way to fix it would be to log into the server and through a terminal, kill the process and restart the service. Well, the TV App was rolled back and the performance issues remain, but now I also see they are not limited to the one playback device. Even if I play a video locally on the server, it will cause a freeze which requires me to kill the plex process and restart the service. How can I track down what is causing the server issues?

2

The best way to start (really only way to start) is by

  1. Verify DEBUG logging is enabled in Settings - Server - General, VERBOSE logging is disabled
  2. Restart PMS
  3. Recreate the failure
  4. Wait 30 seconds after stopping playback / the freeze to collect the logs (Settings - Server - Troubleshooting - Download Logs).
    a. If PMS itself has frozen, restart it then collect the logs immediately.
  5. Attach the ZIP file here so we can inspect it
3

Plex Media Server Logs_2018-11-13_20-35-06.zip (3.5 MB)

This was created right after a freeze. I was watching a recording on my tv. When it ended, the tv app could no longer see the plex server. Went to the server and found that the plex service had frozen. I needed to kill the process and restart it.

4

Another interesting tidbit. Though I finished watching the whole recording, the restarted server thinks I only watched 15 minutes of a 45 minute long program.

5

Thanks… that is a great capture of PMS not responding.

If you look at the Plex Media Server logs… you see the Auth without anything else

Request: without Completed: is another sign.

6

I chatted with the expert in this.

Next time it hangs, Please force the core dump termination when you kill it (kill -15 ) (SEGV)
PMS will trap that kill signal and generate a crash dump.
When it restarts, it will upload.

We only need the cash dump report (in the “Crash Dumps” directory under PMS) to track it for you.

7

further to what @ChuckPa said, we would also need the connections list at the time of the deadlock.

See Diagnostics for Deadlocks on NAS/Linux in this post for details of what is needed

  • connections list and noting down the time, a process dump invoked via kill -segv <pid> and the logs taken after resarting the server and the crash report for the process dump uploaded
8

36d1e507-0fb3-86dd-11c4fcff-69d53e18.dmp.zip (88.1 KB)
Plex Media Server Logs_2018-11-14_10-52-13.zip (2.4 MB)

1 192.168.86.5:51606 - Handling - GET /:/timeline?ratingKey=260724&key=%2Flibrary%2Fmetadata%2F260724&playbackTime=314461&playQueueItemID=31445&state=playing&hasMDE=1&time=2935000&duration=3599000 (Chrome) 2 ??? - Uninitialized 3 ??? - Uninitialized 4 127.0.0.1:35112 - Responding - PUT /video/:/transcode/session/mi007tgta4kp5vlwpcjl8l49/7cd17cdd-0023-400c-8a79-b9ea3789e9da/progress?progress=83.8&size=-22&remaining=-1&vdec_packets=9981&vdec_sw_ok=9946&speed=1.4&vdec_hw_status=0 - Range: 0 - 0 5 192.168.86.5:51586 - Responding - GET /video/:/transcode/universal/dash/mi007tgta4kp5vlwpcjl8l49/0/2954.m4s 6 192.168.86.5:51628 - Handling - GET /connections 7 127.0.0.1:35134 - Handling - PUT /video/:/transcode/session/mi007tgta4kp5vlwpcjl8l49/7cd17cdd-0023-400c-8a79-b9ea3789e9da/progress?progress=83.8&size=-22&remaining=-1&vdec_packets=9981&vdec_sw_ok=9946&speed=1.4&vdec_hw_status=0 - Range: 0 - 0 8 192.168.86.5:50420 - Responding - GET /:/websockets/notifications 9 127.0.0.1:35116 - Handling - POST /video/:/transcode/session/mi007tgta4kp5vlwpcjl8l49/7cd17cdd-0023-400c-8a79-b9ea3789e9da/manifest 10 192.168.86.5:51638 - Pending Request 11 192.168.86.5:51630 - Pending Request 12 192.168.86.5:51498 - Responding - GET /:/timeline?ratingKey=260724&key=%2Flibrary%2Fmetadata%2F260724&playbackTime=294403&playQueueItemID=31445&state=playing&hasMDE=1&time=2915000&duration=3599000 (Chrome) 13 192.168.86.5:51610 - Handling - GET /:/timeline?ratingKey=260724&key=%2Flibrary%2Fmetadata%2F260724&playbackTime=324470&playQueueItemID=31445&state=playing&hasMDE=1&time=2945000&duration=3599000 (Chrome) 14 192.168.86.5:51596 - Handling - GET /:/timeline?ratingKey=260724&key=%2Flibrary%2Fmetadata%2F260724&playbackTime=304418&playQueueItemID=31445&state=playing&hasMDE=1&time=2925000&duration=3599000 (Chrome) 15 192.168.86.5:51578 - Handling - GET /:/timeline?ratingKey=260724&key=%2Flibrary%2Fmetadata%2F260724&playbackTime=304418&playQueueItemID=31445&state=playing&hasMDE=1&time=2925000&duration=3599000 (Chrome) 16 127.0.0.1:33876 - Finished 17 127.0.0.1:52374 - Pending Request

9

what time was the /connections request made?
what time was the kill -SEGV pid done?
I need the dmp file to be automatically uploaded so it gets processed and analyzed
could you place it back in the relevant folder
/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.14.0.5465-425e4ac90
and restart the server so it gets processed please
and then get the logs to show the crash report upload happening

Thanks

10

Connections request made at 3:11:11
connections.txt.zip (3.9 KB)

Kill command at 3:12:21

Log dump at 3:13:03
Plex Media Server Logs_2018-11-14_15-13-03.zip (3.7 MB)

11

Also having these issues with update to Version 1.14.0.5465. Performed update today around noon and unable to really use Plex on any of my 4 Rokus since. Can this be rolled back?

12

Thank you. Diagnostics good. I have located the analyzed crash report.
The deadlock is being referred to the development team

13

Logs please plus details of symptom and at what time.

See https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/

14

I notice most of the requests are from (TV UN65KS800D) on 192.168.86,189 - can you tell what version of the Plex App and if it is the same version as you mentioned in your first post above

15

The Plex app version for the Samsung TV is 3.3.4

16

That version was reported before as causing server deadlock
See posts starting here

I need to establish if the behavior is the same

18

@1dermutt

The deadlock fix that got released today in beta 1.14.0.5468 unfortunately does not appear to fix the deadlock you have.

I would still recommend that you upgrade to it.

The process dump you provided appears to have been invoked after a shutdown attempt. So I am waiting for fresh deadlock diagnostics - but best to get it with version 1.14.0.5468

Release Notice Plex Media Server

19

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

20

@1dermutt Wondering if this is still happening or if the fix that went out fixed this as well

could you let me know please - and also if you have tried 1.15.1 yet