verm__ changed the topic of #buildbot to: A Software Freedom Conservancy Project | Buildbot-3.5.0 | docs: http://docs.buildbot.net/current/ | tutorial: http://docs.buildbot.net/current/tutorial | irclogs: https://libera.irclog.whitequark.org/buildbot
glogan has quit [Ping timeout: 268 seconds]
glogan has joined #buildbot
flx[m] has quit [Quit: Bridge terminating on SIGTERM]
glogan has quit [Quit: Bridge terminating on SIGTERM]
flx[m] has joined #buildbot
vext01 has joined #buildbot
<vext01> hi everyone
glogan has joined #buildbot
<vext01> we had a OOM situation on our CI server today
<vext01> i did a soft reboot via the management console, but upon coming back up, buildbot isn't firing off builds any more
<vext01> when i force a build, it gets stuck as a build request
<vext01> master log adds one line:
<vext01> 2022-09-26 11:15:34+0100 [-] added buildset 3164 to database
<vext01> i wonder if the db is corrupted
<vext01> any ideas what i can try please?
<vext01> seems the workers are in a mess
<vext01> the web ui says they are present, but they are not
<vext01> and they wont restart due to a stale pid file
<vext01> weird
mjw has quit [Killed (NickServ (GHOST command used by wielaard!~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440))]
wielaard is now known as mjw
mark_ has joined #buildbot
mjw has quit [Killed (NickServ (GHOST command used by mark_!~mark@gnu.wildebeest.org))]
mark_ is now known as mjw
wielaard has joined #buildbot