Chalk has automated processes that update core infrastructure passwords on a periodic basis.
At approximately 11:45pm PT, a scheduling error caused two instances of the process to run simultaneously. This caused the ‘old’ password to be dropped two times, leading to some api server instances being unable to connect to their database.
We’ve resolved the configuration error that permitted two instances of the job to run.
Monitors alerted our on-call engineer; the issue was root-cased and resolved via a restart of api server instances running with the ‘old’ password.