SOLVED: Jellyfin service not starting

[umunas]

UPDATE:

Created fresh LXC in Proxmox and installed Jellyfin, configured CIFS and GPU passthrough and everything works for the time being even after several LXC reboots. I backed up LXC with working Jellyfin and will not touch it unless completely necessary. So, fingers crossed I won't have this problem. I have no clue what was the reason for it previously.

The strange thing about previous LXC was its size which was close to 14GiB with almost the same config as the new one, but the new one is only 1.83 GiB.

[Riesling]

Go to /etc/jellyfin in the LXC and if migrations.xml is zero bytes, delete the file and restart Jellyfin.

o.k. that fixed the not starting issue for me after upgrading to 10.10.
It now starts, but soon dies - goes from      
Active: active (running) since Tue 2024-11-05 22:08:05 CET; 10s ago 
to 
Active: inactive (dead) since Tue 2024-11-05 22:09:23 CET; 34s ago

Why is this happening - how can it be fixed to get it up, keep it up and become reachable again?

Code:

root@jellyfin:/var/log/jellyfin# systemctl status jellyfin
● jellyfin.service - Jellyfin Media Server
    Loaded: loaded (/lib/systemd/system/jellyfin.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/jellyfin.service.d
            └─jellyfin.service.conf
    Active: inactive (dead) since Tue 2024-11-05 22:20:47 CET; 2min 29s ago
    Process: 132 ExecStartPre=/bin/mkdir -p /var/log/jellyfin (code=exited, status=0/SUCCESS)
    Process: 137 ExecStartPre=/bin/chown jellyfin:jellyfin /var/log/jellyfin (code=exited, status=0/SUCCESS)
    Process: 138 ExecStart=/usr/bin/jellyfin $JELLYFIN_WEB_OPT $JELLYFIN_FFMPEG_OPT $JELLYFIN_SERVICE_OPT $JELLYFIN_NOWEBAPP_OPT $JELLYFIN_ADDITIONAL_OPTS (code=exited, status=0/SUCCESS)
  Main PID: 138 (code=exited, status=0/SUCCESS)
        CPU: 9.577s

Nov 05 22:20:47 jellyfin jellyfin[138]:    at Jellyfin.Server.Migrations.MigrationRunner.PerformMigrations(IMigrationRoutine[] migrations, MigrationOptions migrationOptions, Action`1 saveConfiguration, ILogger logger)
Nov 05 22:20:47 jellyfin jellyfin[138]:    at Jellyfin.Server.Migrations.MigrationRunner.Run(CoreAppHost host, ILoggerFactory loggerFactory)
Nov 05 22:20:47 jellyfin jellyfin[138]:    at Jellyfin.Server.Program.StartServer(IServerApplicationPaths appPaths, StartupOptions options, IConfiguration startupConfig)
Nov 05 22:20:47 jellyfin jellyfin[138]: [22:20:47] [INF] Running query planner optimizations in the database... This might take a while
Nov 05 22:20:47 jellyfin jellyfin[138]: [22:20:47] [INF] Disposing CoreAppHost
Nov 05 22:20:47 jellyfin jellyfin[138]: [22:20:47] [INF] Disposing MusicBrainzArtistProvider
Nov 05 22:20:47 jellyfin jellyfin[138]: [22:20:47] [INF] Disposing MusicBrainzAlbumProvider
Nov 05 22:20:47 jellyfin jellyfin[138]: [22:20:47] [INF] Disposing PluginManager
Nov 05 22:20:47 jellyfin systemd[1]: jellyfin.service: Succeeded.
Nov 05 22:20:47 jellyfin systemd[1]: jellyfin.service: Consumed 9.577s CPU time.

could the kept back upgrade be the cause?

Code:

root@jellyfin:/var/log/jellyfin# apt update
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease                                                                     
Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]                                                   
Hit:4 https://downloads.plex.tv/repo/deb public InRelease                                                 
Get:5 https://repo.jellyfin.org/debian bullseye InRelease [6,663 B]                                       
Fetched 50.7 kB in 1s (54.3 kB/s)   
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
root@jellyfin:/var/log/jellyfin# apt list --upgradable
Listing... Done
jellyfin/unknown 10.10.1+deb11 all [upgradable from: 10.9.11+deb11]
N: There is 1 additional version. Please use the '-a' switch to see it
root@jellyfin:/var/log/jellyfin# apt list --upgradable -a
Listing... Done
jellyfin/unknown 10.10.1+deb11 all [upgradable from: 10.9.11+deb11]
jellyfin/now 10.9.11+deb11 all [installed,upgradable to: 10.10.1+deb11]

root@jellyfin:/var/log/jellyfin# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  jellyfin
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
root@jellyfin:/var/log/jellyfin#

~R.

[TheDreadPirate]

I'd need to see more of the log than just the tail end.

Did you install Jellyfin manually? Not sure how else the source would be "unknown". What is the output of this command?

Code:

sudo apt list --installed | grep jellyfin

[Riesling]

Thank you Pirate,

jellyfin re-installed due to the issues w. the upgrade to 10.9 a month ago (see https://forum.jellyfin.org/t-inaccessibl...-10-9-11-0 )

Today the host of the proxmox VE had to be rebooted at ~18:00. VE is up, but jellyfin fails to start.

Code:

# apt list --installed | grep jellyfin

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

jellyfin-ffmpeg6/unknown,now 6.0.1-8-bullseye amd64 [installed,automatic]
jellyfin-server/unknown,now 10.10.1+deb11 amd64 [installed,automatic]
jellyfin-web/unknown,now 10.10.1+deb11 all [installed,automatic]
jellyfin/now 10.9.11+deb11 all [installed,upgradable to: 10.10.1+deb11]
#

Full log at https://pastebin.com/raw/rMF49t9i

Cheers,
~R.

[TheDreadPirate]

Code:

sudo apt purge jellyfin-ffmpeg6
sudo apt upgrade jellyfin

It's also possible your database is borked.

Code:

Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 1: 'no such table: ActivityLog'.

[Riesling]

Thank you Pirate,

did that, but no change, jellyfin starts and goes back to  "Active: inactive (dead)"

full session at https://pastebin.com/raw/sdu8RctD

Yes "Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 1: 'no such table: ActivityLog'." (How) can this be fixed?

[Riesling]

https://github.com/jellyfin/jellyfin/issues/12254 fixed it for me:

It's trying to do old migrations, setting IsStartupWizardCompleted to false in system.xml, start the server so it generates migrations.xml

It also survived a re-boot of the VE. Just asked a couple of questions, like user, password, country, language, etc. but it's running now. Puh. 

See you next month w. the next update, I guess. NOT! 

Cheers,
~R.