Issue 118 is resolved: it was issue 135, and umami is healthy #199

2026-09-29T23:54:33Z

jschoubben commented

2026-09-29 23:54:33 +00:00

Verified on the machine: umami has zero restarts, applies all 26 migrations, reports the store up to date, and umami.novox.be answers 200 where it had answered 502 since 2026-09-25.

It was the same fault as 135, filed three days earlier and diagnosed without either record noticing the other. 135's container is umami — named in 135's own evidence table, holding novox.internal:10.42.0.1 after the overlay range moved. The dial appeared to succeed and the first real query timed out because the name pointed at an address that no longer existed; the store, the path and the credential were all fine.

118's own reasoning is kept as a warning because it is careful and wrong: it argued path-MTU and conntrack, and it named the move that would have found it — compare umami against a container created that week — and did not make it. A stale name presents as a network fault, which is why ADR 0148 stops copying names into containers rather than detecting when the copies go bad.

Two corrections: 118's located-in named mesh-catalog modules/umami, which was never at fault, and now names mesh-host's comparison; and 135 gains the pointer to 118.

Checks: records, index, cycle all pass.

Verified on the machine: umami has zero restarts, applies all 26 migrations, reports the store up to date, and `umami.novox.be` answers **200** where it had answered `502` since 2026-09-25. It was the same fault as **135**, filed three days earlier and diagnosed without either record noticing the other. 135's container *is* umami — named in 135's own evidence table, holding `novox.internal:10.42.0.1` after the overlay range moved. The dial appeared to succeed and the first real query timed out because the name pointed at an address that no longer existed; the store, the path and the credential were all fine. 118's own reasoning is kept as a warning because it is careful and wrong: it argued path-MTU and conntrack, and it named the move that would have found it — compare umami against a container created that week — and did not make it. **A stale name presents as a network fault**, which is why ADR 0148 stops copying names into containers rather than detecting when the copies go bad. Two corrections: 118's `located-in` named `mesh-catalog modules/umami`, which was never at fault, and now names mesh-host's comparison; and 135 gains the pointer to 118. Checks: records, index, cycle all pass.

jschoubben added 1 commit 2026-09-29 23:54:33 +00:00

Issue 118 is resolved: it was issue 135, and umami is healthy 295bf2f3ab

Verified on the machine: umami has zero restarts, applies all 26
migrations, reports the store up to date, and umami.novox.be answers 200
where it had answered 502 since 2026-09-25.

It was the same fault as 135, filed three days earlier and diagnosed
without either record noticing the other. 135's container IS umami — it
is named in 135's own evidence table, holding novox.internal:10.42.0.1
after the overlay range moved. The dial appeared to succeed and the first
real query timed out because the name pointed at an address that no
longer existed; the store, the path and the credential were all fine.

118's own reasoning is kept as a warning, because it is careful and
wrong: it argued path-MTU and conntrack, and it named the move that would
have found it — compare umami against a container created that week —
and did not make it. A stale name presents as a network fault, which is
why ADR 0148 stops copying names into containers rather than detecting
when the copies go bad.

Also: 118's located-in named mesh-catalog modules/umami, which was never
at fault; it names mesh-host's comparison now. And 135 gains the pointer
to 118, which is the back-reference I have now missed three times.

jschoubben merged commit 76fbe323ea into main

2026-09-29 23:54:39 +00:00

jschoubben deleted branch issue/118-is-135-and-is-resolved

2026-09-29 23:54:39 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#199