The 2026-10-09 outage on the control node (10:57:57-11:18:12 UTC): symptom, timeline, what is measured and what is guessed, the reproduction of dnsmasq's bind-dynamic closing its listeners on a bridge teardown, and the fixes in review (mesh-controller #179, mesh-catalog #161).
Open for the operator: the dnsmasq watch restarts on health, which departs from ADR 0240 rule 6; why the second resolver did not serve the route proxy is still a guess (its container's resolver file, readable once docker_resolv_conf is delivered); a mesh-lab replay is owed before the issue resolves.
records, index, words and cycle pass locally. Not merged.
The 2026-10-09 outage on the control node (10:57:57-11:18:12 UTC): symptom, timeline, what is measured and what is guessed, the reproduction of dnsmasq's bind-dynamic closing its listeners on a bridge teardown, and the fixes in review (mesh-controller #179, mesh-catalog #161).
Open for the operator: the dnsmasq watch restarts on health, which departs from ADR 0240 rule 6; why the second resolver did not serve the route proxy is still a guess (its container's resolver file, readable once docker_resolv_conf is delivered); a mesh-lab replay is owed before the issue resolves.
records, index, words and cycle pass locally. Not merged.
jschoubben
force-pushed issues/348-the-resolver-stopped-answering-and-nothing-restarted-it from 8d75a37de5 to d6f889d0542026-10-09 11:51:47 +00:00Compare
Deliverynovox/hq@fbd00a16ca40 — delivered since 2026-10-09T13:25:45Z
Delivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
2026-10-09 13:06 (new) → proposed (announced): novox/hq#249's head announced
2026-10-09 13:06 proposed → checked (checked): the verdict names this commit
2026-10-09 13:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-09 13:25 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-09 13:25 published → delivered (done): nothing for a walk to move
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/hq@fbd00a16ca40` — **delivered** since 2026-10-09T13:25:45Z
**Delivery plan** — builds nothing: the change touches no module of the mesh's graph
**Transitions**
- 2026-10-09 13:06 (new) → proposed (announced): novox/hq#249's head announced
- 2026-10-09 13:06 proposed → checked (checked): the verdict names this commit
- 2026-10-09 13:06 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-09 13:25 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-09 13:25 published → delivered (done): nothing for a walk to move
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
Records the 2026-10-09 outage on the control node: what was measured
(the unit ran, the private address refused; a restarted node-engine's
undecided statement cleared the network condition and its reopening
dated the fault after the send), what the reproduction showed of
bind-dynamic, what is still guessed, and the fixes in review.
Plans of a branch superseded each other by when they were made; the
catch-up's late plan of an older merge took over a newer one, once a
security fix to the forge's module. Recorded with the fix in review.
jschoubben
force-pushed issues/348-the-resolver-stopped-answering-and-nothing-restarted-it from 381d3fe477 to 3acc1ec2192026-10-09 12:12:44 +00:00Compare
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The 2026-10-09 outage on the control node (10:57:57-11:18:12 UTC): symptom, timeline, what is measured and what is guessed, the reproduction of dnsmasq's bind-dynamic closing its listeners on a bridge teardown, and the fixes in review (mesh-controller #179, mesh-catalog #161).
Open for the operator: the dnsmasq watch restarts on health, which departs from ADR 0240 rule 6; why the second resolver did not serve the route proxy is still a guess (its container's resolver file, readable once docker_resolv_conf is delivered); a mesh-lab replay is owed before the issue resolves.
records, index, words and cycle pass locally. Not merged.
8d75a37de5tod6f889d054Delivery
novox/hq@fbd00a16ca40— delivered since 2026-10-09T13:25:45ZDelivery plan — builds nothing: the change touches no module of the mesh's graph
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.381d3fe477to3acc1ec219