There was a PG::ConnectionBad issue in the web container, and this is the first time I’ve encountered this issue, though the database itself was running normally. I’ve restarted the web containers, and the issue has been resolved, as I received the confirmation email. However, this issue could potentially happen again. A possible solution would be to add a liveness checker to monitor the database connection in addition to the existing liveness checker we have for Apache verification.
Rub21
commented
3 weeks ago
From: https://discord.com/channels/413070382636072960/634106496560398349/1284581061933793280
Bug description
There was a PG::ConnectionBad issue in the web container, and this is the first time I’ve encountered this issue, though the database itself was running normally. I’ve restarted the web containers, and the issue has been resolved, as I received the confirmation email. However, this issue could potentially happen again. A possible solution would be to add a liveness checker to monitor the database connection in addition to the existing liveness checker we have for Apache verification.
logs: https://gist.github.com/Rub21/8558a611b0e7ef879ebed5791a5d3f6a
cc. @1ec5 @danrademacher @batpad