-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gitea crashes on startup after running "Delete all repository archives" (view logs) #11754
Comments
Does anyone have any idea of perhaps resetting something that way I could get gitea back up and running?? I am running the Gitea instance in Docker and I also have complete access to the external MySQL database which Gitea uses. |
It seems that Gitea crashes after running "Delete all repository archives". Is there a way to stop that? |
I'll close this as no one seems to see this... ;''/ |
I may have an idea of what is happening. As such I will re-open. When starting Gitea, can you look at memory consumption? |
Edit: This assumption I made was incorrect. |
@techknowlogick Thanks for reopening the issue. I've applied the settings you've just talked about. Since I'm running Gitea in docker, I couldn't view the memory usage as Gitea would just crash right away when I start it; meaning I couldn't view the memory usage. Side Note: I'm running this docker container on a home server running Debian Buster that only has 16GB of ram. Below is what the
|
Also, would it be possible to potentially transplant the data from the current Gitea container to a new one? I don't mind if I lose some data as I have a copy of all the repositories except for the settings. |
@Nathan13888 are you still getting the same panic?
have you actually looked at the code for: gitea/modules/setting/database.go Line 108 in 4a4977a
Looking at your provided app.ini: ...
[database]
PATH = /data/gitea/gitea.db
DB_TYPE = mysql
USER = gitea
PASSWD = **OMITTED**
SCHEMA =
SSL_MODE = disable
CHARSET = utf8mb4
[indexer]
... I see that HOST is not set. We don't provide a default: gitea/modules/setting/database.go Line 73 in 4a4977a
Therefore your problem is that you haven't set a HOST |
Hi @zeripath, you were right about the After these changes, the container no longer crashes instantly but after half a minute. There are no details in the Docker log but I found this in the log within the container (view the end of the message). I also compared an old working version of the config and there seems to have no more differences from the current config. From the logs, it seems that Gitea is unable to communicate with MYSQL but the mysql container has been running non-stop for a month or two already without problems and haven't been changed by me either.
|
Btw, I retried multiple times and have come to the same error in the log |
Gitea cannot connect to your database. You need to check the rest of your config. I suspect the hint is here: But that's very unlikely to the name of the Gitea database. (The default is I suggest you check the results of |
v1.13.0+dev-117-ga3b185d54
2.20.1 (for host)
Docker (Debian Buster)
[x]
):Description
Gitea worked perfectly fine before I changed some settings under the
server
section inapp.ini
. After I noticed this crashing, I immediately changed all the settings back to the original settings but the same problem would arise. I'm not sure but I believe that this would have happened even if I didn't change these settings.app.ini
:app.zip
Log from inside the Gitea container:
gitea.log
Log before crashing (in docker)
:
The text was updated successfully, but these errors were encountered: