Server Version#:plexinc/pms-docker:1.22.1.4228 on UnRAID
Player Version#:N/A
After installing the above PMS starts but connections are refused to the server and the docker is marked as unhealthy. Rolling back to previous version has same results.
Docker logs as follows;
[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.
When PMS starts, there will be a delay before you can do anything.
There is a database migration occurring which can take several minutes – all dependent on the number of items indexed.
Recommend you watch the CPU utilization. When it returns to fully idle, it will be ready.
Yes. When it didn’t come back up after 5 mins I rolled it back to the prior version, then I updated back to latest after that didn’t work.
I’ll give it a good hour or so and hope for the best before doing anything else. I can see that it’s doing something, so that’s good, and there are no errors to be found in either the PMS or UnRAID logs so hopefully its just chugging along.
What Engineering did was to improve all the internationalization.
I’m sure you’ve all seen reports or even experienced incorrect characters in subtitles or metadata ?
They’ve addressed that by replacing the original mechanism (ages old) and replaced it with a standard “ICU” (International Components for Unicode) library.
Because PMS has no way of knowing what’s in the database, it has to slug through it that one time and clean up anything which might not have been correctly stored.
That’s what caused the delay… One big long database read & update only as necessary.
@ChuckPa thanks for the explanation. Would have been awesome to do this as a scheduled job and keep the old mechanism while people are migrating their DBs.
This is very error prone and I think my database just bit the dust, cause the server won’t start at all anymore.
Fixed it by uninstalling PMS and reinstalling, recreating my library from scratch. yay!