I've been working on getting some better monitoring and log aggregation set up so I can troubleshoot what is actually happening but it's a bit slow going. As of now I can't tell if the database is getting overloaded, if the frontend is getting spammed, or what is going on really.

My instance has two users and it runs on a VPC with 2 CPUs and 4GB of RAM.

[–] jivandabeast@lemmy.browntown.dev 4 points 9 months ago* (last edited 9 months ago) (1 children)

lock up my entire server until i reboot

Check the ram usage on postgres. Theres a memory leak issue thats being monitored with a proposed fix in the next version (which is upgrading to the newer version of postgres)

[–] Toribor@corndog.social 2 points 9 months ago (1 children)

Thank you! I was secretly hoping someone might have a quick suggestion of something to try. I'll see what I can find out.

[–] jivandabeast@lemmy.browntown.dev 2 points 9 months ago (1 children)

Yeah no problem! My workaround solution is simply just restarting the postgres container when i notice ram usage spiking

[–] Toribor@corndog.social 1 points 9 months ago

Usually by the time I notice the server is already unreachable over SSH but I've been considering adding manual healthchecks to my containers. Paired with the docker-autoheal project it's been a really low effort way for me to keep services healthy without a lot of babysitting. I'm more nervous about implimenting it for something like a stateful database though, but I suppose it's no different than manually issuing a docker restart command.