Server Version#: 1.24.5.5160
Player Version#: Can’t reach it
I upgraded from 1.24.4.5081 to 1.24.5.5160 and cannot connect to Plex. I am on a QNAP NAS TS-1277 with about 60TB on my Plex. I have systematically updated for 6 years now. Today, the upgrade resulted in no errors and I cannot connect to the server any longer. I stopped and restarted the server with no luck. I downgraded and no luck. I upgraded again and no luck. Any ideas?
Read the release notes on the release page. Plex Media Server - #465 by Ridley
Restore backup of your db with the 1.24.4.5081 version.
@Tiberius_13 thanks for the suggestion. For what ever reason, I had a dirty volume that was not correctly mounted. I did an fsck to repair it. Apparently something forced a dismount leaving the volume “sort of” mounted. I ran the 1.24.5.5160 update again and it upgraded fine. The thing is, it appeared to update fine when the volume was dirty. Now, everything is back and working. Very strange issue, but I believe not related to Plex.
Hi all,
I think I maybe just ran into this issue without knowing it. I just installed PlexMediaServer-1.24.5.5160-19d8ce86f-x86_64.qpkg and the server didn’t come back. I then tried stopping and restarting the server, and now I don’t really know what to do.
Have I interrupted a key process by stopping and restarting? How do I recover from this?
Thanks!
Seems like this is likely the issue:
Oct 20, 2021 09:56:10.782 [0x7f40d67530c8] ERROR - Failed to begin transaction (…/Library/DatabaseMigrations.cpp:181) (tries=1): Cannot begin transaction. database is locked
Any next steps would be greatly appreciated.
Seems like I’ve managed to recover simply by rebooting the NAS. That unlocked the database and allowed the migration, and the server is back up and accessible again.
I upgraded to 1.24.5.5160 last night and left it to run but Plex would not Launch - downgraded to 1.24.4.5081 and still did not work - rebooted and 1.24.4.5081 then worked. Tonight re-tried 1.24.5.5160 and rebooted after install - still no success. There is no mention of needing to reboot in the Version Info or the length of time you should wait for the database to ‘upgrade’. Any help or direction appreciated as I see some of you have got it to work.
Like the other posters it’s finally worked after several QNAP reboots and a couple of File System Checks. Lets hope that’s over for a while as I’m with @vmsman not having many major issues in the past.
Unfortunately I don’t really have more info than you. I think it was somewhere around an hour and 20 minutes from installing 1.24.5.5160 to rebooting the NAS and restoring functionality. The sequence I followed was:
- Upgrade
- After the server didn’t come back, stopping and starting Plex Server in App Center.
- When it still didn’t come back, I came to the support forum and found this thread.
- After finding that entry above in the locked database I concluded that the server wasn’t doing anything anymore. I could see it retry 10 times with a second delay in the logs, and then give up. That gave me the confidence to reboot.
- After rebooting, I took no further action. The server did not come up right away, but the migration did successfully complete without incident after that.
I can tell you that I never rolled back to the previous server iteration. I’m not sure if that has any bearing on things.
The log entries I found in the Plex Media Server log are:
Oct 20, 2021 09:56:09.763 [0x7f40d67530c8] WARN - Waited one whole second for a busy database.
Oct 20, 2021 09:56:10.782 [0x7f40d67530c8] ERROR - Failed to begin transaction (…/Library/DatabaseMigrations.cpp:181) (tries=1): Cannot begin transaction. database is locked
Oct 20, 2021 09:56:12.057 [0x7f40d67530c8] WARN - Waited one whole second for a busy database.
Oct 20, 2021 09:56:13.074 [0x7f40d67530c8] ERROR - Failed to begin transaction (…/Library/DatabaseMigrations.cpp:181) (tries=2): Cannot begin transaction. database is locked
Oct 20, 2021 09:56:14.346 [0x7f40d67530c8] WARN - Waited one whole second for a busy database.
Oct 20, 2021 09:56:15.364 [0x7f40d67530c8] ERROR - Failed to begin transaction (…/Library/DatabaseMigrations.cpp:181) (tries=3): Cannot begin transaction. database is locked
Oct 20, 2021 09:56:16.640 [0x7f40d67530c8] WARN - Waited one whole second for a busy database.
Oct 20, 2021 09:56:17.654 [0x7f40d67530c8] ERROR - Failed to begin transaction (…/Library/DatabaseMigrations.cpp:181) (tries=4): Cannot begin transaction. database is locked
Oct 20, 2021 09:56:18.927 [0x7f40d67530c8] WARN - Waited one whole second for a busy database.
Oct 20, 2021 09:56:19.946 [0x7f40d67530c8] ERROR - Failed to begin transaction (…/Library/DatabaseMigrations.cpp:181) (tries=5): Cannot begin transaction. database is locked
Oct 20, 2021 09:56:21.220 [0x7f40d67530c8] WARN - Waited one whole second for a busy database.
Oct 20, 2021 09:56:22.238 [0x7f40d67530c8] ERROR - Failed to begin transaction (…/Library/DatabaseMigrations.cpp:181) (tries=6): Cannot begin transaction. database is locked
Oct 20, 2021 09:56:23.519 [0x7f40d67530c8] WARN - Waited one whole second for a busy database.
Oct 20, 2021 09:56:24.536 [0x7f40d67530c8] ERROR - Failed to begin transaction (…/Library/DatabaseMigrations.cpp:181) (tries=7): Cannot begin transaction. database is locked
Oct 20, 2021 09:56:25.811 [0x7f40d67530c8] WARN - Waited one whole second for a busy database.
Oct 20, 2021 09:56:26.824 [0x7f40d67530c8] ERROR - Failed to begin transaction (…/Library/DatabaseMigrations.cpp:181) (tries=8): Cannot begin transaction. database is locked
Oct 20, 2021 09:56:28.098 [0x7f40d67530c8] WARN - Waited one whole second for a busy database.
Oct 20, 2021 09:56:29.121 [0x7f40d67530c8] ERROR - Failed to begin transaction (…/Library/DatabaseMigrations.cpp:181) (tries=9): Cannot begin transaction. database is locked
Oct 20, 2021 09:56:30.406 [0x7f40d67530c8] WARN - Waited one whole second for a busy database.
Oct 20, 2021 09:56:31.430 [0x7f40d67530c8] ERROR - Failed to begin transaction (…/Library/DatabaseMigrations.cpp:181) (tries=10): Cannot begin transaction. database is locked
Oct 20, 2021 09:56:31.431 [0x7f40d67530c8] ERROR - Exception thrown during migrations, aborting: Cannot begin transaction. database is locked
I assume when I killed the server initially it had locked the database for the migration, and that wasn’t released until I rebooted the whole box.
Not sure that helps, but that was my experience.
Oh good, @davidtomlinson, glad it came back. Agreed, hopefully this is a one time thing, as I regularly update the server QPKG with no issues at all.
@davidtomlinson yup, all is fine after my QNAP TS-1277 went through an FSCK. It thought the file system was dirty. I did need to reboot after that because my 40+ LXC/LXD containers were in limbo. After the reboot, everything is fine and Plex is rocking and rolling again. Things like this are one reason I do RAID 6 with a hot spare and even replicate my Plex libraries to another NAS via HBS3.
Wouldn’t it be great if we could have “Plex Clusters” with a Plex server that would mirror another in all ways regarding database, users, watched items, meta-data, etc?
1 Like
That was fun… Synology… Initial update failed. Read this forum about locked processes…
Restarted NAS, Stopped Plex, reinstalled and I’m up and running.
@vmsman I have 2 x TVS-1282T3 / 1 x TVS-EC1080. Run Plex from TVS-1282T3 Sync to other 2 boxes in different locations, also Windows (NUC) runs Plex pointing at one of the backup boxes for issues like this (BTW the Windows Box upgraded to latest Plex Version with no issues). I use Syncovery on a Windows PC as it offers greater control than HBS3 (which I also use) to replicate my data.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
