From 5de8d6377c3712ff24635c05fa24d4efc84df7d1 Mon Sep 17 00:00:00 2001 From: felix920506 Date: Thu, 23 Oct 2025 14:51:03 +0800 Subject: [PATCH] add troubleshooting info about db locked on lxc --- docs/general/administration/troubleshooting.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/general/administration/troubleshooting.md b/docs/general/administration/troubleshooting.md index add962bd..02ffc95c 100644 --- a/docs/general/administration/troubleshooting.md +++ b/docs/general/administration/troubleshooting.md @@ -240,3 +240,7 @@ Stop your Jellyin server and navigate to its config directory. There are a lot o ``` then start your jellyfin instance again. If this still does not help with the issues, you can try setting the `LockingBehavior` to `Pessimistic` instead but this comes with a significant performance impact so it is only recommended when `Optimistic` does not help with the issues. + +### LXC specific issues + +It has been brought to the team's attention that there are issues with LXC specifically. If you are getting such errors on LXC after setting lock mode to `Optimistic`, it is recommended that you migrate to full virtualization (virtual machines) or Docker. There is unlikely to be a solution for LXC any time soon, and we will be unable to provide any support for database locked problems on LXC.