mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
System shutdown itself after library scan jellyfin/jellyfin:10.8.0-alpha5-amd64 [Issue]: #3502
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 @0TTA on GitHub (Jan 6, 2022).
Please describe your bug
It works without problems, but when I manually scan the library, it scans it, and then the container shutdown itself. It works fine, though, after I manually rerun the container.
Jellyfin Version
Other
if other:
10.8.0-alpha5
Environment
Jellyfin logs
No response
FFmpeg logs
No response
Please attach any browser or client logs here
No response
Please attach any screenshots here
No response
Code of Conduct
@wolonggl commented on GitHub (Jan 6, 2022):
If you scan a large number of library video files, the ubuntu version has the same problem. The scanning process freezes and the Web page does not respond.
@0TTA commented on GitHub (Jan 7, 2022):
Yeah, I'm on unRAID. I had some issues too with HDR transcoding, so, I pull back to alpha3.
@NotExpectedYet commented on GitHub (Jan 8, 2022):
Have this on UnRaid myself. Interface becomes unresponsive on a scan.
@0TTA commented on GitHub (Jan 8, 2022):
Fixed on jellyfin/jellyfin:20220107.9-unstable
@jellyfin-bot commented on GitHub (May 9, 2022):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.