Knowledge Base

I tried upgrading Jellyfin past 10.10 series to the 10.11 series a few months ago, and the database corruption broke the application for me. I had to restore from backup. I have a rpm-switched-to-docker installation on CentOS 7, so my configs and logs are in RHEL-like places rather than in ${HOME}. Thankfully, restoring from backup is just exploding the tarball which restores paths /etc/jellyfin and /var/lib/jellyfin.

Downgrading went fine, thankfully.

Well, I recently tried to upgrade again, now that they've had many point releases underneath 10.11. The db migration went OK, and I did notice that the home screen and overall navigation feels visibly slower.

The app would crash randomly though, when doing boring things like navigation or checking a video's "watched" checkbox. I couldn't find anything in the /var/log/jellyfin/jellyfin_YYYYMMDD.log file, or in docker-compose logs -f --tail=30. I ended up finding something interesting in /var/log/messages. The application was throwing weird errors, not quite a kernel panic: See Appendix A below.

I googled it, and found that lib_sqlite3.so is trying to use sse4.1. I happen to know the reason this system is using CentOS 7 is because CentOS 8's Linux kernel 4.0 series had dropped the drivers for the RAID controller. So of course this system is also so ancient it definitely doesn't have any sse4 instructions. The way to check is to run </proc/cpuinfo grep sse4.

So I reverted to 10.10.7 again and thankfully my recent backup mostly worked. I swear there's still some sort of performance degredation, particularly of video playback which is the "one job" of Jellyfin. But technically the video did play, eventually. It felt like one of those big mkv files where the system is trying to parse all 20GBs rather than streaming it a little at a time.

And upstream Jellyfin has a way forward for this sse4.1 problem. They have submitted a bug to their upstream which will take time, to not require sse4.1. Apparently lots of other Jellyfin users are using old/underpowered hardware too. So I'll wait even longer for upgrading. Man, I want to stay up to date so I don't have huge jumps in behavior, design, functionality, and config changes. But Jellyfin's 10.11 series has had a bunch of bumps. Don't worry; I'm still never leaving. Jellyfin is FLOSS, and FLOSS is life!

Appendices

Appendix A: Crash entry in /var/log/messages

Jul  8 18:54:27 vm4 kernel: traps: .NET TP Worker[6110] trap invalid opcode ip:7f35222a0dfa sp:7f3515efac00 error:0 in libe_sqlite3.so[7f3522279000+d9000]
Jul  8 18:54:27 vm4 containerd: time="2026-07-08T18:54:27.900368087-04:00" level=info msg="shim disconnected" id=4602ed007f02a68cda8a1ba8236d6d57a327f5622eee8949d2d707a5e2478bcb 
Jul  8 18:54:27 vm4 containerd: time="2026-07-08T18:54:27.902140773-04:00" level=warning msg="cleaning up after shim disconnected" id=4602ed007f02a68cda8a1ba8236d6d57a327f5622eee8949d2d707a5e2478bcb namespace=moby
Jul  8 18:54:27 vm4 containerd: time="2026-07-08T18:54:27.902185128-04:00" level=info msg="cleaning up dead shim"
Jul  8 18:54:27 vm4 dockerd: time="2026-07-08T18:54:27.900515177-04:00" level=info msg="ignoring event" container=4602ed007f02a68cda8a1ba8236d6d57a327f5622eee8949d2d707a5e2478bcb module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Jul  8 18:54:27 vm4 containerd: time="2026-07-08T18:54:27.922833969-04:00" level=warning msg="cleanup warnings time=\"2026-07-08T18:54:27-04:00\" level=info msg=\"starting signal loop\" namespace=moby pid=6511 runtime=io.containerd.runc.v2\n"
Jul  8 18:54:28 vm4 containerd: time="2026-07-08T18:54:28.939694602-04:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
Jul  8 18:54:28 vm4 containerd: time="2026-07-08T18:54:28.940012414-04:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
Jul  8 18:54:28 vm4 containerd: time="2026-07-08T18:54:28.940049838-04:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1