Skip to content
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

Open
hakova opened this issue Sep 28, 2024 · 5 comments
Open

kernel: pid 7656 (daemon), jid 7, uid 868: exited on signal 12 #86

hakova opened this issue Sep 28, 2024 · 5 comments

Comments

@hakova
Copy link

hakova commented Sep 28, 2024

Hi there,

I cannot get the jellyfin service started with the error above. Any idea about what I am missing?

Thanks!

@Thefrank
Copy link
Owner

@hakova
OS Version? (uname -a;freebsd-version):
Jellyfin Version:?:
Installation? (e.g., jail, plugin, binary):

The daemon really should not be crashing either so I might need more information depending on the above

@hakova
Copy link
Author

hakova commented Sep 28, 2024

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.

@Thefrank
Copy link
Owner

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

@sarchar
Copy link

sarchar commented Oct 29, 2024

I am currently experiencing this same issue - jellyfin exits with Bad system call. Might be related to Mono?

Oct 29 15:09:56 nas kernel: pid 94681 (daemon), jid 12, uid 868: exited on signal 12
Oct 29 15:10:38 nas kernel: pid 94702 (daemon), jid 12, uid 868: exited on signal 12
Oct 29 15:11:18 nas kernel: pid 94738 (jellyfin), jid 12, uid 868: exited on signal 12

The third line (jellyfin) is my attempt to run the executable directly instead of through service start:

root@jellyfin-server:/usr/local/jellyfin # su -m jellyfin -c '/usr/local/jellyfin/jellyfin --datadir /var/db/jellyfin --cachedir /var/cache/jellyfin'
Bad system call

uname -a;freebsd-version:

FreeBSD jellyfin-server 13.1-RELEASE-p9 FreeBSD 13.1-RELEASE-p9 n245429-296d095698e TRUENAS amd64
13.3-RELEASE-p7

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.

@badrpc
Copy link

badrpc commented Oct 29, 2024

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 daemon is also getting killed due to bad system call (signal 12) so the problem affects the whole userland and therefore is not specific to or caused by jellyfin, .NET or anything above the standard userland.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants