2025-04-15, 04:13 PM
I'm talking about database FILES that a plugin creates. For example, the Playback Reporting plugin and newsletter plugin both create their own database files.
Your log doesn't fully print all the plugin log info, so I can't be sure what you've shared includes all your plugins.
I've seen situations where either the Playback Reporting or Kodi Sync Queue plugin databases were corrupt, but the Jellyfin databases were fine. But the plugin DB being corrupt would prevent the server as a whole from starting. Manually removing the offending plugin(s) would resolve the server startup problem, assuming that it was the plugin database that is corrupt.
Code:
chris@rat-trap:/docker/containers/jellyfin-prod-data/config/data$ ll *.db*
-rwxr--r-- 1 jellyfin chris 12709888 Apr 15 11:05 jellyfin.db*
-rwxr--r-- 1 jellyfin jellyfin 32768 Apr 15 11:10 jellyfin.db-shm*
-rwxr--r-- 1 jellyfin jellyfin 4124152 Apr 15 11:07 jellyfin.db-wal*
-rwxr--r-- 1 jellyfin chris 365871104 Apr 15 10:55 library.db*
-rwxr--r-- 1 jellyfin jellyfin 244551680 Jan 25 16:19 library.db.bak1*
-rwxr--r-- 1 jellyfin jellyfin 720896 Apr 15 11:01 library.db-shm*
-rwxr--r-- 1 jellyfin jellyfin 134217728 Apr 15 11:01 library.db-wal*
-rw-r--r-- 1 jellyfin chris 8900608 Nov 18 16:42 newsletters.db
-rw-r--r-- 1 jellyfin chris 999424 Apr 15 07:51 playback_reporting.db
Your log doesn't fully print all the plugin log info, so I can't be sure what you've shared includes all your plugins.
I've seen situations where either the Playback Reporting or Kodi Sync Queue plugin databases were corrupt, but the Jellyfin databases were fine. But the plugin DB being corrupt would prevent the server as a whole from starting. Manually removing the offending plugin(s) would resolve the server startup problem, assuming that it was the plugin database that is corrupt.