Docker server upgrade. Plex server crashing on 1.42.1.10054-f333bdaa8

Plex Media Server
1

Server Version#: 1.42.1.10054-f333bdaa8
Player Version#: any

Hi. I got the usual update notification in the UI, restarted the server as usual, and now Plex won’t start up. Docker log entries below, but the specific log file referenced doesn’t actually exist (nothing 1.42.xxx). The last logs are from ‘1.41.9.9961-46083195d’. I guess that’s what I just tried to update - I didn’t pay much attention since this never caused issues over countless updates over many years. The file system seems fine and other docker containers appear to operate nominal.

- Does anyone else have this issue?

- Does anyone know how to fix?

- How can I roll back?

Docker log output (please note the referenced log file does not exist):

2025-08-10T17:59:00.938540052Z libc++abi: terminating with uncaught exception of type soci::soci_error: sqlite3_statement_backend::prepare: disk I/O error for SQL: PRAGMA cache_size=2048

2025-08-10T17:59:00.942233986Z ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.42.1.10054-f333bdaa8/PLEX MEDIA SERVER/f4cff5d5-3f36-45e7-30d7a693-b08eb1da.dmp

Thank you.

2

I really believe some upgrades within their containers has caused this and other regressions [1]. Try downgrading for now, as I have and it was ok for now.

[1] Custom domain ssl does not work after update to server version 1.42.1.10054-f333bdaa8

3

It’s a good idea about PUID and GUID and would explain issues accessing the db or writing logs.

But how can I roll this back? The upgrade is not the normal process of deploying a new docker image, but just restarting the Plex server container with the existing image, which seems to trigger a download of new binaries…?

4

You can do this using the Docker image tags. So rather than using plexinc/pms-docker or plexinc/pms-docker:latest you can specify the version number such as plexinc/pms-docker:1.41.6.9685-d301f511a.

If you’re using a third party Docker image (e.g. linuxserver/plex) then you’ll need to refer to the documentation specific to the image.

5

The damage was already done. The old version could no longer start without restoring the permissions manually.

7

Thanks, I rolled back. Unfortunately it’s still crashing with the same message. I’ll have a look at PUID/GUID next…

-

Alright, I’m back up. A docker log file had grown to almost 100gb with all the alerts etc and the system simply ran out of disk space. Plex is back up.

Thanks for any help!

8

Plex docker doesn’t works yet (1.42.1.10060) transcoding messages with errors; downgrading to 1.41.6.9685-d301f511a works perfectly.

9

If you are seeing failures please provide the entire zip of your PMS logs.

10

I think i may know what the issue is but i’d like to verify by at least one affected user sharing what they are setting their UID/GID to

11 
Sure:

  - PUID=1111
  - PGID=1111
12

I put together an image which I hope fixes the errors. can anyone still having issues with docker please try plexinc/pms-docker:plex-user-test?

1 Like
13

It works! no transcoding problems.

14

Anyone willing to give a second confirmation?

15

Sorry, using linuxserver/plex and believe the docker config isn’t compatible.

16

I’m using:

  • PUID=1000
  • PGID=1000

plexinc/pms-docker:latest didn’t let me scan my library, it showed me the hard drives I had mapped, but not the folders within it. Couldn’t transcode or play movies either as it couldn’t find the files.

I tested plexinc/pms-docker:plex-user-test and the folders are back now. Scanning library works, transcoding works, playing movies works, everything works now as it did with 1.41.6.9685-d301f511a. Thank you for your hard work. :heart_hands:

17

@beluga the resolution will need to be on linuxserver/plex then, we appear to have fixed it on our image but have no control over theirs

18

Yeah, I know. Not sure why I didn’t end up on the official image and one of these days I’ll migrate :slight_smile:

19

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