+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: exited error 139 (/t-solved-exited-error-139)
exited error 139 - sp3ngl3r - 2025-09-29
Hello All,
I tried the preview build the other day and it was stuttering on mobile (same LAN, just WIFI). Everything else was working fine. However I tried to rollback to the latest release and now I cannot start the container at all. Both the latest and preview versions boot loop and ultimately exit on error code 139.
I cannot figure this one out via the logs (attached) and thought I'd ask here after a few hours of troubleshooting.
The recurring error is:
jellyfin | [11:06:03] [INF] [9] Jellyfin.Database.Implementations.Locking.NoLockBehavior: The database locking mode has been set to: NoLock.
jellyfin | [11:06:03] [INF] [9] Jellyfin.Server.Migrations.JellyfinMigrationService: Initialise Migration service.
jellyfin | [11:06:03] [INF] [9] Jellyfin.Server.Migrations.JellyfinMigrationService: Old migration style migration.xml detected. Migrate now.
jellyfin | [11:06:03] [FTL] [9] Jellyfin.Server.Migrations.JellyfinMigrationService: Failed to apply migrations
jellyfin | System.InvalidOperationException: Sequence contains no elements
jellyfin | at System.Linq.ThrowHelper.ThrowNoElementsException()
jellyfin | at System.Linq.Enumerable.Last[TSource](IEnumerable`1 source)
jellyfin | at Jellyfin.Server.Migrations.JellyfinMigrationService.CheckFirstTimeRunOrMigration(IApplicationPaths appPaths)
jellyfin | at Jellyfin.Server.Migrations.JellyfinMigrationService.CheckFirstTimeRunOrMigration(IApplicationPaths appPaths)
--thanks
System: Debian 12, on 12th gen i5-1235U, 12 cores (BeeLink EQ12)
Update: I moved the compose.yml to a new blank folder (with the cache + config, empty folders within) and it's looping too but with error 0.
RE: exited error 139 - theguymadmax - 2025-09-29
In the config folder, look for migrations.xml and rename to migrations.xmlbackup. Then retry the setup.
RE: exited error 139 - sp3ngl3r - 2025-09-29
This seems to work for getting the :preview back up and running. So thanks for that as I was DOA will all Jellyfin instances before. The XML looks valid to me though. Though this doesn't solve my ability to rollback to one that isn't jittery on mobile, but I'm up and running again so thanks for that.