HAProxy does not start on 'slave'

[ednt]

Hi,

I'm not sure if it is a 25.1.1 problem, but with 24.7.12 this problem does not occure.

I updated the 'slave' to 25.1.1 and switched over from 'master' (24.7.11, before I syncronised the config)
Then I got infos that an internal web service was not reachable anymore.

HAProxy on 'slave' was not running.
I try to start it via web-gui -> no success
But also no warnings with the current date in the web-gui log.

Strange thing:
If I start HA proxy via CLI:

Code Select Expand

/usr/local/sbin/haproxy -f /usr/local/etc/haproxy.conf -dIt starts without any problems.
Also the state in the gui is green and I can stop it via gui, but I can still not start it again via gui.

The only thing what I can see in the gui log, when I try to start it via gui are the results of the health checks.
So it try to start.
But ... the logs in the gui have the level 'NOTICE' and in the end, the service is not running.

2025-02-19T09:23:01   Notice   haproxy   Health check for backup server isp-web-dmz-1_crm_backend/isp-web-dmz-1m succeeded, reason: Layer7 check passed, code: 200, check duration: 189ms, status: 3/3 UP.   
2025-02-19T09:23:00   Notice   haproxy   Health check for server isp-web-dmz-1_crm_backend/isp-web-dmz-1 succeeded, reason: Layer7 check passed, code: 200, check duration: 98ms, status: 3/3 UP.   
2025-02-19T09:22:59   Notice   haproxy   Health check for backup server isp-web-int-1_backend/isp-web-int-1m succeeded, reason: Layer7 check passed, code: 200, check duration: 89ms, status: 3/3 UP.   
2025-02-19T09:22:59   Notice   haproxy   Health check for server isp-web-int-1_backend/isp-web-int-1 succeeded, reason: Layer7 check passed, code: 200, check duration: 83ms, status: 3/3 UP.   
2025-02-19T09:22:58   Notice   haproxy   Health check for backup server isp-web-dmz-1_backend/isp-web-dmz-1m succeeded, reason: Layer7 check passed, code: 200, check duration: 226ms, status: 3/3 UP.   
2025-02-19T09:22:57   Notice   haproxy   Health check for server isp-web-dmz-1_backend/isp-web-dmz-1 succeeded, reason: Layer7 check passed, code: 200, check duration: 103ms, status: 3/3 UP.

If I start it via CLI I get the health checks with level 'WARNING'.

root@OPNsenseSlave:~ # /usr/local/sbin/haproxy -f /usr/local/etc/haproxy.conf -d
Note: setting global.maxconn to 353117.
Available polling systems :
    kqueue : pref=300,  test result OK
      poll : pref=200,  test result OK
    select : pref=150,  test result FAILED
Total: 3 (2 usable), will use kqueue.

Available filters :
        [BWLIM] bwlim-in
        [BWLIM] bwlim-out
        [CACHE] cache
        [COMP] compression
        [FCGI] fcgi-app
        [SPOE] spoe
        [TRACE] trace
Using kqueue() as the polling mechanism.
[WARNING]  (21747) : Health check for server isp-web-dmz-1_backend/isp-web-dmz-1 succeeded, reason: Layer7 check passed, code: 200, check duration: 103ms, status: 3/3 UP.
[WARNING]  (21747) : Health check for backup server isp-web-dmz-1_backend/isp-web-dmz-1m succeeded, reason: Layer7 check passed, code: 200, check duration: 226ms, status: 3/3 UP.
[WARNING]  (21747) : Health check for server isp-web-int-1_backend/isp-web-int-1 succeeded, reason: Layer7 check passed, code: 200, check duration: 83ms, status: 3/3 UP.
[WARNING]  (21747) : Health check for backup server isp-web-int-1_backend/isp-web-int-1m succeeded, reason: Layer7 check passed, code: 200, check duration: 89ms, status: 3/3 UP.
[WARNING]  (21747) : Health check for server isp-web-dmz-1_crm_backend/isp-web-dmz-1 succeeded, reason: Layer7 check passed, code: 200, check duration: 98ms, status: 3/3 UP.
[WARNING]  (21747) : Health check for backup server isp-web-dmz-1_crm_backend/isp-web-dmz-1m succeeded, reason: Layer7 check passed, code: 200, check duration: 189ms, status: 3/3 UP.
0000000c:GLOBAL.accept(0009)=000e from [unix:1] ALPN=<none>
0000000c:GLOBAL.clicls[000e:ffff]
0000000c:GLOBAL.srvcls[000e:ffff]
0000000c:GLOBAL.closed[000e:ffff]

What happens?

Any ideas?