[OSGeo] #3236: gitea went down and did not come back up

Committees SAC tickets
1

#3236: gitea went down and did not come back up
----------------------+--------------------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-I
Component: SysAdmin | Keywords:
----------------------+--------------------------------------
I assume same issue out of postgresql connections. trac had gone down too
but appeared to come back on it's own.

Both went down 5:35 AM UTC, but trac came back up on it's own around 6 AM
UTC.

I just restarted gitea, but has been down since 5:35 AM UTC
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3236&gt;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

2

#3236: gitea went down and did not come back up
----------------------+---------------------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: new
Priority: normal | Milestone: Sysadmin Contract 2024-I
Component: SysAdmin | Resolution:
Keywords: |
----------------------+---------------------------------------
Comment (by robe):

actually I take that back a bit trac has been up and down, but mostly up.

The 10 cpus allocated to tracsvn container also seem to be pretty maxed
out at the moment

and I'm seeing a bunch of git processes running presumably triggered by
gitea
--
Ticket URL: <#3236 (gitea went down and did not come back up) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

3

#3236: gitea went down and did not come back up
----------------------+---------------------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: closed
Priority: normal | Milestone: Sysadmin Contract 2024-I
Component: SysAdmin | Resolution: fixed
Keywords: |
----------------------+---------------------------------------
Changes (by robe):

* status: new => closed
* resolution: => fixed

Comment:

Looking at the past month of activity on tracsvn, looks like it's been
spiking often to 100% CPU, but memory usage has been staying stead at
14-16GB.

I've for now increased allocated cpus from 10 to 14.

I'm going to close this one out for now.
--
Ticket URL: <#3236 (gitea went down and did not come back up) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.