feat: HAProxy 3.2 LTS (haproxy.debian.net) + capture HAProxy stderr + 2 s supervisor
DRAFT for review, not merged. Context: HAProxy 3.0.11 (Debian trixie) aborts via its own watchdog in the DNS resolver (haproxy #3101, fixed in 3.0.13/3.1.11/3.2.6). * Dockerfile: haproxy from https://haproxy.debian.net trixie-backports-3.2 (committed signing key, fingerprint asserted, series pin 3.2.*, optional HAPROXY_EXACT), native OpenSSL QUIC asserted (no compat layer), /haproxy/HAPROXY_VERSION. * start HAProxy as `haproxy -W -db` (spawn_haproxy_master): `daemon` sent the master's stderr to /dev/null, losing ALERTs and the ha_panic thread dump. stderr -> /var/log/haproxy/haproxy-stderr.log, forwarded to container stderr by scripts/haproxy-stderr-relay.py (rate limited, rotated). * supervisor: pidof probe every 2 s (was python every 15 s), exponential backoff on failed restarts. * tests: relay unit tests; rollback/cert stubs print "Loading success.". Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0185ukXi4YX5FxJGqhi6qab6
This commit is contained in:
1 parent
46ea498db3
commit
a753d300db
12 files changed
+470
-51
No files matched your search
@@ -492,6 +492,22 @@ Rollout: image bump + recreate with the volume and sysctl (WHP's
|
||||
are in the image, outside the `/etc/haproxy` named volume, so nothing can be
|
||||
shadowed; `haproxy.cfg` is regenerated on start with the new `log` line.
|
||||
|
||||
## HAProxy stderr (panic dumps, [ALERT]s) - since 2026.11.4
|
||||
|
||||
HAProxy is started as `haproxy -W -db` so the master keeps a real stderr (with
|
||||
the `daemon` keyword HAProxy points it at /dev/null, which discarded the
|
||||
`[ALERT]` lines, `Current worker (N) exited with code 134` and the whole
|
||||
watchdog/`ha_panic` thread dump). It is appended to
|
||||
`/var/log/haproxy/haproxy-stderr.log` (the `haproxy-logs` volume, so it
|
||||
survives a recreate) and `scripts/haproxy-stderr-relay.py` re-emits every line
|
||||
on the container's stderr prefixed `haproxy-stderr: ` (rate-limited, file
|
||||
rotated at 20 MiB x 3). `docker logs haproxy-manager` and whatever docker
|
||||
logging driver the host configured therefore carry the crash text; the
|
||||
per-request access log stays out of it. The in-container supervisor probes
|
||||
with `pidof` every `HAPROXY_SUPERVISOR_INTERVAL` seconds (default 2, was 15) and
|
||||
backs off to `HAPROXY_SUPERVISOR_MAX_BACKOFF` (30) only when a restart attempt
|
||||
fails. Measured (3.2.26, empty config): crash to listeners back = 1.2-2.0 s.
|
||||
|
||||
## Default Backend Configuration
|
||||
|
||||
With the default splash on (above), unrouted hosts no longer reach this page; it still serves the blocked-IP and suspended pages, and serves unrouted hosts again when `HAPROXY_DEFAULT_SPLASH=off`.
|
||||
|
||||
Reference in new issue
Block a user