Regarding the latest beta database migration

Plex Media Server Plex Pass Betas
1

Server Version#: plexmediaserver_1.40.2.8312-b1c79904d_amd64

It took almost 30 minutes to complete the migration, and I must say it had me worried for a bit. :slight_smile: Even with the release notes. Maybe having some amount of status visible on the Plex app when connecting/trying to connect to a server going through database migration would be a good thing to have before this version goes public, or at least a much more expressive statement about how long the migration process could take.

I have a huge database… library.blobs.db is 2,363,801,600 bytes and the library.db is 634,833,920 bytes. I don’t think I’ve ever performed an upgrade that ever took a noticeable amount of time once it reported having completed the installation.

I am rather curious about what exactly was going on during the migration this time around though. :slight_smile:

BTW, the only visible info I see is if I try connecting directly to the server port, and that just gives me this text:

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.”

Also I should mention that about 20 minutes in I rebooted the server, and reinstalled the update, then as nothing was responding yet finally came here and hunted around and found I should wait even longer. And I guess I am happy to say the reboot in the middle of the upgrade didn’t matter; probably just started the process over, I guess.

2

I too would love to see some sort of information about the database update time remaining. I spent allot of time trying to fix something that wasn’t broken. I just needed to wait 30 min. I would love to see a method to check the progress from the terminal or have the upgrade not complete until the database is updated. Right now something would be better than thinking something is busted. If there is already a way please share.

3

I left mine overnight, similar size DB files. nothing worked and the server was down. Every time I launched the server it crashed so the migration appears to have failed. Not sure what to do now as I have rolled back to an earlier version and an old DB backup.

I did try once uninstalling and then installing manually, it showed a library migration progress bar but once that completed the server crashed.

4

Based on the new entries in the schema_migrations table of the database, at least part of the migration was adjusting more dates to be epoch based instead of local datetime strings. E.g. instead of “2024-04-02 16:00:00”, it’s now “1712099400” in the database.

1 Like
5

My observations fwiw wrt DB upgrade Stuck on "Server is Starting" upon execution of latest Beta - #5 by edrock200

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.