Haproxy peers section not respecting init-addr none

Help!
1

Hello,

it seems like the haproxy peers section is not respecting the option init-addr when starting up. If one of the servers inside the peers section is not reachable / resolvable during startup it just fails with invalid address.

When the server which is not resolvable is commented out it starts working.

Is there any way to overcome this like maybe just using the local peer first if none of the servers is reachable ?

Iam using the followign version haproxy:2.2.2-alpine

Config:

peers proxy_peers
  bind 0.0.0.0:10001
  default-server init-addr none
  server node_1
  server node_2 node_2.haproxy.service.consul:10001 init-addr last,libc,none resolvers mydns
  server node_3 node_3.haproxy.service.consul:10001 init-addr last,libc,none resolvers mydns

Error:

[ALERT] 295/091651 (1) : parsing [/usr/local/etc/haproxy/haproxy.cfg:207] : 'server node_2' : invalid address: 'node_2.haproxy.service.consul' in 'node_2.haproxy.service.consul:10001'"
1 Like
2

I’m facing the same issue with 2.2.4

3

I’m not sure whether this is supposed to work or not.

Could you file a bug please?

4

Bug report: https://github.com/haproxy/haproxy/issues/919