Plex Server Crashing on start 1.27.2.59

Server Version#: 1.27.2.59
Player Version#: N/A
Running on Ubuntu 20.04.4 LTS
I just updated my server, was running 1.25.xx
I had an issue where a previous upgrade failed to connect to my media sources, so I just restored from a backup. I decided to again. This time the server crashes on start. I have the dmp crash report, but not sure how to open to best way to upload.

This is the current server status

Jul 28 14:48:24 plexserver systemd[1]: Starting Plex Media Server…
Jul 28 14:48:24 plexserver systemd[1]: Started Plex Media Server.
Jul 28 14:48:28 plexserver Plex Media Server[3399]: libc++abi: terminating with uncaught exception of type std::bad_cast: std::bad_>
Jul 28 14:48:28 plexserver Plex Media Server[3399]: ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /var/lib/plexmediaserve>
Jul 28 14:48:29 plexserver systemd[1]: plexmediaserver.service: Main process exited, code=killed, status=6/ABRT
Jul 28 14:48:29 plexserver Plex Media Server[3515]: Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-a>
Jul 28 14:48:29 plexserver Plex Media Server[3517]: Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-a>
Jul 28 14:48:29 plexserver Plex Media Server[3519]: Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-a>

A backup of what please?

What you’re showing looks like the host itself is still out of sorts.

I was just saying the previous time I tried upgrading Plex, it didn’t work out. Has nothing to do with this current issue. I have full back ups of my virtual server that I restored.
The issue is I upgraded my server from 1.25.8.5663 to 1.27.2.59 but just doing sudo apt upgrade and the plex server fails to run.

Can you provide me the logs ZIP file / tar.gz file of the Logs directory ?

I need something to examine to go further.

logs.tar (3.1 MB)
Here is the log files.

This looks like the PMS installation itself (executables and libraries)
are not running as they should.

Jul 28, 2022 19:53:25.394 [0x7fe2b9517b38] DEBUG - [Req#d5] [com.plexapp.system] HTTP reply status 404, with 0 bytes of content.
Jul 28, 2022 19:53:25.394 [0x7fe2b953ab38] DEBUG - [Req#d7] [com.plexapp.system] HTTP reply status 404, with 0 bytes of content.
Jul 28, 2022 19:53:25.394 [0x7fe2bb26fb38] DEBUG - Completed: [127.0.0.1:56942] 404 GET /:/plugins/com.plexapp.system/resourceHashes (3 live) GZIP 206ms 261 bytes
Jul 28, 2022 19:53:25.394 [0x7fe2bb26fb38] DEBUG - Completed: [127.0.0.1:56936] 404 GET /:/plugins/com.plexapp.system/resourceHashes (3 live) GZIP 287ms 261 bytes
Jul 28, 2022 19:53:25.395 [0x7fe2b9673b38] DEBUG - [JobRunner] Job running: /usr/lib/plexmediaserver/CrashUploader "--directory=/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.27.2.5929-a806c5905" --version=1.27.2.5929-a806c5905 --platform=Linux "--platformVersion=20.04.4 LTS (Focal Fossa)" --serverUuid=6a9117df18450a9a8fc5d90d9317bad912c16b3d --userId=XXXXXXXXX --sentryUrl=https://sentry.io/api/1233455/minidump --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --vendor=Ubuntu --model=x86_64 --device=PC --allowRetries=0

There should be no ‘404’ (not found) errors

Would you consider:

  1. Uninstall the package (keep all the data)
  2. Verify the host is fully up to date with OS updates
  3. Reboot the host as required
  4. Reinstall the package
  5. Retest

If this doesn’t clear up, my next thoughts point to a deep database corruption (where the logs are vaguely indicating)

Just to add to @ChuckPa advice, if these crashes continue to happen when running on the current public release or current beta, we would need to locate the crash dump files - these get copied to $TMPDIR after attempting to upload them - for example on July the 28th, we would have copied a file for a crash named e46973c1-e0a7-4aa9-d1d3d4a7-57855d7a into the temp directory - the path would be where $TMPDIR is set to

So if it happens still, try and look for files copied into $TMPDIR soon after a crash and the debug server logs zip

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