[Issue]: Jellyfin libraries don't resist reboot / library rebuild is finnicky

[maurocolella]

Please describe your bug

Hi. First of all, Jellyfin is stunning. Wish I could contribute more.

Second: I have had this problem twice so far, within just a few days.

I run the official Jellyfin container on Docker (Portainer) via docker compose, on top of Manjaro.

I use watchtower to update containers automatically, a bind mount to keep configurations, and BTRFS.

The first time, watchtower updated and restarted, I think Portainer itself, causing all my stacks to restart, and my library was shot. There still is a catalog of metadata and it seems correct, but I am unable to browse the library, for all purposes it shows empty.

I tried rescanning all libraries, this was a bit finnicky. Moving away from that web page, then coming back to it, or trying to restart the scan a few times didn't quite appear to produce the desired result.

This same situation has happened again this morning after a power outage.

Finally, I tried running the full library scan again patiently, keeping a browser tab open for it to run, and would you know? It worked.

Is it possible to implement some kind of auto-healing and/or integrity checks on the db?

Also, is the library rebuild task dependent upon UI? Is it something that could run decoupled, through some queue?

It's not too much of a snag, but there's a grey area.

Thanks.

Jellyfin Version

Other

if other:

10.8.4

Environment

- OS: Manjaro Linux 22.0.0 
- Virtualization: Docker
- Clients: Android, Android/Google TV, Linux (desktop), browser
- Browser: Chrome Version 105.0.5195.125 (Official Build) (64-bit)
- FFmpeg Version: ffmpeg version 5.1-Jellyfin
- Playback Method: ?
- Hardware Acceleration: N/A
- Plugins: None
- Reverse Proxy: Custom, Nging
- Base URL: via IP
- Networking:
- Storage:

Jellyfin logs

No new logs since outage. Logs end yesterday, no log output from rescan.

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[jellyfin-bot]

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.

[szszoke]

I seem to be having a similar problem, my libraries disappeared from Jellyfin after a server reboot. @maurocolella did you manage to find a solution to this problem?

[mdcayton]

Having the same issue. Every time the container is restarted Jellyfin thinks its starting from a fresh install.

[maurocolella]

Actually (and apologies for the belated reply), this wasn't a software issue in my case, but primarily due to docker starting before my file systems were mounted - hence bind mounts just weren't available.

When running in Docker, I reckon there is little if anything Jellyfin can do about that; although there might have been other issues at play.

This much was on me, and a problem with the underlying filesystem.