ok so hackny.social went down again last night and I'm starting to do a bit more digging into what's going on. it looks like postgres got a SIGKILL around 1a UTC which also coincided with a spike in CPU usage...
ok so hackny.social went down again last night and I'm starting to do a bit more digging into what's going on. it looks like postgres got a SIGKILL around 1a UTC which also coincided with a spike in CPU usage...