I recently updated my server version from 1.41.0.8994 to Server Version#:1.41.6.9685 using app central on my ASUSTOR NAS (AS5202T 2 bay). Plex media server will no longer launch and I get the error:
Response code=“503” title=“Maintenance” status=“Plex Media Server is currently running startup maintenance tasks.”/
From reading other posts I see that sometimes for a large DB that this can take quite a while as the DB is rebuilt, however it has now been over 24 hours and when I check the activity monitor it shows 0% CPU usage for plex and that the process is sleeping, it has been this way since about 30 minutes after the update.
The App Centre information on plex also still shows the old version code for plex server, but when I try to reinstall it says that it is up to date.
Any help would be greatly appreciated. I installed plex server on my NAS about 3 years ago and have never had any problems. @ChuckPa, I’m reading through the help you gave SGHalliday and I feel like I’m experiencing a similar issue…any chance you could lend a hand?
Your server logs might contain some pointers.
With the Plex Media Server itself being in maintenance mode, you should still be able to access the logs from the Asustor’s file system.
@tom80H I picked up the log and following through from the point of the new install the thing that is jumping out to me is that it is saying it is running 20 DB sessions for migrations, then after a few cycles of messages saying it has captured all 20 sessions I start to see the following message:
INFO - SQLITE3:0x80000001, 17, statement aborts at 60: [select * from metadata_items limit 1] database schema has changed.
I see that message popping up all over the place in the log in areas where it is saying it is running forward migrations.
I’m thinking that there is something wrong with the DB
Not necessarily… that could be simply a test, determining that the data model has changed.
Issues with the database itself should manifest differently (e.g. references to corruption or malformed content).
Hard to tell based on a single line from that log.
Also, if the DB were in maintenance mode and executing tasks, shouldn’t it be showing as active in the activity monitor? And wouldn’t there be associated CPU usage? I don’t hear the drives being accessed, and this is a fairly noisy NAS when plex is running a movie.
I would look for lines in the Plex Media Server.log which are labeled as ERROR - .
DB maintenance doesn’t depend on re-scanning your media… it’s just the database, so you shouldn’t hear major drive activity on your NAS. Usually, this should involve some level of activity of your system (CPU), but there’s not necessarily major peaks.
On to Day 3, still no change in anything. No CPU usage at all on the NAS, and the only thing showing up in the log for the last 3 days is:
DEBUG - [MediaProviderManager/MetadataAgentManager] attempted to online our built-in agents but we’re not yet signed in
This message is every 10 seconds.
I’m wary to try to restart the NAS because if there is something going on with the DB I don’t want it to have to start from scratch. But at this point I have no idea what is going on. Would really appreciate any advice or suggestions.
Not sure if this is related.
The message could hint at some networking problem, preventing your server to connect to Plex’s backend. What DNS server have you set on your NAS or router – using one of Google’s DNS servers (8.8.8.8 or 8.8.4.4) or CloudFlare’s (1.1.1.1) should properly work with the URLs of Plex’s backend.
