6 Commits

Include renames

Author	SHA1	Message	Date
jochen	b62bb15839	Say which provision five consumers' checks exercise, so a database down is one condition (hq issue 145) ... gitea, nextcloud, umami and n8n gain an http check that reaches their database through their own endpoint; mesh-knowledge's watch already asks the database and now names it. While postgres is unhealthy, their findings are held under its condition instead of raising one each.	2026-10-14 03:21:53 +02:00
jochen	93d58f3740	fail2ban: never ban the operator's own addresses, and say a failure from one (hq issue 238, ADR 0339) ... An agent polling the forge from the operator's home got that home banned for a day and then four weeks, and nothing in the house reached the control-node. Every jail spared only private ranges. The mesh-wide setting own-addresses reaches the machine as a mergeable file whose own content is the empty list, so the module composes while it is unset. A new watch process (root) writes its entries into a list every jail's base ignoreip names as file:, which fail2ban reloads without a restart; it checks every jail names that list and keeps each failure a jail ignored because of it for a day. The new fail2ban_health tool judges the watch, so the controller raises a warning naming node, jail, address and count. The ban verb refuses an address on the setting or on the jail's ignore list before the daemon is asked.	2026-10-13 10:54:49 +02:00
jschoubben	d09dbe33ac	Say how the build agent and the route proxy are ready (novox/hq issue 544) ... Neither server declared health, so each walk that moved them waited out the 60 s grace on every machine. The build agent is ready when 'mesh-builder ready' says it took its build work; the route proxy when its http port accepts.	2026-10-12 21:33:13 +02:00
jschoubben	2b2397abe0	dnsmasq: ask the resolver a real question, and restart it when it stops answering (hq issue 348) ... On 2026-10-09 the control node's dnsmasq stayed active and running, its journal silent, and refused every question on its private address for twenty minutes; nothing in the module looked past the unit. The module is now Go (its TypeScript tools were never served): a root watch asks the machine's own name on every listen address over UDP and TCP every 15s, restarts the unit after two failing looks (2 min apart, 3 an hour), and says whether that helped. dnsmasq_health is the watch process's declared check, so a restart that did not help becomes the module's unhealthy condition; the service is judged by its unit.	2026-10-09 15:04:45 +02:00
jochen	f87f4cdfe5	Say how the first twenty-three long-running resources are ready (hq ADR 0240, to-be 48 Phase E) ... Seven modules' images ship a check the mesh never read. Adopted by name where it says healthy on the live mesh today: nine of mail's containers (not its antivirus, whose six-minute start is past the five-minute bound, nor its cache, whose image ships none), the certificate authority, the spreadsheet app, four of the database suite's (the studio among them, with the address it binds fixed), the flow editor and the chat client. And the endpoints four services already declare, looked at from the machine: tcp on the database, the cache, the document store and the broker; http on the website and the dashboards. The count of undeclared falls from 93 to 70.	2026-10-07 18:47:58 +02:00
jochen	c0f9039695	Keep the count of long-running resources without health, and let it only go down (hq ADR 0240 rule 8) ... A field that is optional for ever is one half the catalogue never gets. The catalogue's merge check now holds the controller's count of long-running resources that do not say how they are ready to the number kept in health-undeclared: a change that raises it fails, one that lowers it must write the new number. Until the controller the mesh runs counts (Phase B), the check says it did not count.	2026-10-07 16:17:53 +02:00