On 22 Oct, Willy Tarreau wrote: > Hi Gabriele, > > On Tue, Oct 18, 2016 at 09:40:14PM +0200, Gabriele Cerami wrote: > > Hi, > > > > We're having a problem with version 1.5.14 of haproxy, packaged for > > CentOS 7, but it seems even the code in master is affected. > > > > In situations where bind is not possible (in our case, the address was > > already in use) tcp_connect_server returns with a status of 256 > > (ERR_ALERT). This value is then passed down as exit code for > > haproxy-systemd-wrapper. > > Huh ? First, tcp_connect_server() is not involved here, it's used to > connect to a server, so it never provides an exit code. And even if > instead you meant a bind issue instead, all error codes are limited > to 5 bits so the higher value you can have is 0x1F = 31 if all flags
Yeah, sorry about that hastily made root cause analysis. I'll stick to the facts. This is what we're seeing http://paste.openstack.org/show/586174/ The complete output is somewhat difficult to get, it's available here http://logs.openstack.org/periodic/periodic-tripleo-ci-centos-7-ovb-nonha/9697c38/logs/undercloud/var/log/undercloud_install.txt.gz but you'd have to download it, ungzip it, then open the journal log with journalctl --file var/log/journal/d327fbd51a9f4c4997bdeba685dc22d2/system.journal | less -AXFR As you can see, the thread spawned by the wrapper is returning 256 as status code, and this is interpreded as 0/success by systemd, even if it's actually failing to bind to a port, and thus exiting. thanks for any help

