Plex error 503 upon newest update

Plex Media Server NAS & Devices
1

Server Version#:1.29.0.6244-7000
Player Version#:unk

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

"<Response code="503" title="Maintenance" status="PMS is currently running startup maintenance tasks."/>"
This popped up in html code when trying to start plex after this latest update. Should I wait over the hour I’ve waited so far?
I restarted the NAS, no luck. Tried to roll back, says I can’t roll back.
Help?
Edit - after an hour and a half, it started. Odd.

2

Have a look at this explanation from another thread:

TL;DR: wait for the server to finish the activities after updating the server version.

3

What if I decided to remove Plex and re-install it? Should I still see the same message?
I thought that by removing it, it would start with a new, empty database, but I keep getting the message when I launch Plex.

I have a pretty extensive library that in the past has taken at least a week to index. Is there anything I can do or do I also need to let it run for days?

Note - No intention to hi-jack the thread. I thought the info could be useful instead of creating yet another thread about this message.

4

Uninstalling the app won’t give you a new/empty library. To achieve that you need to clear the server data directory and (depending on your platform) additional configuration files/records.
https://support.plex.tv/articles/201198426-restart-plex-media-server-setup-from-scratch/

Though as you stated that’s a different topic.

5

@tom80H

Is there a way to tell if the library is indeed being upgraded or how long it may take?
It’s been over 72 hours and I still get the message:

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

6

@Julio_Ortiz

Restart it.

After 72 hours, it’s done. There is caching happening somewhere to make it look this way

7

Restarted - I still get the same message. I will leave it running until tomorrow morning.

Just in case: QNAP TVS-1277-i7 and PlexMediaServer-1.29.1.6276-4a96dd5b1-x86_64.qpkg

8

How many items do you have Indexed?

(3 days isn’t enough? your DB is either a) HUGE or b) damaged )

I have a tool which will help with the DB should we need it

9

Well, I guess you would consider it huge. I have 15 libraries. 6,000+ Movies, 3,200+ TV Episodes, and 1.5M Music files. In the past, if I have to scan libraries, it has taken a week or more to index all of them. 45TB

10

That’s rough.

How versed/comfortable are you at the QNAP SSH command line?

Comfortable enough to upload a file, unzip, and then run via the shell ?

11

Yes, I can certainly do that

12

Seeing the same error message. I added a new library with 0 content by accident but then quickly deleted it, at which point the server stopped working. I installed the newest version again over my existing one. Wondering if I just need to wait for the same thing to happen. Hoping I don’t have to do this from scratch.

I have a large library as well. Over 5K movies and around 600 TV Shows.

Can I restore to a previous version somehow to avoid this?

On QNAP TS-453A running. QTS 5.0.1.2248
Running PMS 1.3.0

13

Engineering has added the

503 - Temporarily Unavailble

message while PMS is upgrading the database at first run of a new version.

This is normal.

It was added because people panicked and deleted without thinking

14

Got it. Thank you. Should I be concerned if my HDDs have stopped running like they’re rebuilding everything (they’re much quieter now since this started) and I’m still getting that message, or will it simply take time? I’d like to check my DB size and try to figure out how long it may take if an estimate is possible.

15

Don’t be worried.

There is one database upgrade which, depending on how much media you have, can take about 15 minutes. (it’s a whopper)

When I get this message on smaller NAS boxes, I’ll hit Control+F5 (force refresh) from time to time to see if it’s done.

16

Well, it wouldnt be an upgrade I believe. I added a new library on my server, then deleted it almost immediately and Plex stopped working. I restarted my NAS and when Plex still wouldn’t work, I reinstalled 1.30 over my existing 1.30 thinking it would fix it. There wouldn’t be an upgrade in this case, right? That was at least an hour ago and I’m still seeing the same message.

Here are my DBs. Largest one is about 2.5GB. Hoping it will be resolved by the end of today. Possible?

Capture
Capture934×355 28.6 KB

17

Your DB’s are really out of whack.

Look at the WAL file. When PMS stops, that is supposed to be committed into the main DB.

I’m going to suggest some cleanup (which PMS can’t do while it’s running)

Here you can see the README online

Here is the tool (shell script tool) with README file included in the tar.gz

18

Thanks. I’m not that versed in Linux but I’ll try and follow this guide. Would the WAL file prevent my Plex from completing the maintenance? It’s still giving me the 503 error as of now. I’m going to stop Plex from running and do these.

19

I’m totally lost. I’m not even sure I put the file in the right place on my server. No idea how to run the command line stuff, even with the instructions. Once I got to #5, I was lost.

I have Putty open and used FileZilla to place the tar.gz file, but that’s about as far as I got. No idea how to extract or even run the thing.

I’m a total noob with Linux.

Can i just delete the WAL file and have my Plex revert back to a previous state or something?

Capture
Capture1261×396 44.4 KB

20

DO NOT delete the WAL . Thats a huge portion of your DB

Check you DMs. I just sent you one