Plex Server keeps crashing up startup

Server Version#:1.42.1.10060-4e8b05daf
Player Version#: Firestick, Android phone

OS: Windows 11

Yesterday Plex just did its usual update, and then rebooted.

This time when it tried to fire up, PLEX keeps crashing.

After some snooping around, I noticed that the database (com.plexapp.plugins.library.db) now has NO OWNER., and cannot be accessed.

I have tried changing owner, changing security. Tried renaming and deleting the database. And I tried with both the ID that is used to start the Plex Server, and the actual Windows Administrator ID. No luck….

I search the various forums, and it is suggested that there is a file lock somewhere, but using all the guided resources and tools, no locks were found.

And after several more reboots, problem still exists.

Any help or guidance would be appreciated. The “old fashioned TV” is just not cutting it :sob:

Thanks

Plex Crash Uploader.log (2.3 KB)

Plex Media Server.log (6.8 KB)

<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/

Never start up plex server with “Run as Administrator”. This will mess up the access permissions in the plex data folder. You will have to reset them to the default of the parent folder. All of them. All files within all subfolders as well.

Inspect the file size of the primary db file. Is it larger than 1 GB?

How much free space is on this drive? Did it run full recently?

Hi,

No, I have never started the plex server with administrator only the usual id earmarked for the plex server. Logging in as administrator does not fire up plex.

There is plenty if space on the drive that hosts the database. The drive is a physical drive on the computer , not a network drive, and has about 600gb free out of 1tb.

The dB is 3.1gb, although I don’t really know how big, BIG really really means. I have around 15k movies, 1800 TV series and about 300k music tracks.

Thank you for responding. Is the dB too big?

I’m not sure. It might just be in the ballpark of what is to be expected with that much media.

I’d start by restoring an older database version as explained in my first link above.

It cannot hurt to try and run the DB bloat issue fix, followed by repairing the database using this bat file: DBRepair/Windows at master · ChuckPa/DBRepair · GitHub