2024-06-26, 01:36 PM
(This post was last modified: 2024-06-26, 01:39 PM by Divine Knight. Edited 2 times in total.
Edit Reason: this was meant to be a reply, oops...
)
(2024-06-25, 04:44 PM)ThomasPGH Wrote: 10.9.x needs a few minutes to reorganise the database after an upgrade from 10.8.13 when started for the first time. Since my nssm config is non-default I usually uninstall the service manually and run a batch script with the correct config after each Jellyfin upgrade. Due to the warning at https://github.com/jellyfin/jellyfin/issues I made sure Jellyfin is fully up and running this time, which is something I normally don't do. I also shut it down from the webinterface, which is also something I usually never do.
Could it be that you somehow killed 10.9.6 before the database reorganisation completed and that you maybe ended up with a corrupt database?
Thanks for the suggestion!
I might have accidentally updated Jellyfin via winget using the silent switch and winget breaking that db migration/update process.
But I doubt this directly relates to my issue since a completely fresh Jellyfin 10.9.6 installation, with the 'ProgramData/Jellyfin' folder (which contains the jellyfin.db and library.db) being deleted, still causes my issue on that "vanilla" setup.
While a fresh 10.8.13 install does not.
I might try to upgrade to 10.9.0 this weekend to see if that works.
I just want to get past the "Upgrade your server to at least 10.9.0 or else this client won't be compatible after the next update" message present in the AndroidTV app.