
The guard that approved because it could not see the process
A sandbox hid the central process PID, the config it read was the wrong file and the routes table arrived empty. The guard still said OK.
5 posts

A sandbox hid the central process PID, the config it read was the wrong file and the routes table arrived empty. The guard still said OK.

After the host move, the Capivara hub kept measuring 43 systemd units from the old machine — 26 of them were gone. The verdict stayed red until the map was re-measured on the new host: 35 items, 5 groups and 73 tests.

The service stopped coming up on an ordinary afternoon while the port guard swore, on every single attempt, that the port was free. 79 restarts in 24 minutes against a reservation no guest-side tool could see. The fix was to change the oracle.

The Arachne landing page loaded without CSS, the watchdog restarted the service in an invisible loop, and a zombie socat relay kept stealing the port from its rightful owner. Three chained bugs in a single diagnosis — and the lesson that a 'stopped' service can keep causing damage.

Under the hood of an 83% frontend refactoring: Ghost Components, silent schema drift, the two-systemd war, the phantom Umami proxy, and other pains that don't fit in a changelog.