mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-07-16 05:43:54 +03:00
Server crashed while scanning library #6508
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @simon-kolkmann on GitHub (Nov 24, 2024).
This issue respects the following points:
Description of the bug
I was moving and renaming some files in my library while Jellyfin was scanning said library. Suddenly the server crashed completely.
Reproduction steps
What is the current bug behavior?
The library scan failed spectacularly with a fatal error that brought the server down.
What is the expected correct behavior?
Jellyfin should probably not crash completely - maybe the item could be skipped, maybe the library scan should be aborted. But the server should stay online.
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.10.3
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
No response
Additional information
No response
@felix920506 commented on GitHub (Nov 24, 2024):
Please provide a complete list of plugins
@simon-kolkmann commented on GitHub (Nov 24, 2024):
Sure!
@gnattu commented on GitHub (Nov 24, 2024):
It appears that you are moving files around while the scan is still in progress, which could lead to undefined behaviors, including server crashes. Unfortunately, we can’t do much about this since the files are expected to remain constant throughout the entire scan process. You can add more files (might not get indexed if you do and may require start a scan task again), but you can’t move or delete any files. If the files are in the “to be processed” list and then removed, the server will definitely panic.
@simon-kolkmann commented on GitHub (Nov 25, 2024):
I thought that maybe the server could rather catch this kind of error instead of panicking. But if this is expected behaviour, feel free to close this issue.