gitea: Gitea crash loop every 2 minutes
Gitea Version
1.16.2
Git Version
2.30.2
Operating System
k3s
How are you running Gitea?
Running on Kubernetes v1.22.6+k3s1 with the docker.io/gitea/gitea:1.16.2 image
Database
PostgreSQL
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
REMOVED
Description
Gitea crashes every 1-2 minutes. All crashes end with [F] Unable to create internal queue for XXX Error: Unable to create queue level for XXX with cfg ... in the logs
Screenshots
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 17 (17 by maintainers)
Commits related to this issue
- Adjust error for already locked db and prevent level db lock on malformed connstr This PR adjusts the error returned when there is failure to lock the level db, and permits a connections to the same ... — committed to zeripath/gitea by zeripath 2 years ago
- Adjust error for already locked db and prevent level db lock on malformed connstr (#18923) This PR adjusts the error returned when there is failure to lock the level db, and permits a connections to... — committed to go-gitea/gitea by zeripath 2 years ago
- Adjust error for already locked db and prevent level db lock on malformed connstr (#18923) Backport #18923 This PR adjusts the error returned when there is failure to lock the level db, and permits ... — committed to zeripath/gitea by zeripath 2 years ago
- Adjust error for already locked db and prevent level db lock on malformed connstr (#18923) (#18938) Backport #18923 This PR adjusts the error returned when there is failure to lock the level db, a... — committed to go-gitea/gitea by zeripath 2 years ago
- Adjust error for already locked db and prevent level db lock on malformed connstr (#18923) This PR adjusts the error returned when there is failure to lock the level db, and permits a connections to... — committed to Chianina/gitea by zeripath 2 years ago
Cool. I think we can close this. Sorry it took me so long to get involved.
The logs were saying that the issue was the level db was temporarily unavailable - which is code for it can’t get a LOCK on the db - and it was pointing to the directory but I guess that this isn’t completely clear. I guess the question is whether can do more to make things clearer.
There are a couple of reasons why a lock can’t be taken - but I guess we could just detect this error and try to suggest a few things.
I’ll close this issue though.