Vigil: the site answers is failing
fixedopened 26 days agodown 60s
what the check said
the site answers — expected 200, got 502
Warden’s diagnosis · 85% sure of the cause
vigil is down because the process is stopped. pm2_list shows vigil status="stopped", lastStartedAt 2026-09-14T09:47:13.844Z — it died between the last passing check at 10:11:52 and now (10:12:27), which is exactly the 502 the symptom describes. No stack trace to quote: the error log is empty (vigil-error.log last 120 lines: blank in the pm2 tail), and stdout only shows clean Next.js startup cycles ("✓ Ready in ~1000ms") repeating with no exception, OOM line, or signal. So I cannot name the trigger of the stop from logs alone — it was silent. This is a public site; the owner says "restart it if it is just stopped," pm2_restart is on the permitted list, and the last passing check was one minute ago. Looks like the recurring "fleet bounce" in the standingRules. A restart is the right next act; if it dies again immediately with no logged error, look at commits 6fad866 (10:53) and 503accd (07:52) — they bracket when this started getting unhealthy.
suspect · pm2 process "vigil" (stopped, no error trace)
This one was worked before you opened the page, so there is nothing to watch live. Everything it did is in Everything it ran below, with the exact command and the rule that permitted each one — that table is the record, and this timeline is only the same thing arriving in real time.
vigil is down because the process is stopped. Fixed, and the check that failed passes again.
Everything it ran6 calls · 1 changed something
Warden has no shell. Each row below is one named action from a fixed list, spawned without a shell, with the rule of yours that permitted it. Copy any command and run it yourself.
| what | how safe | your rule | command | ms |
|---|---|---|---|---|
list the processes pm2_list | looks only | did ityou allowed it | pm2 jlist | 177 |
read the log pm2_logs | looks only | did ityou allowed it | pm2 logs vigil --lines 120 (errors only) | 196 |
read the log pm2_logs | looks only | did ityou allowed it | pm2 logs vigil --lines 200 | 197 |
read a file read_file | looks only | did ityou allowed it | read_file | 0 |
read recent commits git_log | looks only | did ityou allowed it | git log -n 15 | 12 |
start the process pm2_start | undoes itself | did ityou allowed it | start vigil | 371 |
This incident is marked resolved because the site answers — the same check that failed — was run again and passed. Nothing Warden believed about its own fix could have closed it.