Hi Willy,
On Thursday, December 4th, 2025 at 9:19 AM, Willy Tarreau <[email protected]> wrote:
> Please continue to watch in case the problem happens again. And next time do
> not hesitate to ping again if you don't get any response after a few days; it
> just means everyone's busy and your message wasn't noticed.
Will do. It wasn't that big of a deal and I got on to other things. Just
happened to notice that the tables appeared to be syncing the other day after I
upgraded haproxy.
Not sure if this could be considered an ongoing bug, but if there are multiple
peers, they will sync between each other on reload, but if it's just one
instance it looks like it won't sync to itself like it used to, at least not
with this config:
peers synced
bind server:83 ssl crt cert.pem
default-server ssl ca-file /etc/ssl/certs/ca-certificates.crt
server server1 sni str(server1.domain.net)
table daily-request-tracking-dynamic type ipv6 size 10m expire 24h store
http_req_rate(24h),http_err_rate(24h)
A reload flushes this table out. Now that I'm looking at this again, it looks
like this no longer works either:
peers synced
peer dev-proxy01 127.0.0.1:83
table daily-request-tracking-dynamic type ipv6 size 10m expire 24h store
http_req_rate(24h),http_err_rate(24h)
Nor does:
peers local
peer dev-proxy01 127.0.0.1:10000
backend foo
stick-table type ipv6 size 1k expire 1m store
conn_cur,http_req_rate(1m),http_err_rate(1m) peers local
This table gets totally flushed on reload.
This is how I'm reloading haproxy:
ExecReload=/usr/local/sbin/haproxy -Ws -f ${CONFIG_DIR} -c
ExecReload=/bin/kill -USR2 ${MAINPID}
Let me know if you want me to do anything more with this.
Bren
