Docker: Plex updated itself on container restart, throws errors about Preferences.xml

Plex Media Server Desktops & Laptops
,
1

Server Version#:1.41.5.9522-a96edc606

I have a weird one here. My Plex server updated itself on container restart to 1.41.5.9522-a96edc606. Now when it is trying to start, it throws a bunch of errors at the console.

First, it keeps repeating this a number of times

2025-04-09 20:16:24.433558+00:00 /config/Library/Application Support/Plex Media Server/Preferences.xml:2.1398: Attribute MachineIdentifier redefined
2025-04-09 20:16:24.433576+00:00 VCEncodingMode="always" MachineIdentifier="d394b0e4-a28e-4ee3-8da0-35dfe2751113"

Then it does this:

2025-04-09 20:16:24.449309+00:00 Attempting to obtain server token from claim token
[...]
025-04-09 20:16:31.349414+00:00 PlexMediaServer install: Custom environment detected.  Skipping postinstallation tasks. Continuing.
2025-04-09 20:16:31.382605+00:00 [cont-init.d] 50-plex-update: exited 0.
2025-04-09 20:16:31.383132+00:00 [cont-init.d] done.
2025-04-09 20:16:31.383610+00:00 [services.d] starting services
2025-04-09 20:16:31.387791+00:00 Starting Plex Media Server.
2025-04-09 20:16:31.387833+00:00 [services.d] done.
2025-04-09 20:16:31.414882+00:00 Failed to load preferences at /config/Library/Application Support/Plex Media Server/Preferences.xml
2025-04-09 20:16:33.415529+00:00 Failed to load preferences at /config/Library/Application Support/Plex Media Server/Preferences.xml

The only thing that I did was restart the container, nothing else changed, never touched the config in weeks.

Is there some kind of bug in the current update?

Thanks!

2

I just restarted my beta test server and it was fine.

Critical: libusb_init failed
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
s6-svwait: fatal: timed out
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
[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... 
[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... 
Attempting to upgrade to: 1.41.6.9685-d301f511a
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

 60 78.2M   60 47.7M    0     0  35.1M      0  0:00:02  0:00:01  0:00:01 35.1M
100 78.2M  100 78.2M    0     0  45.5M      0  0:00:01  0:00:01 --:--:-- 85.2M
(Reading database ... 10002 files and directories currently installed.)
Preparing to unpack /tmp/plexmediaserver.deb ...
PlexMediaServer install: Pre-installation Validation.
PlexMediaServer install: Custom environment detected.  Skipping preinstallation validation.
Unpacking plexmediaserver (1.41.6.9685-d301f511a) over (1.41.6.9606-aa6577194) ...
Setting up plexmediaserver (1.41.6.9685-d301f511a) ...
PlexMediaServer install: Custom environment detected.  Skipping postinstallation tasks. Continuing.
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting Plex Media Server.
Critical: libusb_init failed

Spitballing, but check the permissions on your preferences file?

3

They seem fine, but I never touch anything inside the container, so why would they be off? It can read the file just fine, it complains about its contents (something about ā€œAttribute MachineIdentifier redefinedā€)

4

ĀÆ\_(惄)_/ĀÆ I donā€™t know, sorry, hopefully someone comes along and helps, but I donā€™t think the update is bugged.

5

Turns out, it was the installer. I restarted the container again today and it updated to a newer version (1.41.6.9685-d301f511a) and it came right up, no more errors. Not sure what happened, but I am happy itā€™s working now :slight_smile:

2 Likes
6

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