Haproxy Mdns, Zeroconf, Avahi, Bounjour does not start if backend is off

Hi! I tried to use avahi zeroconf local addresses in Haproxy backends and had success until I turned off the backend. Now if I try to restart Haproxy with the backend off I got an error stating it can not resolv the address which is certainly true due to it is off.

Here is the Haproxy:

frontend ssh_zeroconf
   bind :87
   mode tcp
   default_backend zeroconfssh

backend zeroconfssh
   mode tcp
   server bicha gise.local:22

Here is an extract of the log when I try to restart it:

Jul 23 23:56:04 ubuntu haproxy[32529]: [ALERT] 204/235554 (32529) : Failed to initialize server(s) addr.
Jul 23 23:56:14 ubuntu haproxy[32530]: [ALERT] 204/235604 (32530) : parsing [/etc/haproxy/haproxy.cfg:375] : 'server bicha' : could not resolve address 'gise.local'.
Jul 23 23:56:14 ubuntu haproxy[32530]: [ALERT] 204/235604 (32530) : Failed to initialize server(s) addr.
Jul 23 23:56:33 ubuntu haproxy[32534]: [ALERT] 204/235623 (32534) : parsing [/etc/haproxy/haproxy.cfg:375] : 'server bicha' : could not resolve address 'gise.local'.
Jul 23 23:56:33 ubuntu haproxy[32534]: [ALERT] 204/235623 (32534) : Failed to initialize server(s) addr.
Jul 23 23:56:43 ubuntu haproxy[32537]: [ALERT] 204/235633 (32537) : parsing [/etc/haproxy/haproxy.cfg:375] : 'server bicha' : could not resolve address 'gise.local'.
Jul 23 23:56:43 ubuntu haproxy[32537]: [ALERT] 204/235633 (32537) : Failed to initialize server(s) addr.

Isn’t there a way I can tell haproxy to start and not complain when it can not resolve a “*.local” zeroconf address?

Thanks in advance!
Hernán

1 post - 1 participant

Read full topic