SOLVED: Server won't run after upgrade

[FatherMcGruder]

I was able to use my Jellyfin server without issue yesterday evening. This morning I ran an update, jellyfin:amd64 (10.10.1+ubu2404, 10.10.2+ubu2404) according to /var/log/apt/history.log, and now the server won't stay up for more than a minute or so. I'm not sure if it is even really up because I cannot access it with the browser. If I run sudo systemctl restart jellyfin and then sudo systemctl status jellyfin, I get the following:

Code:

● 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: active (running) since Mon 2024-11-18 19:17:21 EST; 59s ago
  Main PID: 18724 (jellyfin)
      Tasks: 16 (limit: 19089)
    Memory: 926.9M (peak: 1.0G)
        CPU: 11.711s
    CGroup: /system.slice/jellyfin.service
            └─18724 /usr/bin/jellyfin --webdir=/usr/share/jellyfin/web --ffmpeg=/usr/lib/jellyfin-ffmpeg/ffmpeg

Nov 18 19:17:22 El-Savior jellyfin[18724]: [19:17:22] [INF] Filtered interface addresses: ["127.0.0.1", "192.168.0.235"]
Nov 18 19:17:22 El-Savior jellyfin[18724]: [19:17:22] [INF] Bind Addresses ["0.0.0.0"]
Nov 18 19:17:22 El-Savior jellyfin[18724]: [19:17:22] [INF] Remote IP filter is Allowlist
Nov 18 19:17:22 El-Savior jellyfin[18724]: [19:17:22] [INF] Filtered subnets: []
Nov 18 19:18:21 El-Savior jellyfin[18724]: [19:18:21] [INF] Loaded plugin: TMDb 10.10.2.0
Nov 18 19:18:21 El-Savior jellyfin[18724]: [19:18:21] [INF] Loaded plugin: Studio Images 10.10.2.0
Nov 18 19:18:21 El-Savior jellyfin[18724]: [19:18:21] [INF] Loaded plugin: OMDb 10.10.2.0
Nov 18 19:18:21 El-Savior jellyfin[18724]: [19:18:21] [INF] Loaded plugin: MusicBrainz 10.10.2.0
Nov 18 19:18:21 El-Savior jellyfin[18724]: [19:18:21] [INF] Loaded plugin: AudioDB 10.10.2.0
Nov 18 19:18:21 El-Savior jellyfin[18724]: [19:18:21] [INF] Applying migration 'RemoveDuplicatePlaylistChildren'

And then:

Code:

○ 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: inactive (dead) since Mon 2024-11-18 19:18:22 EST; 1min 8s ago
  Duration: 1min 1.066s
    Process: 18724 ExecStart=/usr/bin/jellyfin $JELLYFIN_WEB_OPT $JELLYFIN_FFMPEG_OPT $JELLYFIN_SERVICE_OPT $JELLYFIN_NOWEBAPP_OPT $JELLYFIN_>
  Main PID: 18724 (code=exited, status=0/SUCCESS)
        CPU: 12.742s

Nov 18 19:18:22 El-Savior jellyfin[18724]:    at Jellyfin.Server.Migrations.MigrationRunner.PerformMigrations(IMigrationRoutine[] migrations,>
Nov 18 19:18:22 El-Savior jellyfin[18724]:    at Jellyfin.Server.Migrations.MigrationRunner.Run(CoreAppHost host, ILoggerFactory loggerFactor>
Nov 18 19:18:22 El-Savior jellyfin[18724]:    at Jellyfin.Server.Program.StartServer(IServerApplicationPaths appPaths, StartupOptions options>
Nov 18 19:18:22 El-Savior jellyfin[18724]: [19:18:22] [INF] Running query planner optimizations in the database... This might take a while
Nov 18 19:18:22 El-Savior jellyfin[18724]: [19:18:22] [INF] Disposing CoreAppHost
Nov 18 19:18:22 El-Savior jellyfin[18724]: [19:18:22] [INF] Disposing MusicBrainzArtistProvider
Nov 18 19:18:22 El-Savior jellyfin[18724]: [19:18:22] [INF] Disposing MusicBrainzAlbumProvider
Nov 18 19:18:22 El-Savior jellyfin[18724]: [19:18:22] [INF] Disposing PluginManager
Nov 18 19:18:22 El-Savior systemd[1]: jellyfin.service: Deactivated successfully.
Nov 18 19:18:22 El-Savior systemd[1]: jellyfin.service: Consumed 12.742s CPU time, 1.0G memory peak, 0B memory swap peak.

Here is the output of sudo journalctl -u jellyfin -n 200 --no-pager if that is useful.

Any idea how I can fix this problem? I'm wondering if there's a way for me to just roll back to 10.10.1.

[theguymadmax]

There was a bug in the previous build, but a fix has been implemented and will be included in the next release.

[FatherMcGruder]

There was a bug in the previous build, but a fix has been implemented and will be included in the next release.

Thank you! Someone shared a workaround in that thread which helped me get up and running again. Their instructions were to edit 'config/migrations.xml', but for me it was '/etc/jellyfin/migrations.xml'.