SOLVED: Jellyfin server on fedora asahi linux crash

[Armentis]

Hi everybody,


Since the last fedora update was released :

Fedora Linux Asahi Remix 41
Kernel Linux 6.12.12-400.asahi.fc41.aarch64+16k

The Jellyfin server crashes systematically and randomly many times and crashes the system at the same time. I just did a complete system reinstallation and the crashes are happening again.

In the jellyfin log file, i detect 3 WRN :

[WRN] [1] Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware: The WebRootPath was not found: "/var/lib/jellyfin/wwwroot". Static files may be unavailable.
[WRN] [1] MediaBrowser.MediaEncoding.Encoder.MediaEncoder: Filter: "scale_cuda" with option "format" is not available
[WRN] [1] MediaBrowser.MediaEncoding.Encoder.MediaEncoder: Filter: "tonemap_cuda" with option "GPU accelerated HDR to SDR tonemapping" is not available

Thanks for the help

[gnattu]

The very first thing is that your Jellyfin server is outdated. Please try update to latest version first. The dotnet version shipped with 10.9 might be having trouble with 16K pages on Linux, so updating could help. But that is not a guarantee.

Also, Jellyfin is not officially encouraged to be running on Apple Silicon with Linux, as hardware acceleration features won't work because those are mainly built for macOS. There aren’t equivalent implementations for Linux right now, unfortunately. This means you have to use your CPU for all server side media processing. Although M1 is fast enough to do most of the work with software, you may still want to use the hardware acceleration to improve performance and reduce power consumption. By running it on Linux you also lose the higher quality Apple AAC encoder shipped with macOS, but that is less of a problem.

As for the warnings, they usually don’t cause major problems. The one is only for the swagger which is not used by jellyfin-web but only api docs, the other two will print on all platforms have no cuda support which means nothing if you don't want to use cuda base acceleration. If no obvious logs are printed and it crashes, and your system is not out of resources (like stopped by an oom kill), then it is very likely a compatibility problem but I cannot judge which part is the problem. It could be your kernel updates, or it could be the too old dotnet having bugs.

[Armentis]

Thanks for your help.

My actual Jellyfin server version is 10.10.5. I forgot to change it in my profil..

I know for the hardware accelaration. However, it has been working very well for 1 year now, exept since (I think) the latest major udapte for fedora.

[gnattu]

> exept since (I think) the latest major udapte for fedora.

Then I think that could be the kernel regression? Can you try rollback kernel and see if that was indeed the case

[Armentis]

Seem to work well since the last fedora udapte.