Vigil: the site answers is failing

fixedopened 26 days agodown 2m

what the check said

the site answers — expected 200, got 502

Warden’s diagnosis · 95% sure of the cause

vigil is down because pm2 shows the `vigil` process in status "stopped" — not errored, not crash-looping, just stopped. pm2_list reports "vigil | stopped | restartsSinceAdded: 14 | lastStartedAt: 2026-09-14T09:28:12.833Z", which matches the failure: a stopped process is not listening on :3100, so the site probe gets a 502. The error log for vigil is empty, and the out log shows a trail of clean Next.js "Ready in ~Xms" banners — no stack trace, no OOM, no deploy-induced crash. The most recent commits (36a05c0 docs, 4c945ec social card, 6fad866 safety-net fix) landed after 09:28 and are docs/assets, not running code. No recent code change is plausibly responsible. Per the owner's standing policy ("Restart it if it is just stopped"), the fix is `pm2_start vigil` (or `pm2_restart vigil`) — both are on the allow-without-asking list.

suspect · vigil pm2 process (stopped)

Done

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.

Everything it ran10 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	181
read the log `pm2_logs`	looks only	did ityou allowed it	pm2 logs vigil --lines 80 (errors only)	183
read the log `pm2_logs`	looks only	did ityou allowed it	pm2 logs vigil --lines 120	206
read a file `read_file`	looks only	did ityou allowed it	read_file	1
read the log `pm2_logs`	looks only	did ityou allowed it	pm2 logs vigil --lines 200	186
search the code `grep_repo`	looks only	did ityou allowed it	grep_repo	0
read the log `pm2_logs`	looks only	did ityou allowed it	pm2 logs vigil-out.log --lines 80	173
read the log `pm2_logs`	looks only	did ityou allowed it	pm2 logs vigil --lines 80	232
read recent commits `git_log`	looks only	did ityou allowed it	git log -n 10	9
start the process `pm2_start`	undoes itself	did ityou allowed it	start vigil	253

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.