Upgrade to latest version breaks server with error 503 PMS Maintenance

Just finished upgrading and now the server is broken, when trying to logon I get the following error:

This XML file does not appear to have any style information associated with it. The document tree is shown below.

Server Version#: PlexMediaServer-1.28.2.6151-914ddd2b3-x86_64
Player Version#:

As stated elsewhere in the forum:

503 means Temporarily unavailable.

The message tells you PMS is performing database maintenance.

As soon as the maintenance is complete, the normal web page will return.

I’m sure Engineering will at some nice polishing to it but for the moment, it at least tells you the database maintenance is running.

Maintenance of this level is when the schema is being updated for the entire database and you can’t open a database while its core structure is changing.

Ok thanks

@ChuckPa How long does it usually take for the maintenance to complete? I have had that page for about a day now.

@pchung777

Which version are you updating from?

How many items are indexed ? (approximate count of movies, episodes, songs, photos)

“Normal” maintenance, from a recent version to the version installed, normally takes less than 5 minutes in most cases when you have 40,000 items indexed and you’re running on a NAS (ARMv8 or Intel Core CPU)

Are you able to manually grab the log files for me? (Do you have the PlexData shared folder previously defined ? )

I’m on version 1.28.2 (whatever the latest is). I am running on a Qnap TS-251, which I think is an Intel Celeron. I probably have close to 50k files, not really sure.

I tried to message you for the log files, but it says you aren’t accepting messages.

@pchung777

I have sent you a PM where you can attach your logs

Hey ChuckPa,

I have exactly the same issue running on a WD Ultra E2. Can you help with that as well ? I have less than 10k files, so should not run for hours, right ? Updating to 1.29.1.6316. from -1.26.1.5798 as the versions after that always gave me problems starting the PMS.

Cheers
Carsten

Upgraded now to 1.29.2.6334 still the same issue. Please !!! I need help. My girls are killing me with PLEX not running
Thanks

Hi again,

after updating to the latest version, at least the PMS is running again. However, my Server is connected but my media is not shown at all. If I execute search new media manually, I can see that it screens through my media. If I select e.g. my movie folder, the PMS throws an “unexpected error occured”.
How can I solve this ?

Thank you for answering asap
Cheers
Carsten

@ChuckPa when you have time, could you consider to help or at least refer me to somebody who could ?
Thanks

@carsten_773

Are you running a WD OS5 machine ?

If you do, I have added WD OS-5 support to my utility which will help you.

1 Like

@carsten_773

I have not published support for WD yet. I would like to confirm it works ok for you before final release

I have a WD MyCloud EX2 Ultra OS5. As written above, after the last update the PMS starts again is connected to my media, but my media is not shown in the UI. Please forward to the WD spcialist that I can get this running again

Thanks a million
Cheers from Germany
Carsten

@ChuckPa Hey Chuck,

nope it did not work for me. However, I deleted the entire library and started from scratch. With just 10k files, that was easier than running a script.

Thanks anyways
Cheers
Carsten

Is there any way to query the status? I’ve been sitting on this for about 18hrs so far on a QNAP. I have an absurd number of items so I’m not surprised by the time. I normally upgrade right away, but when this first started in Oct I rolled it back. So I am going from an Oct version to the latest version (as of 12/15)

EDIT: You can look in the Plex Media Server.log file to watch the migration progress. SSH to the NAS, navigate to the Logs folder in the Plex Data Folder, then tail -f "Plex Media Server.log".


Unfortunately not.

You have to let it run to completion. Depending on the size of the database and the CPU in your system it could take minutes to days.

If you interrupt it, the process will start over from the beginning.

1 Like

Thank you. The log hasn’t moved since it started. Is this expected?
Dec 15, 2022 16:18:21.044 [0x7f6ad03a9b38] DEBUG - [JobRunner] Job running: /share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/CrashUploader "--directory=/share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server/Crash Reports/1.30.0.6486-629d58034" --version=1.30.0.6486-629d58034 --platform=Linux "--platformVersion=QTS 5.0.1.2194" --serverUuid=*** --userId=*** --sentryUrl=https://o17675.ingest.sentry.io/api/1233455/minidump/ --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --vendor=QNAP --model=x86_64 --device=TS-451+ --allowRetries=0 Dec 15, 2022 16:18:21.044 [0x7f6ad03a9b38] DEBUG - [JobRunner] Jobs: Starting child process with pid 9028

Plex Media Server.log hasn’t moved since the 15th. Plex Media Server.1.log does show the 503 responses but nothing else is moving.

The only thing Plex in ps ax is “./Plex Media Server”

Are there any other processes to look for? CPU doesn’t seem to be doing much.
Thanks!

It’s hanging, I recommend you restart your QNAP, and the monitor again

1 Like