Plex was running but not responding this morning on my server and when I closed and re-opened the app it said it couldn’t connect to my server securely. After allowing an insecure connection it now says “A problem has been detected with a core component of Plex Media Server.”
Logs.7z (3.1 MB)
I’m running Windows Server 2019 and I think the problem occurred last night when a virtual machine started using way too much RAM. It crashed Minecraft too, but that is running again when I started it this morning.
Any suggestions?
Pfft. Restarting the server again seems to have fixed it. Guess I’ll just focus on making sure I have a good understanding of backing up and restoring the database in the future.
Precautionary measure: Verify that your primary plex database file hasn’t been corrupted
-
activate debug logging (not ‘verbose’!)
- quit Plex Server
- wait 1 minute
- start Plex Server
- wait 5 minutes
-
fetch log files and attach them here
Or inspect them yourself. Take a look at the Plex Media Server.log file and seek for messages about database corrupt or malformed.
If you find these, you may have to repair your database.
Thank you for your reply.
I searched Plex Media Server.log, as well as […].1.log, .2.log, etc. and found no instance of the word corrupt or malformed.
Is there some kind of best practice when it comes to backing up and restoring the database?
Backups of the main database file are done automatically.
If you want to backup the whole Plex data folder, you need to use your own backup solution. Here is one customized for Plex on Windows: https://github.com/alekdavis/PlexBackup
