Plex Server (MacOS) crashing regularly for past few days

General Discussions
1

Hi-

My Plex server (stable for many years) started crashing on February 9th after updating to the latest plexpass version. The crash occurs between 20 minutes and 2 hours after restarting the server.

I reverted to the latest stable release on the public channel, and it seems the stable version is also crashing. To my knowledge, nothing else has changed either on my server or the Tuner I use.

I’ve downloaded my logs, and my server was set to send crash reports. To my untrained eye, I didn’t see anything out of the ordinary.

Happy to send the logs. Any help would be appreciated.

Mike

2

Hello,

Bumping this thread and adding some details. Full server log package attached.

The server continues to regularly crash. I’ve turned on debug and verbose logging, here are a few things I noticed in the logs a few seconds before the crash occurs.

Please help if you can, this is very frustrating.

From Plex Media Server.log:

Feb 14, 2018 02:14:28.877 [0x70000be9d000] DEBUG - Completed: [127.0.0.1:50324] 200 GET /clients (7 live) TLS GZIP 2ms 593 bytes (pipelined: 1)
Feb 14, 2018 02:14:29.096 [0x70000b97f000] DEBUG - Thread: Running async task started by thread 0x70000b879000.
Feb 14, 2018 02:14:29.430 [0x70000c856000] DEBUG - Thread: Running async task started by thread 0x70000b879000.
Feb 14, 2018 02:14:29.739 [0x70000b97f000] DEBUG - Thread: Running async task started by thread 0x70000b879000.
Feb 14, 2018 02:14:29.739 [0x70000be9d000] VERBOSE - WebSocket: processed 1 frame(s)
Feb 14, 2018 02:14:32.052 [0x70000c856000] DEBUG - Thread: Running async task started by thread 0x70000b879000.
Feb 14, 2018 02:14:32.053 [0x70000be9d000] VERBOSE - WebSocket: processed 1 frame(s)
Feb 14, 2018 02:14:33.283 [0x70000bf20000] ERROR - Exception getting remote address: remote_endpoint: Invalid argument
Feb 14, 2018 02:14:33.677 [0x70000bf20000] DEBUG - Job running: ‘/Applications/Plex Media Server.app/Contents/MacOS/CrashUploader’ ‘–directory=/Users/mike/Library/Application Support/Plex Media Server/Crash Reports/1.11.2.4772-3e88ad3ba’ ‘–version=1.11.2.4772-3e88ad3ba’ ‘–platform=darwin-x86_64 (10.13.3)’ ‘–serverUuid=9fa053a65f8a406cc528a5c648fd6e9b2cef708f’ ‘–userId=mike@lamoureux.me’ ‘–url=https://crashreport.plexapp.com’
Feb 14, 2018 02:14:33.683 [0x70000bf20000] VERBOSE - Jobs: Starting child process with pid 40562

From Plex Crash Uploader.log:

Feb 14, 2018 02:14:33.722 [0x700005bf9000] INFO - Crash Uploader - Platform: darwin-x86_64 (10.13.3) ServerUUID: 9fa053a65f8a406cc528a5c648fd6e9b2cef708f UserId: mike@lamoureux.me Version: 1.11.2.4772-3e88ad3ba
Feb 14, 2018 02:14:33.719 [0x7fff9b924340] DEBUG - HTTP requesting POST https://crashreport.plexapp.com
Feb 14, 2018 02:14:34.086 [0x7fff9b924340] DEBUG - HTTP 503 response from POST https://crashreport.plexapp.com

From Plex Media Scanner Deep Analysis.log:
Feb 14, 2018 02:14:56.050 [0x7fff9b924340] DEBUG - Deep Analysis: Saving bitrate analysis
Feb 14, 2018 02:14:56.052 [0x7fff9b924340] DEBUG - Updating part with ID=372895 [/Volumes/video/Movies/Three Billboards Outside Ebbing, Missouri 2017/Three.Billboards.Outside.Ebbing.Missouri.2017.720p.WEB-DL.DD5.1.H264-FGT.mkv]
Feb 14, 2018 02:14:56.053 [0x7fff9b924340] DEBUG - [MI] Closing input file: /Volumes/video/Movies/Three Billboards Outside Ebbing, Missouri 2017/Three.Billboards.Outside.Ebbing.Missouri.2017.720p.WEB-DL.DD5.1.H264-FGT.mkv
Feb 14, 2018 02:14:56.053 [0x7fff9b924340] DEBUG - [FFMPEG] - Statistics: 3888389889 bytes read, 3 seeks

I also noticed that the PMS Plugin Logs/com.plexapp.system.log file continues to have entries after the crash at 2:14am, so perhaps a second process is still running? Also, there are a few critical errors in that log file as well, but do not correspond to the server crash time:

2018-02-14 01:02:31,446 (700008255000) : CRITICAL (agentservice:364) - Exception in update request handler (most recent call last):
File “/Applications/Plex Media Server.app/Contents/Resources/Plug-ins-3e88ad3ba/System.bundle/Contents/Code/agentservice.py”, line 297, in update
version = self.agent_get_version(libraryAgent or identifier, ‘Artist’ if media_type == ‘Album’ else media_type)
File “/Applications/Plex Media Server.app/Contents/Resources/Plug-ins-3e88ad3ba/System.bundle/Contents/Code/agentservice.py”, line 1172, in agent_get_version
for agent in self.agent_info[identifier]:
File “/Applications/Plex Media Server.app/Contents/Resources/Plug-ins-3e88ad3ba/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/code/sandbox.py”, line 108, in
getitem = lambda x, y: x.getitem(y),
KeyError: ‘com.gracenote.onconnect’

3

Hello,

A couple hours later, another crash. I had also updated to the latest beta. I noticed that the forums ask for verbose logging off, so I’m attaching my logs again for this latest crash, which had the setting turned off.

From this log I see:

2018-02-14 12:44:26,152 (7fffb0a83340) : CRITICAL (runtime:709) - Private handlers are no longer supported; couldn’t register <bound method StreamService.token_handler of <streamservice.StreamService object at 0x10ea6efd0>>

and:

Feb 14, 2018 12:44:36.630 [0x700000993000] WARN - [E] web_service_t::get_device_status. get_device_info returned error for device dvb#hdhr#0#273979660

Help is appreciated. Thank you.

Mike

4

I’ve seen this too. I updated about 2 wks ago and it stopped. I don’t know which version had the crashing. Sorry for being unable to help…

5

@mdlamoureux What version of PMS are you on now? Are you still seeing the issue?

6

@“MovieFan.Plex” @OttoKerner

7

PMS 1.11.3.4803 has been stable for the past 24 hours. I’ve had transcoding and direct stream clients, and DVR recordings. I was going to give it another 24 hours before posting back here that this is closed. Other than applying the latest PMS beta, no other changes to my server or library (NAS library on Synology)

8

I have the same problem with the same error via plex.tv
Posted here: https://forums.plex.tv/discussion/310202/plex-crashed-randomly-a-few-times-a-week-on-mac

9

@mdlamoureux said:
Hello,

Bumping this thread and adding some details. Full server log package attached.

The server continues to regularly crash. I’ve turned on debug and verbose logging, here are a few things I noticed in the logs a few seconds before the crash occurs.

Please help if you can, this is very frustrating.

From Plex Media Server.log:

Feb 14, 2018 02:14:28.877 [0x70000be9d000] DEBUG - Completed: [127.0.0.1:50324] 200 GET /clients (7 live) TLS GZIP 2ms 593 bytes (pipelined: 1)
Feb 14, 2018 02:14:29.096 [0x70000b97f000] DEBUG - Thread: Running async task started by thread 0x70000b879000.
Feb 14, 2018 02:14:29.430 [0x70000c856000] DEBUG - Thread: Running async task started by thread 0x70000b879000.
Feb 14, 2018 02:14:29.739 [0x70000b97f000] DEBUG - Thread: Running async task started by thread 0x70000b879000.
Feb 14, 2018 02:14:29.739 [0x70000be9d000] VERBOSE - WebSocket: processed 1 frame(s)
Feb 14, 2018 02:14:32.052 [0x70000c856000] DEBUG - Thread: Running async task started by thread 0x70000b879000.
Feb 14, 2018 02:14:32.053 [0x70000be9d000] VERBOSE - WebSocket: processed 1 frame(s)
Feb 14, 2018 02:14:33.283 [0x70000bf20000] ERROR - Exception getting remote address: remote_endpoint: Invalid argument
Feb 14, 2018 02:14:33.677 [0x70000bf20000] DEBUG - Job running: ‘/Applications/Plex Media Server.app/Contents/MacOS/CrashUploader’ ‘–directory=/Users/mike/Library/Application Support/Plex Media Server/Crash Reports/1.11.2.4772-3e88ad3ba’ ‘–version=1.11.2.4772-3e88ad3ba’ ‘–platform=darwin-x86_64 (10.13.3)’ ‘–serverUuid=9fa053a65f8a406cc528a5c648fd6e9b2cef708f’ ‘–userId=mike@lamoureux.me’ ‘–url=https://crashreport.plexapp.com’
Feb 14, 2018 02:14:33.683 [0x70000bf20000] VERBOSE - Jobs: Starting child process with pid 40562

From Plex Crash Uploader.log:

Feb 14, 2018 02:14:33.722 [0x700005bf9000] INFO - Crash Uploader - Platform: darwin-x86_64 (10.13.3) ServerUUID: 9fa053a65f8a406cc528a5c648fd6e9b2cef708f UserId: mike@lamoureux.me Version: 1.11.2.4772-3e88ad3ba
Feb 14, 2018 02:14:33.719 [0x7fff9b924340] DEBUG - HTTP requesting POST https://crashreport.plexapp.com
Feb 14, 2018 02:14:34.086 [0x7fff9b924340] DEBUG - HTTP 503 response from POST https://crashreport.plexapp.com

Managed to find crash reports from your server. There was one on 1.11.3.4803 and more on earlier versions
Is it still crashing?
It is an exception that is not being allowed for and treated as an error and resulting in a crash
I will refer it to the development team to stop the crash and handle the error without crashing

The subsequent crash uploader log after the above which got a 503 error would have retried the upload of the crash report and would have got a crash report identifier - it is always important to match an actual crash to the logs and the crashes I looked at are for other times for which I have no logs

If it is still crashing please restart the server and download the logs and attach the full zip

10

I found the later crash uploader log in the subsequent zipped logs you provided

There was an invalid packet received which caused the crash. This has been referred to the development team to stop the crashes

11

Ok, the behavior was happening frequently but has now stopped. I’ve been stable for a few days now with no changes on my side made.