Latest update causes plexmediaserver.service to segfault on startup

Plex Media Server Desktops & Laptops
1

Server Version#: 1.18.3.2111-5a96726d0

Dec  5 13:57:41 media-server systemd[1]: Started Plex Media Server.
Dec  5 13:57:43 media-server kernel: [ 3935.442391] [UFW BLOCK] IN=ens160 OUT= MAC= SRC=172.16.0.4 DST=239.0.0.250 LEN=289 TOS=0x00 PREC=0x00 TTL=1 ID=16535 DF PROTO=UDP SPT=32414 DPT=32415 LEN=269 
Dec  5 13:57:43 media-server kernel: [ 3935.442657] [UFW BLOCK] IN=ens160 OUT= MAC= SRC=172.16.0.4 DST=239.255.255.250 LEN=289 TOS=0x00 PREC=0x00 TTL=1 ID=11505 DF PROTO=UDP SPT=32410 DPT=32411 LEN=269 
Dec  5 13:57:43 media-server kernel: [ 3935.573466] [UFW BLOCK] IN=ens160 OUT= MAC= SRC=172.16.0.4 DST=239.0.0.250 LEN=298 TOS=0x00 PREC=0x00 TTL=1 ID=16542 DF PROTO=UDP SPT=32414 DPT=32415 LEN=278 
Dec  5 13:57:48 media-server sh[12897]: ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.18.3.2111-5a96726d0/PLEX MEDIA SERVER/363ff956-db2c-a9ba-3c577611-6c2131f6.dmp
Dec  5 13:57:48 media-server kernel: [ 3940.186807] Plex Media Serv[12919]: segfault at 0 ip 0000000000e16df9 sp 00007f2ff37fda90 error 4 in Plex Media Server[94b000+d5a000]
Dec  5 13:57:48 media-server kernel: [ 3940.186813] Code: 00 48 85 c0 74 0d 48 8b 08 48 3b 48 08 0f 84 ec 01 00 00 83 7f 18 00 0f 88 3c 01 00 00 48 8b 47 08 48 8b 40 f0 4c 89 7c 24 30 <4c> 8b 30 48 8b 68 08 4d 85 f6 75 09 48 85 ed 0f 85 26 02 00 00 48
Dec  5 13:57:48 media-server sh[12897]: Segmentation fault (core dumped)

I’ve tried down grading, with no luck.

2

What does journalctl -xe | grep -i plex show?

Also, may I have the logs ZIP and obtain a copy of the crash report file?

3

Not too much:

Dec 05 14:55:07 media-server systemd[1]: Starting Plex Media Server...
-- Subject: Unit plexmediaserver.service has begun start-up
-- Unit plexmediaserver.service has begun starting up.
Dec 05 14:55:07 media-server systemd[1]: Started Plex Media Server.
-- Subject: Unit plexmediaserver.service has finished start-up
-- Unit plexmediaserver.service has finished starting up.
4

I think I have it sorted… cleared out the cache for the fuse file system and it seems to be running well now.

5

I spoke too soon… here’s the log of interest

Dec 05, 2019 15:52:06.159 [0x7f92effff700] WARN - Sync: local sync directory "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Cache/Transcode/Sync+" does not exist
Dec 05, 2019 15:52:07.065 [0x7f93227fc700] WARN - Crash: Crash reporting disabled
6

Does user plex:plex have permission to write to the Cache & its subdirectories?

Did you delete everything under there, including the Transcode tree?
If so, please recreate them and make certain user plex:plex (or user you run it as) has ownership.

The directory tree is created once during initial startup. After this time, it expects it to be there.

7

Yeah, I cleared it, and created the folders. I also did a reinstall through apt, which recreated the content. The crashes are still occurring, however, just without anything in the logs now. How may I submit a crash dump?

8

If you have “Submit Crash Reports to Plex” checked (Settings - Sever - General), they will upload automatically.

Seeing the full logs will tell me a lot. I will be able to see how far it gets.

Also, if you have any customization (override.conf) of the service, knowing the changes shines a great deal of light on it.

9

Is there a manual way to submit? It currently doesnt start to the point I can change that setting. I think ill just need to do a clean install - is there documentation on migrating a plex server? Ideally i’d like to keep the metadata and scan results.

10

I think i managed to get it set to send them… you should get one per minute if so :wink:

11

I still need the logs to know which dump files to pull.
The logs show me the UUID – which is unique for each server.

12

If you still have the .dmp file, I can analyze it myself

13

i have many :slight_smile: How can I securely send it to you?

14

DM sent. Please respond there.

15

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