Description of problem: If we use send-proxy and accept-proxy in our HAProxy 1.8 configuration, reloads stop working. The following is enough to trigger the issue: backend app_test_backend server app_test_frontend abns@app_test_frontend send-proxy frontend app_test_frontend bind abns@app_test_frontend accept-proxy During reload we get log messages like these: Nov 01 09:47:38 hap-test02.test.sparebank1.no haproxy[8701]: [WARNING] 304/094738 (8701) : server-state application failed for server 'app_test_backend/app_test_frontend', invalid srv_f_forced_id value '-' Nov 01 09:47:41 hap-test02.test.sparebank1.no haproxy[8701]: [ALERT] 304/094738 (8701) : Starting frontend app_test_frontend: cannot listen to socket [] Nov 01 09:47:41 hap-test02.test.sparebank1.no haproxy[8701]: [WARNING] 304/094738 (8701) : Reexecuting Master process in waitpid mode Nov 01 09:47:41 hap-test02.test.sparebank1.no haproxy[8701]: [WARNING] 304/094738 (8701) : Reexecuting Master process There might be multiple issues here: a problem with values set for non-TCP addresses in server-state, and a problem listening to the sockets after reload (cannot listen to socket []). After the reload command is completed the HAProxy instance no longer accepts any connections. These issues seems to have been fixed in later 1.8 versions. When I tried 1.8.14 compiled from source the problem went away. Version-Release number of selected component (if applicable): RHEL 7.6 rh-haproxy18-runtime-3.1-2.el7.x86_64 rh-haproxy18-3.1-2.el7.x86_64 rh-haproxy18-haproxy-1.8.4-3.el7.x86_64
Moving to RHSCL since this is not RHEL.
Planning to rebase haproxy in RHSCL-3.3, so that should fix this.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1436