Server Version#:1.43.0.10162-720010162
Player Version#:
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>
First from the looks of it and doing some reading my DB files are MASSIVE. Not entirely sure what to do here as it is taking up a ton of room on my server. Am i able to delete any of these files or deflate them? I believe the ones with dates are backups, what about the TMP file?
Any help in bringing this DB size down is appreciated. See my image attached for file sizes and names
It will give you info on two methods. Letting Plex clean the database will take many hours during which the server will be running, but not available. Using the shell script may still take a long time, but it will be faster. The tar file (in this post) is configured for DSM 7 systems with Plex installed via Package Center (hence my question above).
Read the info and write back with any questions.
Deleting Backup Datbase Files
The -tmp file is can be deleted. It is possibly a leftover from Plex trying to clean the database (note the date is 09/12/2025).
The files with dates appended are backups and not actively used by Plex. They can be deleted if necessary to free up space.
Before deleting them, suggest you do the following (I’m being a bit paranoid):
Scan a library (generates activity).
Pull the log files (settings → troubleshooting) and unzip.
Look in Plex Media Server.log and the rollovers, .1.log to .5.log, for any ERROR entries that mention the database is corrupt or malformed. You can search for corrupt and malformed.
If you find any such entries, stop, write back, and include the log files.
If there are no such entries, then:
Stop Plex Media Server
Delete the files with dates appended.
Copy the active database files, com.plexapp.plugins.library.db and com.plexapp.plugins.library.blobs.db, to a place outside the Plex Data Folder (so you have a backup)
I installed with the Package Center, however I run manual updates and don’t rely on the package center updates as they are lagging behind.
I deleted a the TMP and a few of the older back ups but have the two most recent still. After downloading and looking at the logs I did find a few mentions of pulse data being corrupt and a mention of a URL being malformed. Logs are attached.
Suggest you temporarily disable Settings > Scheduled Tasks > Backup database every three days. Otherwise Plex will continue to make backups. Re-enable it once the database is debloated.
The log files do not show signs of database corruption. The pulse data error looks like something to do with AAC audio, but that has nothing to do with de-bloating the database.
You’ve two options: De-bloat using the ChuckPa-Deflate script (requires SSH access to NAS) or let Plex clean the database.
There is no way to tell how long it will take to debloat the database. Suggest you pick a day where Plex can be offline for hours, then run the script or manually start the cleaning with WebTools.
Write back with how you would like to proceed, questions, etc.
Sounds good - I will proceed with the ChuckPa-Deflate script. I am familiar with this script in my previous research and actually did attempt to run this, however I stopped the script when trying to fix this previously as i thought it was hanging, but now that I know it may take multiple hours I will go that route. Cheers!
I just checked the tar file. It has paths for a Linux install (like Ubuntu), not for DSM 7. I thought it was set for Synology. I’ll look for a Syno version or modify the paths.
It isn’t urgent - though I do have my server down for maintenance right now having notified my users. Do you have an ETA when it may be ready to use? I am hoping to have these repairs complete by tomorrow afternoon (around 24h from now)
)
Let me know once it is ready and I can be one of the first test subjects.