Closed thisisusernameforgithub closed 3 years ago
zeripath
commented
3 years ago Please update gitea to the latest version - that is 1.12.5.
All of these cgroup threads are running git pack-objects. That is a child process of git gc
Gitea runs git gc regularly so these will be related to that.
thisisusernameforgithub
commented
3 years ago Please update gitea to the latest version - that is 1.12.5.
All of these cgroup threads are running
git pack-objects. That is a child process ofgit gcGitea runs git gc regularly so these will be related to that.
how can you get rid of such anomalous activity? it seems that these processes are started and not completed on time, but simply hang, creating a load
zeripath
commented
3 years ago You don't state what kind of system you are running on but git pack objects can hang if packs become too large for the available memory. That would require setting the global git settings for pack objects which are described in the git documentation.
In terms of these I suggest you bring down Gitea and run git gc on the repositories on the command line. (You can do this whilst Gitea is running if preferred - but you'll need to kill these broken child processes.)
thisisusernameforgithub
commented
3 years ago You don't state what kind of system you are running on but git pack objects can hang if packs become too large for the available memory. That would require setting the global git settings for pack objects which are described in the git documentation.
In terms of these I suggest you bring down Gitea and run git gc on the repositories on the command line. (You can do this whilst Gitea is running if preferred - but you'll need to kill these broken child processes.)
You don't state what kind of system you are running on
Thank you for the answer! What kind of system are you talking about?
my Gitea version: 1.12.3 my Git version: 2.22.0 my OS: Centos 7.8
zeripath
commented
3 years ago I mean are you running on a raspberry pi, a server with limited memory, over NFS or some sort of other slightly restricted case etc.
thisisusernameforgithub
commented
3 years ago I mean are you running on a raspberry pi, a server with limited memory, over NFS or some sort of other slightly restricted case etc.
this works on a hardware server with a normal amount of RAM and a normal processor. tell me how can i avoid hung processes and a large number of CGroups?
zeripath
commented
3 years ago I suspect that there is an issue with your git garbage collection.
... I suggest you bring down Gitea and run git gc on the repositories on the command line. (You can do this whilst Gitea is running if preferred - but you'll need to kill these broken child processes.)
Did you do the above?
thisisusernameforgithub
commented
3 years ago at the moment gitea has been active for almost 3 months and there are no crooked/frozen processes in the daemon branch (probably influenced by the update to version 1.12.3 and rescans of the database and repos after it) I think the problem is more irrelevant
service gitea status -l
Redirecting to /bin/systemctl status gitea.service
● gitea.service - Gitea (Git with a cup of tea)
Loaded: loaded (/etc/systemd/system/gitea.service; enabled; vendor preset: disabled)
Active: active (running) since Чт 2021-01-07 15:15:23 MSK; 2 months 17 days ago
Main PID: 11574 (gitea)
CGroup: /system.slice/gitea.service
├─ 4348 /opt/gitea/gitea serv key-196 --config=/opt/gitea/custom/conf/app.ini
├─ 4357 git-upload-pack tp/open.git
├─ 4358 /usr/libexec/git-core/git pack-objects --revs --thin --stdout --progress --delta-base-offset
└─11574 /opt/gitea/gitea web -c /opt/gitea/custom/conf/app.ini
мар 26 16:19:30 vm01.git gitea[11574]: [Macaron] 2021-03-26 16:19:30: Started GET /P/co.git/info/refs?service=git-upload-pack for 10.4.5.22
мар 26 16:19:30 vm01.git gitea[11574]: [Macaron] 2021-03-26 16:19:30: Completed GET /TP/co.git/info/refs?service=git-upload-pack 200 OK in 56.85053ms
мар 26 16:20:12 vm01.git gitea[11574]: [Macaron] 2021-03-26 16:20:12: Started GET /api/internal/serv/command/255/tp/fz?mode=1&verb=git-upload-pack for 127.0.0.1
мар 26 16:20:12 vm01.git gitea[11574]: [Macaron] 2021-03-26 16:20:12: Completed GET /api/internal/serv/command/255/tp/fz?mode=1&verb=git-upload-pack 20...9.806863ms
мар 26 16:20:12 vm01.git gitea[11574]: [Macaron] 2021-03-26 16:20:12: Started POST /api/internal/ssh/255/update/46 for 127.0.0.1
мар 26 16:20:12 vm01.git gitea[11574]: [Macaron] 2021-03-26 16:20:12: Completed POST /api/internal/ssh/255/update/46 200 OK in 2.650697ms
мар 26 16:20:15 vm01.git gitea[11574]: [Macaron] 2021-03-26 16:20:15: Started GET /api/internal/serv/command/196/tp/open?mode=1&verb=git-upload-pack for 127.0.0.1
мар 26 16:20:15 vm01.git gitea[11574]: [Macaron] 2021-03-26 16:20:15: Completed GET /api/internal/serv/command/196/tp/open?mode=1&verb=git-upload-pack... 9.68546ms
мар 26 16:20:16 vm01.git gitea[11574]: [Macaron] 2021-03-26 16:20:16: Started POST /api/internal/ssh/196/update/19 for 127.0.0.1
мар 26 16:20:16 vm01.git gitea[11574]: [Macaron] 2021-03-26 16:20:16: Completed POST /api/internal/ssh/196/update/19 200 OK in 2.981946ms
after 2 months of continuous running gitea i see the following:
After restarting gitea, the situation has improved
my top -H
What can be wrong? Why is CGroup growing so: /system.slice/gitea.service
And a large number of threads - 418 sleeping & 12 zombie