Update to 1.41.7.9799 unstable

Plex Media Server
22

Thanks for the detailed instructions - appreciate it!

I did let DBRepair do its thing and was able to get it up and running again. As of right now everything seems back to normal. Although, my main library database is still sitting at 21GB which may be normal I have a rather large movie, music TV library with previews on etc. Right now just happy it’s back up and running!

23

Is that about normal? Did you compare it to your backup sizes?

24

Here a screen shot of the backups

Screen
Screen1077×505 158 KB

25

Wow, that’s still massive. More than 10x normal size.

26

Yeah, Im not 100% sure the initial one finished. I might run the updated version that just came out and see if it makes any difference!

27

Grab the latest version of DBRepair: GitHub - ChuckPa/DBRepair: Database repair utility for Plex Media Server databases

To pull via command line:

$ wget -O DBRepair.sh https://github.com/ChuckPa/DBRepair/releases/latest/download/DBRepair.sh

I do not know if the Update option will work. The name was changed from “Plex DBRepair” to “DBRepair” which also means a new location at GitHub.

Looking at your db files, it seems the first run did not work for some reason. Notice the backup from May 12 is only 2.01 GB.

If you restore a backup, use the one from 05-15. There is no blobs.db backup for 05-12, and the backups from 05-21 and 05-24 are just as large as the active db.

You can re-run DBRepair with the updated version. It will take just as long as the first time (limited by CPU speed and hard drive read/write speed).

There is another option. If you’ve a faster system - PC, Mac, etc. - you can use it to clean the database files.

  1. Install and claim PMS on a PC/Mac. Do not create libraries. In Settings → Library, disable Empty trash automatically after every scan.
  2. Stop PMS. Toss the (empty) database files and replace them with com.plexapp.plugins.library.db and com.plexapp.plugins.library.blogs.db from the NAS.
  3. If on a Mac, use DBRepair to fix the db. If on a Windows PC, see Library.db size more than doubled in latest version - #186 by FordGuy61.
  4. Once the process is finished, stop PMS and move the db files back to the NAS.

Be sure to stop PMS on the NAS before copying db files to/from the NAS.

28

Running the latest version now - Checks complete with OK says its Performing DB cleanup tasks now so just going to let it do its thing! Thanks

29

@FordGuy61 this time it looks like to finished correctly database is back to 1.79GB from 27GB!

1 Like
30

Good to hear.

Monitor db size for a few days. If the abnormal growth returns, you can fall back to 1.41.6 or earlier until Plex fully resolves the problem (or re-run DBRepair). I’ve not noticed any growth on my server running 1.41.7.9823, but it has not had much traffic either.

Suggest you stop Plex and make a manual copy of the database files as a backup. This gives you a current backup that is not bloated.

You can then delete the other backups and recover the space (no need to keep the bloated backups).

Once Plex makes its own backup (every 3 days), you can delete the manual copy if desired.

31

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