2024-11-18, 04:08 PM
I recently installed Jellyfin (10.10.2.0) on an Ubuntu Server 24.04.1 VM through ProxMox. Everything worked correctly until the server rebooted and the service failed to start. However, if I go to connect to the web console I can connect and get full functionality if I just remove the server and re-add it.
When I use journalctl on jellyfin I get the following:
Here's the output of systemctl status jellyfin:
The log files show nothing from November 17th, they were last updated 3 days earlier when I purged and reinstalled. I can't start the service but if I do sudo /usr/bin/jellyfin start --ffmpeg=/usr/lib/jellyfin-ffmpeg/ffmpeg it starts fine, even though the service still says that it's not running. If the service isn't required can I just have this command run on after boot without any issues? Thanks!
When I use journalctl on jellyfin I get the following:
Code:
jellyfin.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit jellyfin.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Nov 17 12:44:53 nas systemd[1]: jellyfin.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit jellyfin.service has entered the 'failed' state with result 'exit-code'.
Nov 17 12:44:53 nas systemd[1]: jellyfin.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ Automatic restarting of the unit jellyfin.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Nov 17 12:44:53 nas systemd[1]: jellyfin.service: Start request repeated too quickly.
Nov 17 12:44:53 nas systemd[1]: jellyfin.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit jellyfin.service has entered the 'failed' state with result 'exit-code'.
Nov 17 12:44:53 nas systemd[1]: Failed to start jellyfin.service - Jellyfin Media Server.
░░ Subject: A start job for unit jellyfin.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit jellyfin.service has finished with a failure.
░░
░░ The job identifier is 1528 and the job result is failed.Here's the output of systemctl status jellyfin:
Code:
sudo systemctl status jellyfin
× jellyfin.service - Jellyfin Media Server
Loaded: loaded (/usr/lib/systemd/system/jellyfin.service; enabled; preset: enabled)
Drop-In: /etc/systemd/system/jellyfin.service.d
└─jellyfin.service.conf
Active: failed (Result: exit-code) since Sun 2024-11-17 12:44:53 EST; 22h ago
Duration: 201ms
Main PID: 1782 (code=exited, status=1/FAILURE)
CPU: 188ms
Nov 17 12:44:53 nas systemd[1]: jellyfin.service: Scheduled restart job, restart counter is at 5.
Nov 17 12:44:53 nas systemd[1]: jellyfin.service: Start request repeated too quickly.
Nov 17 12:44:53 nas systemd[1]: jellyfin.service: Failed with result 'exit-code'.
Nov 17 12:44:53 nas systemd[1]: Failed to start jellyfin.service - Jellyfin Media Server.The log files show nothing from November 17th, they were last updated 3 days earlier when I purged and reinstalled. I can't start the service but if I do sudo /usr/bin/jellyfin start --ffmpeg=/usr/lib/jellyfin-ffmpeg/ffmpeg it starts fine, even though the service still says that it's not running. If the service isn't required can I just have this command run on after boot without any issues? Thanks!