Haproxy config check behaving differently in version 3.2

Toni · August 8, 2025, 10:39am

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

lukastribus · August 8, 2025, 1:49pm

This looks like a bug, make sure you are on latest version 3.2.3 and if so, please file a bug on github:

Toni · August 10, 2025, 7:48pm

Many thanks for your reply. I am in fact using the very latest version 3.2.3.

I have opened this bug report:

github.com/haproxy/haproxy

Haproxy config-check behaving differently in version 3.2

opened 07:46PM - 10 Aug 25 UTC

tferic

type: bug status: needs-triage

### Detailed Description of the Problem I noticed that the haproxy config check… behaves differently in haproxy version 3.2. I am using haproxy 3.2.3 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 an issue with my build? ### Expected Behavior haproxy 3.2: ``` # haproxy -c -f /etc/haproxy/haproxy.cfg Configuration file is valid ``` ### Steps to Reproduce the Behavior `haproxy -c -f /etc/haproxy/haproxy.cfg` ### Do you have any idea what may have caused this? _No response_ ### Do you have an idea how to solve the issue? _No response_ ### What is your configuration? ```haproxy frontend WEB bind *:80 name *:80 mode http timeout client 100s use_backend be_http backend be_http mode http timeout connect 5s timeout server 100s server 10.11.12.13:443 10.11.12.13:443 ``` ### Output of `haproxy -vv` ```plain # haproxy -vv HAProxy version 3.2.3-1844da7 2025/07/09 - https://haproxy.org/ Status: long-term supported branch - will stop receiving fixes around Q2 2030. Known bugs: http://www.haproxy.org/bugs/bugs-3.2.3.html Running on: Linux 5.14.0-570.30.1.el9_6.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Jul 30 15:58:22 UTC 2025 x86_64 Build options : TARGET = linux-glibc CC = cc CFLAGS = -O2 -g -fwrapv OPTIONS = USE_THREAD=1 USE_LINUX_TPROXY=1 USE_OPENSSL=1 USE_LUA=1 USE_ZLIB=1 USE_TFO=1 USE_NS=1 USE_QUIC=1 USE_PROMEX=1 USE_PCRE=1 USE_PCRE_JIT=1 USE_QUIC_OPENSSL_COMPAT=1 DEBUG = Feature list : -51DEGREES +ACCEPT4 +BACKTRACE -CLOSEFROM +CPU_AFFINITY +CRYPT_H -DEVICEATLAS +DL -ENGINE +EPOLL -EVPORTS +GETADDRINFO -KQUEUE -LIBATOMIC +LIBCRYPT +LINUX_CAP +LINUX_SPLICE +LINUX_TPROXY +LUA +MATH -MEMORY_PROFILING +NETFILTER +NS -OBSOLETE_LINKER +OPENSSL -OPENSSL_AWSLC -OPENSSL_WOLFSSL -OT +PCRE -PCRE2 -PCRE2_JIT +PCRE_JIT +POLL +PRCTL -PROCCTL +PROMEX -PTHREAD_EMULATION +QUIC +QUIC_OPENSSL_COMPAT +RT -SLZ +SSL -STATIC_PCRE -STATIC_PCRE2 +TFO +THREAD +THREAD_DUMP +TPROXY -WURFL +ZLIB Default settings : bufsize = 16384, maxrewrite = 1024, maxpollevents = 200 Built with multi-threading support (MAX_TGROUPS=32, MAX_THREADS=1024, default=4). Built with SSL library version : OpenSSL 3.5.1 1 Jul 2025 Running on SSL library version : OpenSSL 3.5.2 5 Aug 2025 SSL library supports TLS extensions : yes SSL library supports SNI : yes SSL library supports : TLSv1.0 TLSv1.1 TLSv1.2 TLSv1.3 OpenSSL providers loaded : default QUIC: connection socket-owner mode support : yes QUIC: GSO emission support : yes Built with Lua version : Lua 5.4.7 Built with the Prometheus exporter as a service Built with network namespace support. Built with zlib version : 1.2.11 Running on zlib version : 1.2.11 Compression algorithms supported : identity("identity"), deflate("deflate"), raw-deflate("deflate"), gzip("gzip") Built with transparent proxy support using: IP_TRANSPARENT IPV6_TRANSPARENT IP_FREEBIND Built with PCRE version : 8.44 2020-02-12 Running on PCRE version : 8.44 2020-02-12 PCRE library supports JIT : yes Encrypted password support via crypt(3): yes Built with gcc compiler version 11.5.0 20240719 (Red Hat 11.5.0-5) Available polling systems : epoll : pref=300, test result OK poll : pref=200, test result OK select : pref=150, test result OK Total: 3 (3 usable), will use epoll. Available multiplexer protocols : (protocols marked as <default> cannot be specified using 'proto' keyword) quic : mode=HTTP side=FE mux=QUIC flags=HTX|NO_UPG|FRAMED h2 : mode=HTTP side=FE|BE mux=H2 flags=HTX|HOL_RISK|NO_UPG h1 : mode=HTTP side=FE|BE mux=H1 flags=HTX|NO_UPG <default> : mode=HTTP side=FE|BE mux=H1 flags=HTX fcgi : mode=HTTP side=BE mux=FCGI flags=HTX|HOL_RISK|NO_UPG spop : mode=SPOP side=BE mux=SPOP flags=HOL_RISK|NO_UPG <default> : mode=SPOP side=BE mux=SPOP flags=HOL_RISK|NO_UPG none : mode=TCP side=FE|BE mux=PASS flags=NO_UPG <default> : mode=TCP side=FE|BE mux=PASS flags= Available services : prometheus-exporter Available filters : [BWLIM] bwlim-in [BWLIM] bwlim-out [CACHE] cache [COMP] compression [FCGI] fcgi-app [SPOE] spoe [TRACE] trace ``` ### Last Outputs and Backtraces ```plain ``` ### Additional Information Dynamically linked to self-compiled version of OpenSSL 3.5.1 Question asked in HAProxy Forum here: https://discourse.haproxy.org/t/haproxy-config-check-behaving-differently-in-version-3-2/11960

Toni · August 11, 2025, 2:42pm

It turns out this change has been made deliberately (not a bug).

Topic		Replies	Views
Segmentation fault when running config check Help!	2	1614	June 12, 2017
Upgrading Haproxy 1.5.18 to 1.7.x or 1.8.x Help!	5	6590	January 29, 2018
About the Configuration Samples category Configuration Samples	1	1814	December 8, 2015
Unable to start HAPROXY 2.2 Help!	5	1066	October 30, 2020
[SOLVED] Migrating Haproxy 1.5.8 to 1.7.5 Help!	10	1262	July 30, 2018

Haproxy config check behaving differently in version 3.2

Related topics