Jellyfin has locked up my server. Should I reboot or wait?
Jellyfin has locked up my server. Should I reboot or wait?
I started the scan for my movie collection (roughly 140 movies) on my Raspberry Pi 3B. It has become unresponsive and I can't ssh in now. It seems to be due to all the ffmpeg instances. I have two questions:
Should I wait for an hour or should I just reboot the server? Also, is there a way to disable the setting for chapter images from the web UI? I can't find it in the setting.
It is running ffmpeg which is likely converting your videos (or possibly extracting thumbnails).
I'd look in the settings and see if there's something related to that you can turn off.
Besides the obvious transcoding, trickplay or movie miniature generation will do that to you, yeah.
I waited a long time before making this post. Within minutes of posting the system became responsive again. It only picked up on one movie though.
Jellyfin really shouldn't push the available system resources so hard. It's impossible for the user to know if the scan is actually happening when the UI and SSH interfaces have locked up. It seems it couldn't complete the scan either because it was being excessive with system resources.
If you use some kind of virtualisation and/or containerisation then you can limit ram and/or cpu usage. This can of course greatly reduce lockups if not eliminate them.
Edit: I only now read it's a Pi 3B. Not sure if hosting Jellyfin on that device is a good idea... If you insist though, consider running an LXC inbetween and limit it to three cores. That should leave one core available for the system so the system doesn't lock up again.
...i think a 3B is severely underpowered if you are going to be using transcoding. I'd disable it completely so it basically only serves the file.
Can you maybe set niceness, ioniceness and cpu affinity?
if you lower those for the type of processes that cause this, responsiveness for other things will be better.
If you can't inject things like ionice or nice into the command lines of those processes, maybe use a cronjob to find and renice or ionice -p them.
I never thought of that, good idea. This docker image spins off a lot of processes so I wonder if there’s a high-level way to instruct that for all of them.
Probably your 3b is way underpowered for the task? I don't want to discourage you, but I only use mine as USBIP server and even updating that thing after install is feeling f* slow.
I think you're right. The CPU issue settles down after the first scan on a vanilla installation. But now my swap space is getting filled which is locking up the system. A Pi4 with 4GB of RAM isn't expensive though so if I can just swap the units without having to do anything else I might do that.