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
are reported together.

> The problem is that exit value is truncated to the least significant 8
> bits, so even if haproxy fails, systemd gets an exit code of 0 and
> thinks the service start succeded.

I agree this would be a problem but if you really observe an exit code
of 256, I'm interested in knowing how it is produced because I see no
way to produce this!

Thanks,
Willy

Reply via email to