An old issue from 2 years ago keep coming back, server deadlocks!

This issues here has popped up yet again over the last 2 days.

Have been unable to get a Dump file as for some reason it only creates a 0KB file.
I do have the logs and the connections list
Plex Media Server Logs_2023-09-21_15-50-19.zip (4.7 MB)
connections.txt (86.2 KB)

Currently
Server Version#: 1.32.5.7516

Heres a New batch of Logs and connection list, Plex and the server its on had been restarted and this has happened again after just 5 hours!!

Again I was not able to get a dump file as its keeps creating 0KB empty files, most annoying.
Plex Media Server Logs_2023-09-21_20-56-02.zip (4.6 MB)

Connections.txt (82.0 KB)

Sep 21, 2023 20:55:11.400 [8040] ERROR - [DatabaseFixups] SQLITE3:0x7ff779e23dc0, 11, database corruption at line 84326 of [a29f994989]

The database is corrupt.

You can attempt to repair it or try restoring from a backup.

Repair: See Library Not Updating - #4 by FordGuy61

Restore: Restore a Database Backed Up via ‘Scheduled Tasks’

Would that course the sever to lock up and be stuck with hundreds of open connections?

Yes, and or a thousand other problems. A corrupt database causes a snowball effect with other issues. Fix that, and Ill bet your problem goes away, if not you can repost new logs and further troubleshooting can be performed. But until the database is fixed its pointless to do additional troubleshooting.

OK cool now my other question is.
How dose the DB Repair work? I have just run it and it claims to have moved some files and repaired, which is really interesting cos it has just been run on a system that dose NOT have plex installed!!

That would mean that Plex was installed at some point, as it found the files it expected. Without knowing which options you selected from the database repair tool I cant tell you exactly what it did. There are several repair methods available depending on how damaged your database is.

Can’t see how, things like that I always run in windows Sandbox mode first to see what it dose. No options came up when you run the windows bat file, it just spat out a bunch of info saying it had done this that and the other and moved 3 files

do you have a file at %LOCALAPPDATA%\Plex Media Server\Plug-in Support\Databases\PlexDBRepair.log ?
Without knowing what that actually said, I cant tell you exactly what it did. That batch file dumps your current database into a new copy, and then moves the original databases to a dbtmp folder, then moves the dumped/restored copy back to where it was originally. (there are other steps that happen but I am giving a high level overview) with the log files I could provide more information for what happened exactly in your case.

@morpheus2n2

A corrupt database can cause the problems you are experiencing. There may be other issues, but the first step in fixing things is repairing the database.

The post I linked in my first reply shows the output of the repair process. That is from Plex Media Server running on my Windows 10 PC. ChuckPa, the account on GitHub, works for Plex (Team Member = consultant/contractor). He has the same username on this forum.

As @dbirch mentions, the bat file makes a backup of the current database files.

You can easily make a backup yourself. Stop Plex Media Server (to close the files), navigate to the Plex Data Folder → Plug-in Support. Then copy the Databases folder to another location.

If you like, you can try a manual repair, issuing the SQL commands yourself. See Repair A Corrupted Database.

I still suggest you use the BAT file. It makes the process much easier.

Ok worked it out, and its now run properly on the main plex machine and has fixed the DB, just hoping its the last of the mess :smiley:

Ahh see I knew that wouldn’t fix it,
Server was running for just a few hours and has done it again!!
@sa2000 was the one on the case last time.
This time I was able to get a dump file :smiley:

@morpheus2n2 Not sure what that google drive link is for, but you should be able to zip and upload your logs to this thread.

Logs, connections list and dump file which is to big to upload hence the link.

If you compress the logs folder it should be ~5mb and you can upload it.

Yes I know that, but you can NOT compress the dump file from 300+mb down enough for the forums!

You can upload just the logs to the thread.

Also, can you modify the Google Drive permissions so a Google login is not required to download the file?

I’ll sort the permission bit out in a min, however when I had this issue last time I was asked to put the logs and dump etc all together for ease

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