Yesterday, 09:17 PM
(This post was last modified: Yesterday, 09:17 PM by Sea Monkey. Edited 1 time in total.)
(Yesterday, 06:45 PM)tomstephens89 Wrote: I am managing to lock the database and stop Jellyfin responding. I already have knocked down parallel library scanning to 8 threads on an i7 13700k system with NVME application and 8 spinner RAID 0 data.
I am in the default 'NoLock' mode. I have never had such problems in the 2 years up until now. Should I change to optimistic?
This appears to be happening when I try and run an initial library sync from a new Pi5 running Kodi with the jellyfin add on. The Jellyfin UI becomes completely unresponsive when this happens and I have to restart.
Change to optimistic and remove the parallel thread limitation. You'll still likely have trouble getting Jellyfin for Kodi to fully sync, especially with large libraries, but this will at least prevent the database locking and entirely collapsing the server. If you haven't already nuked your libraries, I'd recommend against it and just enjoying whatever content you currently have in there until a bugfix release. There's always Jellycon if you want to see new content on the server within Kodi.