I noticed that the haproxy config check behaves differently in haproxy version 3.2.
Older versions returned “Configuration file is valid“, but version 3.2 does not report anything, when the configuration has no errors and no warnings.
haproxy 3.2:
# haproxy -c -f /etc/haproxy/haproxy.cfg
haproxy 2.8:
# haproxy -c -f /etc/haproxy/haproxy.cfg
Configuration file is valid
Is this issue known? Or is it just my own build?
Thanks
2 posts - 2 participants