My Plex Server is crashing nightly. Someone Please help

General Discussions
1

Hi There, my plex server is crassly nightly/daily. Im am using the latest version, plex is on its own dedicated mac mini. I have quite a large library but I have been using plex for years I just don’t understand what is going on. I have attached the logs.

2

@jakeclifford said:
Hi There, my plex server is crassly nightly/daily. Im am using the latest version, plex is on its own dedicated mac mini. I have quite a large library but I have been using plex for years I just don’t understand what is going on. I have attached the logs.

Can’;t see any crash but a possible hang

What the logs show that there may have been a hang at about 06 am on Oct 01, 2017
What is logged after that is I presume you trying to shutdown Plex Media Server at 12:40

Oct 01, 2017 06:03:07.983 [0x70000ac01000] VERBOSE - JobManager: child process with PID 2820 exited
Oct 01, 2017 06:03:09.986 [0x70000b2a8000] DEBUG - Stopping file watcher for com.plexapp.agents.thetvdb
Oct 01, 2017 06:03:13.240 [0x70000b1a2000] DEBUG - Stopping file watcher for com.plexapp.agents.localmedia
Oct 01, 2017 06:03:17.998 [0x70000aafb000] DEBUG - Stopping file watcher for com.plexapp.agents.plexthememusic
Oct 01, 2017 06:48:13.544 [0x70000b019000] DEBUG - NetworkServiceBrowser: PLAYER departed after not being seen for 181.987851 seconds: 192.168.0.17

Oct 01, 2017 12:40:37.076 [0x7fffb5c213c0] DEBUG - Shutting down with signal 15
Oct 01, 2017 12:40:37.076 [0x7fffb5c213c0] DEBUG - Ordered to stop server.
Oct 01, 2017 12:40:37.076 [0x70000a7e9000] DEBUG - Stopping server...

If you are getting a hang like the one at 06:00 / 06:48 am - then try and force a process dump rather than just a shutdown

You can do through a terminal session but need to find the PID number of the Plex Media Server app process and then do a
kill -SEGV <pid>
where <pid> is the process number

This should generate a crash report which would get reported after restart of the server.
Please capture the logs zip again after the restart following the forced crash
and also look into any OSX captured diagnostic reports for it in these directories

~/Library/Logs/CrashReporter/
~/Library/Logs/DiagnosticReports/

and zip and also attach

3

yes i guess a hang is more accurate. I will do that when it happens next time and update the logs for you. Thank you Jake