-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kernel: pid 7656 (daemon), jid 7, uid 868: exited on signal 12 #86
Comments
@hakova The daemon really should not be crashing either so I might need more information depending on the above |
Thank you for the quick response. I am sorry for missing posting that crucial piece of information. TrueNAS Core, jellyfin version 10.9.6 in a jail following the guide here. While I was troubleshooting, reading the issue 75, I realized that it addressed my problem. Following the recommendation there, i.e., installing tmux and running jellyfin within tmux and detaching actually worked. Based on the bleak future of TrueNAS Core, I will be using it this way as long as I can. Later on, when I have the courage and time, I may switch to FreeBSD completely, giving up the nice UI provided by TrueNAS Core. |
TrueNAS Core 13.3 should be out. Give that shot and update the jail that is running jellyfin and see if that resolves the issue |
I am currently experiencing this same issue - jellyfin exits with Bad system call. Might be related to Mono?
The third line (jellyfin) is my attempt to run the executable directly instead of through
EDIT: My TrueNAS is the 13.0 stream, so that's probably the inconsistency -- even though the jail for jellyfin is 13.3, TrueNAS is oudated. I'm postponing my update to 13.3 for now, but may report back sometime. |
I think it's almost never a good idea to have a userland (libraries, commands, such as daemon, etc.) more recent than a kernel. Whether it's a system userland or a userland inside a jail makes no difference here. A more recent userland may expect the kernel to support features not present in the older kernel. I'm pretty sure this is exactly what's causing the "Bad system call" error. Notice that the system command |
Hi there,
I cannot get the jellyfin service started with the error above. Any idea about what I am missing?
Thanks!
The text was updated successfully, but these errors were encountered: