systemctl status haproxy.service, you will see:Failed to start HAproxy Load Balancer
journalctl -u haproxy, you see an error similar to:[ALERT] #### : config : [/etc/haproxy/haproxy.cfg:####] : 'server ####' : unknown keyword ',libc,none'.
[ALERT] #### : config : Fatal errors found in configuration.
Aria Operations 8.18.x
The HAProxy configuration file /etc/haproxy/haproxy.cfg contains a syntax error. The parser does not recognize the keyword string ,libc,none when it is formatted incorrectly (often with a leading comma or incorrect spacing) on the server backend lines. This prevents the load balancer from initializing, which breaks the communication path to the primary cluster
To resolve this issue, you must manually correct the syntax in the HAProxy configuration file:
cp /etc/haproxy/haproxy.cfg /etc/haproxy/haproxy.cfg.bakvi /etc/haproxy/haproxy.cfgNote: Extra space between last and libc needs to be removed
systemctl restart haproxysystemctl status haproxyOnce the service starts successfully, you verify that the Cloud Proxy transitions back to an Online status in the VMware Aria Operations UI.