- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
I’m a bit surprised there hasn’t been an official post about this yet.
Big thanks to @joshuaboniface and the rest of the Jellyfin team
I’m also personally waiting for 10.9.1, there appears to be a small migration issue, and a memory leak.
I’m actually pretty good at finding memory issues in .net programs, maybe I’ll debug this a little on my setup if I get a moment. Dotnet trace was essential for this as it was a Linux arm device
Cool I updated anyway because I live dangerously
There’s a pinned announcement post that I made yesterday. It should be at the top.
Yeah, I can see it now.
I can only assume that the post hadn’t propagated to my server 3 hours ago.
Thanks for the heads up about the issues. I’ll probably wait for 10.9.1 too.
Just upgraded to 10.9.0, server didn’t close properly so there were sqlite
.db-wal
files left besides thejellyfin.db
andlibrary.db
files which caused an error about the database tables being locked.:Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 6: 'database table is locked'.
Solved it by running
systemctl stop jellyfin cd /var/lib/jellyfin/data sqlite3 jellyfin.db > .recover > .quit sqlite3 library.db > .recover > .quit
Now the
.db-wal
files were gone and I couldsystemctl start jellyfin
I did lose a bunch of music metadata, but the advantage of contributing to musicbrainz is that it’s easily recovered :)