Hi
I switched my plex to :beta (I’m a plexpass user) and now it won’t start, it’s stuck at that message:
<Response code="503" title="Maintenance" status="PMS is currently running startup maintenance tasks."/>
Is there any way I can recover my setup?
Wait.
Plex is performing maintenance tasks such as database schema changes. While that is happening the server will be unavailable.
Ok… but server load is pretty low… doesn’t “feel” likt that’s the case
I’ll give it another hour and post back, thanks for replying
BOOM! it’s back
Cool.
I was updating my Synology based server to see how the migration went.
The server does not have many movies, so the migration took just a couple of minutes, but I did get the same 503 message until migration was complete.
The SQLITE message you circled is normal. The database schema often changes from one PMS version to another, and such messages get logged.
The ones to watch out for are SQLITE ERROR messages. Any of those indicate problems with the database. INFO and WARN are almost never a problem.
FYI, unless you specifically need them, disable verbose log messages in Settings → Server_Name → General. Leave debug, the default, enabled. Verbose adds too much info to the log files. They wrap very quickly and desired information can be lost. Note you will need to restart Plex Media Server after changing the setting. It is not documented, but a few versions back, Plex made a restart necessary when downgrading log levels.
Thank you, yeah I enabled debug becaause I had been facing another issue when I moved to my new server and I kinda forgot.
I’ve had this up for over an hour, how long does it take? I’ve never seen it before my years of having a plex server. I just saw it as soon as I updated to 1.29.0.6219-b1b4d4871 on my qnap tonight. At first I thought it was a loading error which I’ve had in the past so I restarted my server but it’s still showing and has been for over an hour. Should I try rolling it back to a previous version?
According to Qboost Plex is running but there’s 0 cpu usage and the memory says 28.53. When I start plex through qnap desktop this is the text I have on the window instead of plex loading up, it doesn’t even try:
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.”
If I have to delete plex and reload it do I lose my server settings? I have 8TB of files, it will be a nightmare reloading everything.
Checking my qnap system resources it was showing plex as “sleeping” so I tried rolling it back to the previous 1.28.2 version and I have the same thing screen happing with the startup maintenance.
Any advice would be appreciated.
My QNAP PMS is running in this maintenance mode for already 10 hours. Something must be going wrong, I think
In my case all I did is wait, it’s an i5 7th gen nuc and it took 2:23
I had no change after leaving itover night. I ended up having a firmware update this morning on my Qnap and now it works. I did roll it back to the previous 1.28 version though. I turned off the plex pass thing on the site. Not risking the 1.29 until it’s out of beta or whatever. I’ll wait for my plex to alert me.
I confirm that the issue has been resolved by updating to QOS 5.0.1
Odd, but we’re on different platforms so I guess it’s just what it is.
Mine is doing the same thing. Windows Server 2016.
I have an enormous library so this might take a minute. hopefully it will finish and everything will be okay. I will post here and let the community know the outcome.
Update on my upgrade to 1.29.0.6219:
I did the upgrade around 10:30pm last night. It immediately went into the maintenance mode and after waiting for one hour I decided to go to bed. At 8am this morning it was still showing the same thing so I restarted the PMS and now everything is working fine. I’m not sure if the process got hung up or what happened. I have a very large music library (15k songs) but only 500 movies/tv shows/etc. I thought this information might be useful for others.
Also, I am still running the 32 bit version. I will move to 64 bit at some point soon so long as it’s stable.
So after it working fine for 12 days, I got the notification that there was a new official upgrade:
PlexMediaServer-1.29.0.6244-819d3678c-x86_64
And now I’m back in maintenance mode on my Qnap.
Is this business as usual now that we wont have our servers usable for 12 hours? Or is there a time I should restart it? Currently letting it run.
I have around 40 TB of data, I’m not sure if I’m going to update again for a long time if this is going to become a standard practice. I’d really rather not sit here and have to roll versions back and fourth. I never opted to be a part of a test branch for these types of issues.
Currently on a QNAP tvs-x72x with 32 gb of ram and I’ve been sitting on an inactive service for the past two hours. The QNAP dash shows little to no activity from the CPU ( https://i.imgur.com/2WotoBi.png ).
I’ve installed the application from the approved applications store provided by QNAP ( https://i.imgur.com/MwYJhH8.png ) and I pulled version (PlexMediaServer-1.29.0.6244-819d3678c-x86_64.qpkg).
What is the proper process for rolling this update back for QNAP devices?
I left it for a bit and it still showed maintenance in the browser window but when I closed it and reopened it from the Qnap desktop it loaded up. So I’m not sure when in the past 3 hours it completed but it did.
I’m on 1.29 now. The last time this happened I figured it was a crash so I rolled back to 1.28 (I have about a year of qpk updates saved on my hard drive so I just reinstalled the previous working version). I still had the maintenance mode and it eventually cleared after I went to bed.
I’m up and running, which is great. I would still appreciate knowing if this is going to be the new standard since I’m not at home all day and losing a night of plex due to an update is a real broken thumb when it happens.
For what ever it may be worth, a reboot of my QNAP appeared to resolve the issue. Hope you find this helpful.
