Thanks for the logs
There are a couple of issues here
- the database appears to have got corrupted
May 10, 2022 09:40:58.251 [8828] ERROR - SQLITE3:0x85ae95fb, 11, database corruption at line 67162 of [1b256d97b5]
May 10, 2022 09:40:58.251 [14640] ERROR - SQLITE3:0x85ae95fb, 11, database corruption at line 67162 of [1b256d97b5]
May 10, 2022 09:40:58.251 [8828] ERROR - SQLITE3:0x85ae95fb, 11, statement aborts at 5: [select id from metadata_items where guid=? and id<>? ] database disk image is malformed
May 10, 2022 09:40:58.251 [14640] ERROR - SQLITE3:0x85ae95fb, 11, statement aborts at 5: [select id from metadata_items where guid=? and id<>? ] database disk image is malformed
May 10, 2022 09:40:58.252 [14640] ERROR - Soci Exception handled: sqlite3_statement_backend::loadOne: database disk image is malformed
- you appear to be running multiple instances of Plex Media Server.exe on the same machine. I suspect this is because you are running it as scheduled task or service and it is also starting as a process automatically on logging in on windows !
Multiple instances lead to indeterminate outcomes and may also cause database corruptions
If you run Plex Media Server as a service or scheduled task you must ensure you disable the automatic start on login - which is the default after every install / update. You could also use the 3rd party service wrapper solution that many users use instead of inventing your own - see PMS as a service - General Discussions / Tips, Tricks & How-Tos - Plex Forum
For database corruptions - see
Repair a Corrupted Database | Plex Support
Restore a Database Backed Up via ‘Scheduled Tasks’ | Plex Support
