Just updated to the new QNAP PMS. Now it won’t connect to my server at all. Anyone else experiencing the issue? I’ve rebooted my entire QNAP unit, and even reinstalled 1.40.2 over the previous installation, which usually works. I’ve stopped and started it as well. Just nothing.
When I went to open it from the server, it said this:
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=“Plex Media Server is currently running database migrations.”
@ChuckPA I believe you helped me resolve this once before. Eagerly awaiting your much needed assistance!
Are you here to help or make fun of my lack of knowledge on how Plex DBs function? I’ve had this happen before and the maintenance error never went away. I needed to repair the DB, but I had someone help me.
According to the release notes for 1.40.2.8395, “(PLEASE NOTE) Please also be patient when updating to this version if you have a very large database and allow the upgrade process to finish.”
How large is your database? How long did it take to finish?
Thank you @fiftyKnights. Nice to know some people are willing to help. My DB is quite large I believe. I have approx 84TB of storage, and I can only imagine how large the DB is. It’s been about 30 minutes so far, so I guess I’ll just have to wait it out and hope for the best. I fear that it won’t resolve on its own though. I hope I didn’t mess anything up by installing the server twice.
Wow, that’s huge amount of storage! I’ve got about half that and I’m afraid to upgrade to this new version of PMS. Good luck, and please let us know when it finishes.
I’m guessing it may not finish. I’m a noob when it comes to Linux so I’ll have to wait for help or try to do it myself.
99% of the time those small sever updates don’t even need you to read the release notes. Wish there was something additional the devs could’ve done to warn us basic users about the time it would need.
Knowing what you know now, don’t make the same mistake I did. Just leave it. I’ve begun repairing the DB using an old repair dialogue from the other time I corrupted my DB. Coming along ok so far.
Glad you got it restored. I’ve learned the hard way to check the release notes, and maybe wait a week or two before upgrading to a new release. Especially if you see a comment about being patient for database upgrade. Scary stuff…
One thing to check, when do upgrade, if it’s taking Plex server a long time to become available via the web app, is to check if the plex media server process is running and taking lot of CPU. If so, it is doing something. If it’s “sleeping” and still not responding, that’s a bad sign.
Learned my lesson. Luckily this time it wasn’t the hard way. Did that already. Again, appreciate the help. Some dbags just come here to comment and provide no assistance.
While that can sometimes be true, ChristianKent’s comment was my first thought as well.
I HAD just come off of looking at the new release notes, so it was fresh in my mind. If I hadn’t seen it - like you must have missed - I would have been freaking out. What may be worse, is that my docker server is set to automatically check for and install updates on restart. Looking at my server status page is also the ONLY place I know to find release notes. So if my server rebooted for any reason before I saw the notes, I would not have known why it didn’t come up immediately.
In this case, I’d have preferred the server come up just enough to run a web server with a simple note that says “UPDATING DATABASE, DO NOT SHUT ME DOWN” until it finished the database update…
All it does is pointing at the Announcements sub forum, with the number after the last slash in the URL (which normally addresses the post number) being replaced by last.
I was able to resolve it by. doing a server restart and giving it about 30 minutes for my 8TB worth of libraries. I too wish there was more of a warning to wait, and not just the sketchy looking .xml print out.
I don’t even read the notes. I just get the new version and install it. 99% of the time it works immediately. No reason to really check the notes. I learned the hard way.
Just checked the log.
Apr 22, 2024 03:55:31.762 [140231104367416] WARN - Warning: ex: boost::filesystem::last_write_time: No such file or directory [system:2]: “/share/CACHEDEV5_DATA/.qpkg/PlexMediaServer/Resources/Plug-ins-c0dd5a73e”, couldn’t check file: “/share/CACHEDEV5_DATA/.qpkg/PlexMediaServer/Resources/Plug-ins-c0dd5a73e”
