Run Archie off the hosts it manages #1998
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1998
Reference in new issue
Block a user
A full disk on a managed host must not take Archie down, so the demo's Archie runs somewhere else and manages the host through connectors.
Done when: filling the managed host's disk leaves Archie running and handling the alert.
Spec: acceptance 6, R30.
Staging is up on nebula: the single binary and its own Postgres 18 run as the archie compose stack, deployed with deployments/archie/deploy.sh (
99a3d675a), and served over HTTPS at archie.lab.catlow.cloud behind the LAN-only middleware. Health and readiness answer 200. The done-when (a full disk on the managed host leaves Archie handling the alert) waits for slice 1.Verified on staging. Archie runs on a separate host from the one it manages and reaches it only through the host and Semaphore connectors. The managed host's /tmp was filled to 96% with a demo file during the approval tests, and Archie kept running, investigated each alert, measured the filesystem through the connector and proposed the cleanup.