Plex crashes whenever doing Media Optimization

server-unraid

#1

Hey all,

Ever since I moved my server over to unRAID Plex crashes (every time, without fail) whenever I try to optimize media. This is the last log shows the following:

Sep 13, 2017 00:27:27.870 [0x7fa6f53ff700] DEBUG - Relay: cleaning up inactive relay connection to 23.96.218.141
Sep 13, 2017 00:27:28.035 [0x7fa73ba6c840] DEBUG - Shutting down with signal 15
Sep 13, 2017 00:27:28.035 [0x7fa73ba6c840] DEBUG - Ordered to stop server.
Sep 13, 2017 00:27:28.036 [0x7fa73ba6c840] WARN - Timed out waiting for server to finish.
Sep 13, 2017 00:27:28.036 [0x7fa73ba6c840] DEBUG - Stopping server...
Sep 13, 2017 00:27:28.036 [0x7fa7217ff700] DEBUG - MetadataItemClusterRequestHandler: a shutdown event has been received
Sep 13, 2017 00:27:28.036 [0x7fa72d3ff700] DEBUG - JobManager: child process killed by signal: 15 (Terminated)
Sep 13, 2017 00:27:28.036 [0x7fa7217ff700] DEBUG - TranscodeJobManager: [Running] onServerShutdown
Sep 13, 2017 00:27:28.036 [0x7fa7217ff700] DEBUG - TranscodeJobManager: [Running] -> [Shutdown]
Sep 13, 2017 00:27:28.036 [0x7fa7217ff700] DEBUG - TranscodeJobManager: [Shutdown] cancelJob (transcode) c5f01a6a-979f-4609-9443-56b5e85c3b75
Sep 13, 2017 00:27:28.036 [0x7fa7217ff700] DEBUG - Killing job.
Sep 13, 2017 00:27:28.036 [0x7fa7217ff700] DEBUG - Signalling job ID 213 with 9
Sep 13, 2017 00:27:28.036 [0x7fa7217ff700] DEBUG - Job was already killed, not killing again.
Sep 13, 2017 00:27:28.037 [0x7fa7217ff700] DEBUG - Stopping transcode session c5f01a6a-979f-4609-9443-56b5e85c3b75
Sep 13, 2017 00:27:28.037 [0x7fa7217ff700] DEBUG - Cleaning directory for session c5f01a6a-979f-4609-9443-56b5e85c3b75 (/config/Library/Application Support/Plex Media Server/Cache/Transcode/Sessions/plex-transcode-c5f01a6a-979f-4609-9443-56b5e85c3b75-6c2f4143-4e39-451c-a934-418e76bd9c2c)
Sep 13, 2017 00:27:28.055 [0x7fa72d3ff700] DEBUG - JobManager: child process killed by signal: 9 (Killed)
Sep 13, 2017 00:27:28.055 [0x7fa715a3b700] DEBUG - Jobs: '/usr/lib/plexmediaserver/Plex Transcoder' exit code for process 213 is -9
Sep 13, 2017 00:27:28.365 [0x7fa7227ff700] DEBUG - Plex Tuner Service exited.
Sep 13, 2017 00:27:28.466 [0x7fa7227ff700] DEBUG - JobRunner: exec of /usr/lib/plexmediaserver/Plex Tuner Service cancelled. In shutdown state.
Sep 13, 2017 00:27:28.466 [0x7fa7227ff700] ERROR - Plex Tuner Service failed to start
Sep 13, 2017 00:27:29.037 [0x7fa73ba6c840] WARN - Timed out waiting for server to finish.
Sep 13, 2017 00:27:29.037 [0x7fa73ba6c840] DEBUG - Server stopped.
Sep 13, 2017 00:27:29.037 [0x7fa73ba6c840] DEBUG - NetworkService: Stopping advertisement.
Sep 13, 2017 00:27:29.037 [0x7fa7247ff700] ERROR - Network Service: Error in advertiser handle read: 125 (Operation canceled) socket=70
Sep 13, 2017 00:27:29.137 [0x7fa7247ff700] INFO - Network Service: Abandoning advertise socket, it was closed.
Sep 13, 2017 00:27:30.256 [0x7fa72d3ff700] ERROR - JobManager: child process returned: 255 (Unknown error 255)
Sep 13, 2017 00:27:30.256 [0x7fa72d3ff700] DEBUG - Jobs: '/usr/lib/plexmediaserver/Plex Transcoder' exit code for process 289 is 255

Server specs are as following:
AMD FX 8350
16GB of 1866mhz memory
750w PSU

This issues never occurred when I ran PMS on Windows, so I'm not sure why a new OS would cause this. Any help would be much appreciated!


#2

Without seeing the rest of your logs it is impossible to say what's happening but from what you posted above, PMS is being commanded to shut down by something in the OS.

Sep 13, 2017 00:27:28.035 [0x7fa73ba6c840] DEBUG - Shutting down with signal 15
Sep 13, 2017 00:27:28.035 [0x7fa73ba6c840] DEBUG - Ordered to stop server.

#3

@ChuckPA said:
Without seeing the rest of your logs it is impossible to say what's happening but from what you posted above, PMS is being commanded to shut down by something in the OS.

Which log would specifically be the most help?


#4

If you can capture your logs right after it shuts down (because log files roll over quickly), Settings - Server - Help - Download Logs will give you the ZIP file I need to see.


#5

Sorry for the late response -

It just crashed again and when I restarted it I downloaded the logs and I have uploaded them to Google Drive for you to view. https://drive.google.com/file/d/0Bzn5J8Plx1-kT3UwdW4xdGswUGc/view?usp=sharing

If there is another way for me to share them that would be easier please let me know!

Thanks


#6

Thank you for the log files.

I see two things.

  1. I see the 500 errors
  2. I also see '4k' media AFTER optimation being played? I didn't know television episodes are available in 4K (what PMS thinks it has).
  3. I see a number of attempts to play episodes back to back 11, 12, 13, etc. Is this correct?

I have asked another team member to join in and share his thoughts.


#7

I've followed up with my team member.

He agrees you are experiencing the deadlock problem which was fixed in PMS 1.9.0.

We would like you to update to PMS 1.9.0.


#8

Yes, I do have TV episodes in 4k. What I was doing I was optimizing my 4k TV episodes into a 20 Mb/s 1080p file to make trans-coding for remote users easier on my CPU. That would explain the logs saying episodes are being "played' back to back.

Now onto the silly question - I don't actually know how to manually install docker containers. I use a plugin called Community Applications to install the PMS docker for me, but it doesn't have an option to use Plex Pass versions of PMS. How would I go about doing this?


#9

Setting up docker isn't too difficult IF the docker package for your system is a good one.

I know nothing of Unraid and know very little of Docker so therefore can be of little assistance.

I do recommend you install the official PMS image and not one created by others for Security and Privacy reasons.

The full documentation and how-to is here. https://github.com/plexinc/pms-docker


#10

Thanks for all of your help, I really appreciate it!