-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Issues to start gitea with MariaDB since last update #33714
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
Comments
I could imagine that the recently added database transaction increased the database workload of fetchTask on your system.
|
TBH I do not think it could be the case, a transaction is quite lightweight in most cases and it shouldn't make a SQL run that long Below is outdated, see next comment.
I guess there is something wrong with the SQL or the data/index in database. I think something like:
(status "running" = 6) could help to explain the problem. |
And one more thing, maybe it is not related to the "Actions" SQL. I can see there are various different SQLs in the slow log, like this:
I think it's better to see what happens on MariaDB side. Is it running a lot of SQLs concurrently? Is there any bottleneck from network or disk? Or is the MariaDB itself is quite busy? What causes the MariaDB's heavy load? What does MariaDB's slow query log say? |
My MariaDB instantance is doing nothing, no load, also my homelab server as 4 cores, 16 Gb of RAM, CPU load avg is always under 2, and RAM usage is always under 55% I'm getting other SQL error at statrup like
Unless something has changed in the latest Docker 28 update regarding networking, which I doubt, as my Zabbix server under docker is able to connect to my MariaDB instance. |
If you downgrade to 1.23.3, does the problem still exist? |
Yes I downgraded down until 1.22, problem still persists |
So I would still suggest you to check your other services including MariaDB, it doesn't seem to be a Gitea's problem. |
Well, it looks like there's no issue with my MadiaDB container, I double checked and it works OK with my other phpmyadmin and zabbix server containers. |
I'm having plenty of these errors in MariaDB logs
I also used the gitea db username/password to connect through phpmyadmin (which is also in a docker container) and all works OK. Also double checked the db IP, port, username, password... in the app.ini file and all looks OK |
Issue fixed by moving the gitea docker container from bridge network to host network, it was working OK for ages on the bridge network. Probably a recent change from Docker v28 Still doesn't explain why phpmyadmin which is still running OK on the bridge network Well, not entirely fixed, I'm now having an issue with SSH_LISTEN_PORT not being taken into account, SSH still trying to use port 22, where my app.ini has
|
Switched back to bridge network and came back up and running again |
I'm curious how did you resolve your problem. |
Description
I'm having issues with my gitea instance, running with Docker since last gitea update 1.23.3 to 1.23.4 (watchtower doing the auto updates)
Gitea is starting, I see logs with slow SQL queries, and it ends up with a timeout error
The MariaDB instance is also running with Docker, and it's working OK, no issues whatsoever to access the gitea DB
Gitea Version
1.23.4
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
Debian/Docker
How are you running Gitea?
Official Gitea Docker image docker.io/gitea/gitea:latest
Database
MySQL/MariaDB
The text was updated successfully, but these errors were encountered: