---
status: open
opened: 2026-09-30
located-in: []
fixed-by:
amended-design:
---

# 158 — The proxy re-reads and re-logs every route it serves, every two seconds

## What was observed

The route proxy on the control node logs the whole of what it serves about every two seconds —
measured 2026-09-30, **31 times in sixty seconds**, each line naming all 52 routes:

```
23:27:19 serving 52 route(s): autoconfig.novox.be, autoconfig.novox.internal, … www.praktijkdespiegel.be
23:27:21 serving 52 route(s): autoconfig.novox.be, autoconfig.novox.internal, … www.praktijkdespiegel.be
23:27:23 serving 52 route(s): autoconfig.novox.be, autoconfig.novox.internal, … www.praktijkdespiegel.be
```

Nothing is changing. The route set is identical every time.

## Why it matters

**It buries the only line that matters.** Between two of those entries sits the one error that explained
a failing name:

```
23:27:23 http: TLS handshake error from 10.10.0.3:33480:
  no public route for "keycloak.novox.be.internal" in this mesh, so no certificate is asked for
```

One line of signal to roughly 5,000 characters of repetition, and the diagnosis it belonged to
([issue 157](../157-a-routed-names-internal-alias-is-served-by-nothing/00-report.md)) was found by
grepping past it. A log that says the same true thing every two seconds is a log nobody reads, which is
the same failure as one that says nothing — and it is the mesh's own accuracy rule pointed the other
way: a report that is loud about the unchanging is not reporting.

Whether the *re-read* is also wasteful is secondary and unmeasured — it may be a cheap file stat. The
logging is not in question.

## Where to look

Not localised. The proxy is `mesh-controller examples/route-proxy`; whether it re-reads on a timer or on
a file watch, and whether it logs unconditionally or only on change, is the first thing to read. Saying
what changed — or saying nothing — is the behaviour wanted, and the mesh already has the rule written
down for its own reports: a log that is quiet on success and loud on failure reads as broken when it is
working, and one that is loud always reads as nothing.