2024-11-10, 06:13 PM
Just spoke with Joshua. Is it the cleanup playlists and collections tasks? Try disabling that startup job.
2024-11-10, 06:13 PM
Just spoke with Joshua. Is it the cleanup playlists and collections tasks? Try disabling that startup job.
2024-11-23, 09:37 AM
(2024-11-10, 06:13 PM)TheDreadPirate Wrote: Just spoke with Joshua. Is it the cleanup playlists and collections tasks? Try disabling that startup job. My debug logs are basically 1:1 with psych0d0g. I tried disabling the "cleanup playlists and collections tasks" and it made no difference to the ~3 minute delay after "Closed connection to database 'main'" line. Here's my network.xml Code: <?xml version="1.0" encoding="utf-8"?>
2024-11-28, 03:29 PM
(This post was last modified: 2024-11-28, 03:42 PM by vodka. Edited 3 times in total.)
I've tried disabling every startup task, and it makes no difference.
I've noticed that the delay is remarkably consistent, it is almost always 178 seconds for me. I've done 6 restarts of JF while testing today, and 4 of them had a delay of 178 seconds at the exact same point as in the logs posted by psych0d0g. Two others were 180 seconds. I can't see this as being related to anything but EFCore considering where in the logs the delay occurs. Edit: I found a github issue with others having this same problem: https://github.com/jellyfin/jellyfin/issues/8787 Edit2: looking more into it, there seems to be a correlation between IOPS and this issue, moving the entire config folder to a much faster nvme storage device (and also avoiding the unraid filesystem layer) took down this delay from ~178 seconds to ~25 seconds. |
|
|