HaProxy does not transfer backend states during reload
When reloading Haproxy (due to config changes for instance) the newly started process does not seem to remember the existing backend status.
The generated haproxy config does contain: server-state-file /tmp/haproxy_server_state
and the haproxy packages writes the server state before reloading: https://github.com/pfsense/FreeBSD-ports/blob/devel/net/pfSense-pkg-haproxy/files/usr/local/pkg/haproxy/haproxy.inc#L2344-L2345
but it seems to miss the configuration to actually load those during start: https://cbonte.github.io/haproxy-dconv/1.8/configuration.html#load-server-state-from-file
Now I wonder if this is on purpose or if this is an oversight. I added "load-server-state-from-file global" to the defaults section and manually reloaded haproxy and all backends kept their previous state.
#2 Updated by Florian Apolloner about 1 month ago
Hi Viktor, I do not think that the ticket you linked is correct. I am specifically talking about the config option "load-server-state-from-file global". I do know that hitless reloads work (even on stable), but it doesn't seem that the backend check status is transferred over to the new instance.
#3 Updated by Viktor Gurov 17 days ago
- Affected Version deleted (