+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Core dump at start of Server (/t-core-dump-at-start-of-server)
Core dump at start of Server - vincen - 2023-12-03
Hi
Here are the situation: I have a Debian 12 server running Jellyfin server 10.8.13 if I remember well (the recent update for security issue). It was running well since weeks. I had to reboot the server for some outside reasons (change of UPS).
Since server has been restarted, Jellyfin server doesn't start anymore. It just crashes with a coredump.
No updates of the Debian 12 has been done recently neither any modifications in system. The most recent update has been to upgrade the jellyfin server for the security issue.
Here is result when I try to start service by hand:
Code:
root@pro-4:~# /etc/init.d/jellyfin start
Starting jellyfin (via systemctl): jellyfin.service.
root@pro-4:~# /etc/init.d/jellyfin status
× jellyfin.service - Jellyfin Media Server
Loaded: loaded (/lib/systemd/system/jellyfin.service; enabled; preset: enabled)
Drop-In: /etc/systemd/system/jellyfin.service.d
└─jellyfin.service.conf
Active: failed (Result: core-dump) since Sun 2023-12-03 08:50:55 CET; 2s ago
Duration: 602ms
Process: 82250 ExecStart=/usr/bin/jellyfin $JELLYFIN_WEB_OPT $JELLYFIN_RESTART_OPT $JELLYFIN_FFMPEG_OPT $JELLYFIN_SERVICE_OPT $JELLYFIN_NOWEBAPP_OPT $JELLYFIN_ADDITIONAL_OPTS (code=dumped, signal=ABRT)
Main PID: 82250 (code=dumped, signal=ABRT)
CPU: 279ms
Dec 03 08:50:55 pro-4.toto.net systemd[1]: Stopped jellyfin.service - Jellyfin Media Server.
Dec 03 08:50:55 pro-4.toto.net systemd[1]: jellyfin.service: Converting job jellyfin.service/restart -> jellyfin.service/start
Dec 03 08:50:55 pro-4.toto.net systemd[1]: jellyfin.service: Consumed 279ms CPU time.
Dec 03 08:50:55 pro-4.toto.net systemd[1]: jellyfin.service: Start request repeated too quickly.
Dec 03 08:50:55 pro-4.toto.net systemd[1]: jellyfin.service: Failed with result 'core-dump'.
Dec 03 08:50:55 pro-4.toto.net systemd[1]: jellyfin.service: Service restart not allowed.
Dec 03 08:50:55 pro-4.toto.net systemd[1]: jellyfin.service: Changed dead -> failed
Dec 03 08:50:55 pro-4.toto.net systemd[1]: jellyfin.service: Job 13661 jellyfin.service/start finished, result=failed
Dec 03 08:50:55 pro-4.toto.net systemd[1]: Failed to start jellyfin.service - Jellyfin Media Server.
Dec 03 08:50:55 pro-4.toto.net systemd[1]: jellyfin.service: Unit entered failed state.
root@pro-4:~#Here is one of the coredump it generates when it tries to start:
Code:
root@pro-4:~# coredumpctl debug 70342
PID: 70342 (jellyfin)
UID: 117 (jellyfin)
GID: 127 (jellyfin)
Signal: 6 (ABRT)
Timestamp: Sun 2023-12-03 08:39:30 CET (2min 20s ago)
Command Line: /usr/bin/jellyfin --webdir=/usr/share/jellyfin/web --restartpath=/usr/lib/jellyfin/restart.sh --ffmpeg=/usr/lib/jellyfin-ffmpeg/ffmpeg
Executable: /usr/lib/jellyfin/bin/jellyfin
Control Group: /system.slice/jellyfin.service
Unit: jellyfin.service
Slice: system.slice
Boot ID: 454d5ce2671b46039499ffde9ca17e5f
Machine ID: 364fa134852f4098b60fb7e16c7fef01
Hostname: pro-4.toto.net
Storage: /var/lib/systemd/coredump/core.jellyfin.117.454d5ce2671b46039499ffde9ca17e5f.70342.1701589170000000.zst (present)
Size on Disk: 3.7M
Message: Process 70342 (jellyfin) of user 117 dumped core.
Stack trace of thread 70342:
#0 0x00007f4460ca9d3c n/a (libc.so.6 + 0x8ad3c)
#1 0x00007f4460c5af32 raise (libc.so.6 + 0x3bf32)
#2 0x00007f4460c45472 abort (libc.so.6 + 0x26472)
#3 0x00007f4460912ea2 n/a (libcoreclr.so + 0x512ea2)
#4 0x00007f4460912dc2 n/a (libcoreclr.so + 0x512dc2)
#5 0x00007f44606da635 n/a (libcoreclr.so + 0x2da635)
#6 0x00007f44606da716 n/a (libcoreclr.so + 0x2da716)
#7 0x00007f446062b598 n/a (libcoreclr.so + 0x22b598)
#8 0x00007f43e79464d8 n/a (n/a + 0x0)
#9 0x00007f43e6b4409e n/a (n/a + 0x0)
#10 0x00007f43e6b43fd9 n/a (n/a + 0x0)
#11 0x00007f43e6b43f6e n/a (n/a + 0x0)
#12 0x00007f4460783597 n/a (libcoreclr.so + 0x383597)
#13 0x00007f44605b978b n/a (libcoreclr.so + 0x1b978b)
#14 0x00007f446048efea n/a (libcoreclr.so + 0x8efea)
#15 0x00007f446048f341 n/a (libcoreclr.so + 0x8f341)
#16 0x00007f44604c3d23 n/a (libcoreclr.so + 0xc3d23)
#17 0x00007f446047720a coreclr_execute_assembly (libcoreclr.so + 0x7720a)
#18 0x00007f44610625b1 n/a (libhostpolicy.so + 0x185b1)
#19 0x00007f4461062a41 n/a (libhostpolicy.so + 0x18a41)
#20 0x00007f446106346c corehost_main (libhostpolicy.so + 0x1946c)
#21 0x00007f44610bcc14 n/a (libhostfxr.so + 0x13c14)
#22 0x00007f44610bb349 n/a (libhostfxr.so + 0x12349)
#23 0x00007f44610b693b hostfxr_main_startupinfo (libhostfxr.so + 0xd93b)
#24 0x000056088904fa25 n/a (jellyfin + 0x10a25)
#25 0x000056088904fef0 n/a (jellyfin + 0x10ef0)
#26 0x00007f4460c461ca n/a (libc.so.6 + 0x271ca)
#27 0x00007f4460c46285 __libc_start_main (libc.so.6 + 0x27285)
#28 0x0000560889043d7a n/a (jellyfin + 0x4d7a)
Stack trace of thread 70345:
#0 0x00007f4460d1b05f __poll (libc.so.6 + 0xfc05f)
#1 0x00007f446090b5de n/a (libcoreclr.so + 0x50b5de)
#2 0x00007f446090cf6f n/a (libcoreclr.so + 0x50cf6f)
#3 0x00007f4460917cee n/a (libcoreclr.so + 0x517cee)
#4 0x00007f4460ca8044 n/a (libc.so.6 + 0x89044)
#5 0x00007f4460d2861c n/a (libc.so.6 + 0x10961c)
Stack trace of thread 70351:
#0 0x00007f4460d170dc read (libc.so.6 + 0xf80dc)
#1 0x00007f43e40ba33f n/a (libSystem.Native.so + 0xf33f)
#2 0x00007f4460ca8044 n/a (libc.so.6 + 0x89044)
#3 0x00007f4460d2861c n/a (libc.so.6 + 0x10961c)
Stack trace of thread 70348:
#0 0x00007f4460ca4da6 n/a (libc.so.6 + 0x85da6)
#1 0x00007f4460ca7468 pthread_cond_wait (libc.so.6 + 0x88468)
#2 0x00007f446090b2ab n/a (libcoreclr.so + 0x50b2ab)
#3 0x00007f446090af61 n/a (libcoreclr.so + 0x50af61)
#4 0x00007f446090f942 n/a (libcoreclr.so + 0x50f942)
#5 0x00007f446090fc51 n/a (libcoreclr.so + 0x50fc51)
#6 0x00007f44607e9559 n/a (libcoreclr.so + 0x3e9559)
#7 0x00007f44607e93c5 n/a (libcoreclr.so + 0x3e93c5)
#8 0x00007f44607e910d n/a (libcoreclr.so + 0x3e910d)
#9 0x00007f4460917cee n/a (libcoreclr.so + 0x517cee)
#10 0x00007f4460ca8044 n/a (libc.so.6 + 0x89044)
#11 0x00007f4460d2861c n/a (libc.so.6 + 0x10961c)
Stack trace of thread 70350:
#0 0x00007f4460ca4da6 n/a (libc.so.6 + 0x85da6)
#1 0x00007f4460ca774c pthread_cond_timedwait (libc.so.6 + 0x8874c)
#2 0x00007f446090b296 n/a (libcoreclr.so + 0x50b296)
#3 0x00007f446090af61 n/a (libcoreclr.so + 0x50af61)
#4 0x00007f44609100f9 n/a (libcoreclr.so + 0x5100f9)
#5 0x00007f446058135a n/a (libcoreclr.so + 0x18135a)
#6 0x00007f44605811ac n/a (libcoreclr.so + 0x1811ac)
#7 0x00007f446057db4a n/a (libcoreclr.so + 0x17db4a)
#8 0x00007f446057e14d n/a (libcoreclr.so + 0x17e14d)
#9 0x00007f44605810d0 n/a (libcoreclr.so + 0x1810d0)
#10 0x00007f4460917cee n/a (libcoreclr.so + 0x517cee)
#11 0x00007f4460ca8044 n/a (libc.so.6 + 0x89044)
#12 0x00007f4460d2861c n/a (libc.so.6 + 0x10961c)
Stack trace of thread 70346:
#0 0x00007f4460d1b05f __poll (libc.so.6 + 0xfc05f)
#1 0x00007f44607f261c n/a (libcoreclr.so + 0x3f261c)
#2 0x00007f44608b98cd n/a (libcoreclr.so + 0x4b98cd)
#3 0x00007f44608b76b7 n/a (libcoreclr.so + 0x4b76b7)
#4 0x00007f4460917cee n/a (libcoreclr.so + 0x517cee)
#5 0x00007f4460ca8044 n/a (libc.so.6 + 0x89044)
#6 0x00007f4460d2861c n/a (libc.so.6 + 0x10961c)
Stack trace of thread 70349:
#0 0x00007f4460ca4da6 n/a (libc.so.6 + 0x85da6)
#1 0x00007f4460ca774c pthread_cond_timedwait (libc.so.6 + 0x8874c)
#2 0x00007f446090b296 n/a (libcoreclr.so + 0x50b296)
#3 0x00007f446090af61 n/a (libcoreclr.so + 0x50af61)
#4 0x00007f446090f942 n/a (libcoreclr.so + 0x50f942)
#5 0x00007f446090fb79 n/a (libcoreclr.so + 0x50fb79)
#6 0x00007f44606a319a n/a (libcoreclr.so + 0x2a319a)
#7 0x00007f44606025ff n/a (libcoreclr.so + 0x2025ff)
#8 0x00007f44606027bc n/a (libcoreclr.so + 0x2027bc)
#9 0x00007f446057db4a n/a (libcoreclr.so + 0x17db4a)
#10 0x00007f446057e1ed n/a (libcoreclr.so + 0x17e1ed)
#11 0x00007f44606029e8 n/a (libcoreclr.so + 0x2029e8)
#12 0x00007f4460917cee n/a (libcoreclr.so + 0x517cee)
#13 0x00007f4460ca8044 n/a (libc.so.6 + 0x89044)
#14 0x00007f4460d2861c n/a (libc.so.6 + 0x10961c)
Stack trace of thread 70347:
#0 0x00007f4460d16e80 __open64 (libc.so.6 + 0xf7e80)
#1 0x00007f44607f309f n/a (libcoreclr.so + 0x3f309f)
#2 0x00007f44607ebc98 n/a (libcoreclr.so + 0x3ebc98)
#3 0x00007f44607eadb9 n/a (libcoreclr.so + 0x3eadb9)
#4 0x00007f4460917cee n/a (libcoreclr.so + 0x517cee)
#5 0x00007f4460ca8044 n/a (libc.so.6 + 0x89044)
#6 0x00007f4460d2861c n/a (libc.so.6 + 0x10961c)
ELF object binary architecture: AMD x86-64
GNU gdb (Debian 13.1-3) 13.1
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/jellyfin/bin/jellyfin...
(No debugging symbols found in /usr/lib/jellyfin/bin/jellyfin)
[New LWP 70342]
[New LWP 70345]
[New LWP 70351]
[New LWP 70348]
[New LWP 70350]
[New LWP 70346]
[New LWP 70349]
[New LWP 70347]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/jellyfin --webdir=/usr/share/jellyfin/web --restartpath=/usr/lib/jelly'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007f4460ca9d3c in ?? () from /lib/x86_64-linux-gnu/libc.so.6
[Current thread is 1 (Thread 0x7f4461112740 (LWP 70342))]
(gdb)
Not sure what else I can supply about it ? or what to look to fix the problem as the coredump is quite impossible to understand for me
Last thing I had done related at Jellyfin server was to change the cache directory but Jellyfin had been restarted since and was working fine since (modification done 1/2 days ago)
Thanks for help,
Vincèn
RE: Core dump at start of Server - TheDreadPirate - 2023-12-03
Is the cache directory on a separate drive?
RE: Core dump at start of Server - vincen - 2023-12-04
(2023-12-03, 03:04 PM)TheDreadPirate Wrote: Is the cache directory on a separate drive?Well drives means nothing on Linux but volume yep ! It has worked before like that when I rstarted Jellyfin server process when I changed the directory !
Does it mean I should use a symlink ?
RE: Core dump at start of Server - TheDreadPirate - 2023-12-04
No. I was just considering whether the drive unmounted or the mounting parameters changed or something. A symlink would still be affected by both scenarios.
RE: Core dump at start of Server - vincen - 2023-12-07
(2023-12-04, 03:42 PM)TheDreadPirate Wrote: No. I was just considering whether the drive unmounted or the mounting parameters changed or something. A symlink would still be affected by both scenarios.Nope no changes regarding mounted volumes. Any ideas what I can try to find a solution at problem or fix the issue ?
RE: Core dump at start of Server - TheDreadPirate - 2023-12-07
Backup /var/lib/jellyfin and reinstall at this point.
RE: Core dump at start of Server - vincen - 2023-12-08
(2023-12-07, 01:53 PM)TheDreadPirate Wrote: Backup /var/lib/jellyfin and reinstall at this point.oki will try that perhaps
For now giving it a try at Emby 
RE: Core dump at start of Server - Dewin - 2024-04-11
I had this problem. I didn't have /var/cache/jellyfin nor have it chmoded for jellyfin:jellyfin. Once I did those two things, it worked.