![]() |
"Could not start Jellyfin server process after the specified wait period." - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: "Could not start Jellyfin server process after the specified wait period." (/t-could-not-start-jellyfin-server-process-after-the-specified-wait-period) Pages:
1
2
|
RE: "Could not start Jellyfin server process after the specified wait period." - b4ttlesnake - 2024-07-08 (2024-06-20, 01:06 PM)TheDreadPirate Wrote: Can you share the contents of migrations.xml? I am having this exact same problem. This is the new migrations.xml generated after deleting the corrupted one. Server still not starting. Code: <?xml version="1.0" encoding="utf-8"?> RE: "Could not start Jellyfin server process after the specified wait period." - TheDreadPirate - 2024-07-09 Also try renaming system.xml and let it regenerate from defaults. RE: "Could not start Jellyfin server process after the specified wait period." - Al Imran - 2024-11-27 I deleted all the files in the config folder with the xml files and it worked RE: "Could not start Jellyfin server process after the specified wait period." - chaos2go - 2025-04-08 Good evening I have the same problem. Unfortunately, deleting the files does nothing for me log file --> https://pastebin.com/R87Hq5rL cheers and thanks chaos RE: "Could not start Jellyfin server process after the specified wait period." - TheDreadPirate - 2025-04-08 (2025-04-08, 08:29 PM)chaos2go Wrote: Good evening You're running the unstable, still in development, build of Jellyfin. I have no way to tell if this is a legit problem or a bug. I'm leaning towards a bug Regardless, post to the jellyfin git hub. https://github.com/jellyfin/jellyfin/issues RE: "Could not start Jellyfin server process after the specified wait period." - theguymadmax - 2025-04-08 (2025-04-08, 08:29 PM)chaos2go Wrote: Good evening Version 10.11 is an unstable build and should only be used for testing purposes. Inter-unstable versions may not always be compatible. To resolve any issues, restore a 10.10.x backup, then reinstall the latest 10.11 unstable build. If the problem persists, then you can report it. https://jellyfin.org/posts/efcore-refactoring-incoming/: "The downside of this is, though, that we might not be able to cleanly implement unstable-to-unstable migrations in a way that will work properly. While we will try to do this, we cannot guarantee it." "Fifth and finally, if you have a failing migration, restore an older database version first and try to re-run it. If it still fails, try your oldest (ideally, 10.9.11 or 10.10.0 stable) backup as well. If that one doesn't work, it's a new bug to report." RE: "Could not start Jellyfin server process after the specified wait period." - chaos2go - 2025-04-09 thanks for your Replay , yes i know . I tried it first with the new Final release and hat the same Problem . Found the Issue ... Had duplicates in the migrated DB Make A copy of the DB file in "C:\ProgramData\Jellyfin\Server\data" use https://sqlitebrowser.org/ --> DB Browser --> open DB file to work with SELECT Type, Value, COUNT(*) as Anzahl FROM ItemValues GROUP BY Type, Value HAVING COUNT(*) > 1; Search for entries who ar dublicated SELECT ROWID, Type, Value FROM ItemValues WHERE Type = 3 AND Value = 'Dublicate Value entry '; as example in my case SELECT ROWID, Type, Value FROM ItemValues WHERE Type = 3 AND Value = 'Ay Yapım'; Next step, delete duplicated ROWID DELETE FROM ItemValues WHERE ROWID = one Value of a dubplicatet ROWID here; example DELETE FROM ItemValues WHERE ROWID = 125; now you can check again with SELECT Type, Value, COUNT(*) as Anzahl FROM ItemValues GROUP BY Type, Value HAVING COUNT(*) > 1; repeat for each duplicatet value safe and make sure that the name of DB file is correct --> start jellyfin again. give him a bit time to run "i thought it didn't work, my brother said in the morning he couldn't find the new files ... ![]() so now I did a new scan of the libraries and everything is back to normal. " cheers , hope it helps others too. and thanks for the cool community |