SOLVED: Jellyfin service not starting

[merulius]

AMD 64bit
New Ubuntu install

I installed latest jellyfin a week ago from the official source and it worked fine. I used the one-line install that starts "curl".

I then closed my Ubuntu (22.04 Jammy) server, restarted and it has not worked since.

The following is the crucial part of the Journal.

Jan 09 19:14:54 balrog systemd[29812]: jellyfin.service: Failed at step EXEC spawning /opt/jellyfin/jellyfin.sh: No such file or directory
Jan 09 19:14:54 balrog systemd[1]: jellyfin.service: Main process exited, code=exited, status=203/EXEC

The directory /opt/jellyfin does not exist. I would think it should be created at install time.

I have uninstalled Jellyfin and reinstalled and same results.

Any ideas?

[TheDreadPirate]

So you ran this?

Code:

curl https://repo.jellyfin.org/install-debuntu.sh | sudo bash

/opt/jellyfin is the location of a manual Jellyfin install and the service should not be looking there. And I have a hard time believing it would randomly start looking there after a reboot.

What is the output of "systemctl status jellyfin"?

[merulius]

Thanks for the reply, Pirate.
I may have got confused (no, I did get confused) with installing, reinstalling etc.

Status follows. Thanks in advance for any help.


[18:51:48] [INF] [1] Main: Jellyfin version: 10.8.13
[18:51:48] [INF] [1] Main: Environment Variables: ["[JELLYFIN_LOG_DIR, /home/steve/.local/share/jellyfin/log]"]
[18:51:48] [INF] [1] Main: Arguments: ["/usr/lib/jellyfin/bin/jellyfin.dll"]
[18:51:48] [INF] [1] Main: Operating system: Linux
[18:51:48] [INF] [1] Main: Architecture: X64
[18:51:48] [INF] [1] Main: 64-Bit Process: True
[18:51:48] [INF] [1] Main: User Interactive: True
[18:51:48] [INF] [1] Main: Processor count: 12
[18:51:48] [INF] [1] Main: Program data path: /home/steve/.local/share/jellyfin
[18:51:48] [INF] [1] Main: Web resources path: /usr/lib/jellyfin/bin/jellyfin-web
[18:51:48] [INF] [1] Main: Application directory: /usr/lib/jellyfin/bin/
[18:51:48] [ERR] [1] Main: The server is expected to host the web client, but the provided content directory is either invalid or empty: /usr/lib/jellyfin/bin/jellyfin-web. If you do not want to host the web client with the server, you may set the '--nowebclient' command line flag, or set'hostwebclient=false' in your config settings.
[18:51:48] [INF] [2] Main: Received a SIGTERM signal, shutting down
steve@balrogusr/lib/jellyfin/bin$ sudo systemctl status jellyfin
× jellyfin.service - Jellyfin
Loaded: loaded (/etc/systemd/system/jellyfin.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/jellyfin.service.d
└─jellyfin.service.conf
Active: failed (Result: exit-code) since Wed 2024-01-10 15:26:52 UTC; 3h 40min ago
Main PID: 1443 (code=exited, status=203/EXEC)
CPU: 2ms

Jan 10 15:26:52 balrog systemd[1]: jellyfin.service: Scheduled restart job, restart counter is at 5.
Jan 10 15:26:52 balrog systemd[1]: Stopped Jellyfin.
Jan 10 15:26:52 balrog systemd[1]: jellyfin.service: Start request repeated too quickly.
Jan 10 15:26:52 balrog systemd[1]: jellyfin.service: Failed with result 'exit-code'.
Jan 10 15:26:52 balrog systemd[1]: Failed to start Jellyfin.

[TheDreadPirate]

Did you run the bash script as your self or did you run it as root. It looks like you ran it as yourself when you should be running it as root.

This is what is telling me you ran the install script as yourself.

Code:

[18:51:48] [INF] [1] Main: Program data path: /home/steve/.local/share/jellyfin

Do this and exactly this.

Code:

sudo apt purge jellyfin*
cd /home/steve/.local/share/
rm -rf jellyfin
curl https://repo.jellyfin.org/install-debuntu.sh | sudo bash

The part I think you missed was the "| sudo bash" at the end and you ran the script as yourself.

[merulius]

Thanks, Pirate. Below is the result of the install step. Doesn't look good. I did also install Gerbera at some point (trying to find an alternative to Jellyfin) and that seems to be causing a problem. I'm going to purge Gerbera following your template and will get back with the results.



% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0> Determining optimal repository settings.
100 9937 100 9937 0 0 16441 0 --:--:-- --:--:-- --:--:-- 16451

Found the following details from '/etc/os-release':
Real OS: ubuntu
Repository OS: ubuntu
Repository Release: jammy
CPU Architecture: amd64
If this looks correct, press <Enter> now to continue installing Jellyfin.

> Fetching repository signing key.

> Installing Jellyfin repository into APT.
Types: deb
URIs: https://repo.jellyfin.org/ubuntu
Suites: jammy
Components: main
Architectures: amd64
Signed-By: /etc/apt/keyrings/jellyfin.gpg

> Updating APT repositories.
Hit:1 http://gb.archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://gb.archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Hit:3 https://brave-browser-apt-release.s3.brave.com stable InRelease
Hit:4 http://gb.archive.ubuntu.com/ubuntu jammy-backports InRelease
Get:5 http://gb.archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Hit:6 https://downloads.1password.com/linux/debian/amd64 stable InRelease
Get:7 https://gerbera.jfrog.io/artifactory/debian jammy InRelease [4,080 B]
Get:8 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1,277 kB]
Get:9 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [261 kB]
Get:10 http://gb.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1,023 kB]
Get:11 http://gb.archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [228 kB]
Hit:12 https://pkg.cloudflareclient.com jammy InRelease
Get:13 http://gb.archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [826 kB]
Err:7 https://gerbera.jfrog.io/artifactory/debian jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E7F84CDAE846576A
Hit:14 https://repo.jellyfin.org/ubuntu jammy InRelease
Reading package lists... Done
W: GPG error: https://gerbera.jfrog.io/artifactory/debian jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E7F84CDAE846576A
E: The repository 'https://gerbera.jfrog.io/artifactory/debian jammy InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure( manpage for repository creation and user configuration details.
Failed to update APT repositories. Something is wrong with your APT sources, GPG keys, or Internet connection. Try again shortly or use https://jellyfin.org/contact to find us for troubleshooting.

[merulius]

Slightly more encouraging result to 'systemctl status jellyfin'

But still not running.



jellyfin.service - Jellyfin
Loaded: loaded (/etc/systemd/system/jellyfin.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/jellyfin.service.d
└─jellyfin.service.conf
Active: failed (Result: exit-code) since Thu 2024-01-11 16:50:42 UTC; 7s ago
Process: 54230 ExecStart=/lib/jellyfin/jellyfin.sh (code=exited, status=203/EXEC)
Main PID: 54230 (code=exited, status=203/EXEC)
CPU: 1ms

Jan 11 16:50:42 balrog systemd[1]: jellyfin.service: Scheduled restart job, restart counter is at 5.
Jan 11 16:50:42 balrog systemd[1]: Stopped Jellyfin.
Jan 11 16:50:42 balrog systemd[1]: jellyfin.service: Start request repeated too quickly.
Jan 11 16:50:42 balrog systemd[1]: jellyfin.service: Failed with result 'exit-code'.
Jan 11 16:50:42 balrog systemd[1]: Failed to start Jellyfin.

[merulius]

A bit more digging reveals that there is no file jellyfin.sh in /lib/jellyfin which explains the exception code 203.

Any ideas why it might be absent?

[merulius]

In jellyfin.service we see

[Unit]
Description=Jellyfin
After=network.target

[Service]
Type=simple
User=jellyfin
Restart=always
ExecStart=/lib/jellyfin/jellyfin.sh

[Install]
WantedBy=multi-user.target

And as I have written in a previous post, jellyfin.sh does not exist, at least not in /lib/jellyfin.

So this is confirmed straight-out-of-the-box. I don't know what is going on.

The jellyfin install instructions talk about creating a jellyfin.sh file and saving it in home directory (making it executable, etc).

Seems like I'm caught between two methods of installing - the automatic and the manual.

[TheDreadPirate]

> Updating APT repositories.
Hit:1 http://gb.archive.ubuntu.com/ubuntu jammy InRelease
Get:2 http://gb.archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]                                                                                               
Hit:3 https://brave-browser-apt-release.s3.brave.com stable InRelease                                                                                                                                 
Hit:4 http://gb.archive.ubuntu.com/ubuntu jammy-backports InRelease                                                                                                                                   
Get:5 http://gb.archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB]                                   
Hit:6 https://downloads.1password.com/linux/debian/amd64 stable InRelease                                                 
Get:7 https://gerbera.jfrog.io/artifactory/debian jammy InRelease [4,080 B]                                               
Get:8 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [1,277 kB]                       
Get:9 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [261 kB]                     
Get:10 http://gb.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [1,023 kB]                                         
Get:11 http://gb.archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [228 kB]                                         
Hit:12 https://pkg.cloudflareclient.com jammy InRelease                                                                               
Get:13 http://gb.archive.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [826 kB]     
Err:7 https://gerbera.jfrog.io/artifactory/debian jammy InRelease                   
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E7F84CDAE846576A
Hit:14 https://repo.jellyfin.org/ubuntu jammy InRelease
Reading package lists... Done
W: GPG error: https://gerbera.jfrog.io/artifactory/debian jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E7F84CDAE846576A
E: The repository 'https://gerbera.jfrog.io/artifactory/debian jammy InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure( manpage for repository creation and user configuration details.
Failed to update APT repositories. Something is wrong with your APT sources, GPG keys, or Internet connection. Try again shortly or use https://jellyfin.org/contact to find us for troubleshooting.

I don't think your server is actually pulling the jellyfin repo due to the issues you have with other repos.  Which is causing it to not pull down most of the packages.

In /etc/apt/sources.list.d/ remove the repo associated with  https://gerbera.jfrog.io/artifactory/debian.  Or comment it out temporarily.  Once you can get "sudo apt update" to run cleanly, redo the steps in my previous post.

[merulius]

Thanks. Will do and will report back.