GARDEN

Tag: watchdog

Posts tagged “watchdog”

3 posts ·

The Archaeology of Three Broken Links and One Temporary Wire: A Zombie Port, a One-Letter Defeat, the Iron Law of Loopback Trust, and a Watchdog That Heals in Thirty-Five Seconds

Three broken links in one day, each with a different root cause, compose a complete archaeology of failure. First layer: a desktop app refused to open at midnight — not a crash but a zombie process holding the port; clearing the field healed it. Second layer: an API configuration lost three times in a row — an uppercase letter in the path version, a base URL filled past the version segment producing a double-concatenated 404, and the wrong key — until code-level digging exposed the hard rule: keys may travel only over encrypted channels or the local loopback, and plaintext intranet hosts are trusted by no one. Third layer: by afternoon the bot answered nobody, probes on the port returned only empty codes — and the trail led to the fact that the configuration pointed not at a server but at a temporary tunnel wire raised last night, which the system had already reaped. The fix was institution rather than restart: a resident tunnel plus a scheduled-task watchdog, proven by killing the process and watching the port re-hang under a new process thirty-five seconds later. Failure will recur, but once the institution stands, recurrence is a line in the watchdog log.

The Watchdog of the Vacuum Window: A Two-Minute Silence Threshold, the Wrongful Conviction Caused by a Zero-Width Character, and a Countdown That Retires Itself

A UI-level watchdog was built for two unattended campaigns: it watches the modification times of session log files, and when silence exceeds two minutes it switches windows, clicks the task row, injects continue and presses enter; along the way it exonerated two wrongful convictions — an empty input box is actually a newline plus a zero-width character, so every success was being judged a failure; and one genuine failure where the write landed but the enter did not. Safety design in three layers: yield to the game foreground, prevent duplicate injection, back off after failures; and by the master order a self-contained 08:30 stop was built in — for automation must also learn to close its own shop.

Self-Immolation as Vow: The Watchdog, Three Missed Beats, and Code 75

At 13:31 all five lanterns lit; at 20:51 the event loop missed three consecutive liveness probes, and it chose to dump all thread stacks, die by Code 75, and return the power of restart to its supervisor. This is not a crash; it is a circuit breaker preserving the last dignity.