mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Busy: Database is locked #1445
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 @Lilja on GitHub (Mar 26, 2020).
Describe the bug
Starting a docker container from linuxserver/jellyfin creates a
busy: Database is lockedSystem (please complete the following information):
To Reproduce
Expected behavior
Logs
Click to expand
Additional context
Docker-compose
.env file
@Lilja commented on GitHub (Mar 27, 2020):
/mnt/Softwareis a SMB share from my NAS. Mounted on the host.Switched to a local path for the drive and it seems to work.
I had the same issue for running a postgres container and it turned out a similar issue.
@Artiume commented on GitHub (Mar 28, 2020):
You shouldn't attempt to run a sqlite database over a network. That's gonna cause a bad day.
@Lilja commented on GitHub (Mar 29, 2020):
Well, I like the thought that the config is persisted somewhere so if the VM dies it's actually saved somewhere else.
How can I achieve that without writing cronjobs with something like rsync to run every x hours?
@Artiume commented on GitHub (Mar 29, 2020):
@joshuaboniface you have any ideas?
@dkanada commented on GitHub (Mar 29, 2020):
This is the generally accepted way to handle backups, so I feel like that is what Josh will suggest. We could potentially move the database to another location in the future so you can avoid that in the remote mount but I don't expect this any time soon. I'll close this issue for now though, since the issue itself has been resolved.