Server won't start with "Error starting framework core for /usr/lib/plexmediaserver/Resources/..."

Plex Media Server
,
1

Server Version#: plexinc/pms-docker:1.42.2.10156-f737b826c

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 40-plex-first-run: executing... 
Plex Media Server first run setup complete
[cont-init.d] 40-plex-first-run: exited 0.
[cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing... 
[cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0.
[cont-init.d] 50-plex-update: executing... 
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting Plex Media Server.
[services.d] done.
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.42.2.10156-f737b826c/PLEX MEDIA SERVER/fba4a14d-2abf-472f-e1d03b9e-676b7007.dmp
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-f737b826c/PlexMovie.bundle.
Starting Plex Media Server.
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.42.2.10156-f737b826c/PLEX MEDIA SERVER/b77c8197-c35e-49ce-d0abf08a-a814491e.dmp
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
Error starting framework core for /usr/lib/plexmediaserver/Resources/Plug-ins-f737b826c/PlexMovie.bundle.
..........

Haven’t changed anything, and this randomly started happening overnight. Removed and recreated the container, but no luck.

2

3d365e76-2872-40e7-38ac8f89-6960dfd1.log (159.2 KB)

3d365e76-2872-40e7-38ac8f89-6960dfd1.dmp.txt (793.9 KB)

3

Did you copy over your database from the crashed server? If your database became corrupted somehow (power glitch?), then the database is still corrupted.
Is everything updated?

4

In case you didn’t get it fixed, or if you just rebuilt everything from scratch, I wanted to throw this out there. I have run into this issue a handful of times. If you go to the plex ip:port you probably get “Plex Media Server is currently running startup maintenance tasks.”
In your browser, type in “plexIP:Port/web”
This should give an option to “take control” of your server again. I usually run into this when I move the docker in some way. This time, it was when I switched from using a stack to using a script that will stop my docker container, pull the latest updates, and restart the container. Despite it using all the same variables, volumes, etc, it still caused this issue. No harm no foul.