Opened 5 months ago
Closed 5 months ago
#3236 closed task (fixed)
gitea went down and did not come back up
Reported by: | robe | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | Sysadmin Contract 2024-I |
Component: | SysAdmin | Keywords: | |
Cc: |
Description
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
Change History (2)
comment:1 by , 5 months ago
comment:2 by , 5 months ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
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.
Note:
See TracTickets
for help on using tickets.
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