I'm upgrading one of our test clusters from 2.0.13 to 2.0.14 and our
regular graceful-restart process is failing with:
[ALERT] 092/174647 (114374) : [/usr/sbin/haproxy.main()] Some protocols
failed to start their listeners! Exiting.
Looking at strace, it looks like the bind(2) call for the peer socket is
failing. Did something change about the order in which peer sockets are
bound?
Our peers block is pretty straightforward and hasn't changed in several
years.
peers lb
peer devlb1west 10.132.46.130:7778
peer devlb2west 10.132.37.135:7778
Our graceful restart command looks like
/usr/sbin/haproxy -f /path/to/haproxy.config -p
/home/srvelb/run/haproxy.pid -sf 70409 -x /path/to/admin/mode/socket
and also hasn't changed since the addition of domain-socket FD passing in
1.8.
I notice a bunch of peer-related commits got pulled into 2.0.14...
Anyone else seen this?
--
James Brown
Engineer
