Hi Willy
Yes, this patch works, no more segfaults.
However, unrelated to this issue, while testing I noticed that the address
from the state file is not applied if the configuration does not use a
hostname.
In the example I provided, the configuration originally has the IP address
set to 169.254.0.9, which is then updated through the socket to say 10.0.19.17.
Expectation was that upon haproxy restart the address in the state fill
will override the address in the configuration, but this does not happen.
I see the relevant code in srv_init_addr :
if (srv->hostname)
return_code |= srv_iterate_initaddr(srv);
As per the server-template example in the dynamic scaling blog post, this
should have been supported. Am I missing some configuration?
Thanks!
-- Raghu
-- Raghu
On Fri, Jan 12, 2018 at 4:14 PM, Willy Tarreau <w...@1wt.eu> wrote:
> Hello Raghu,
>
> On Thu, Jan 11, 2018 at 02:20:34PM +0530, Raghu Udiyar wrote:
> > Hello,
> >
> > Haproxy 1.7.10 segfaults when the srv_admin_state is set to
> > SRV_ADMF_CMAINT (0x04)
> > for a backend server, and that backend has the `slowstart` option set.
> >
> > The following configuration reproduces it :
> (...)
>
> Thanks for all the details, they made it easy to reproduce.
>
> From what I'm seeing, it's a fundamental design issue in the state
> file handling in 1.7. It starts checks before they have been
> initialized, and try to wake up a NULL task. In 1.8 due to the more
> dynamic config, the initialization sequence has changed and checks
> are initialized before parsing the state file, but I don't feel at
> ease with doing in 1.7 since I don't know if some config elements
> may remain non-updated.
>
> So instead I've just protected against using the task wakeups during
> the state file parsing, and they will be initialized later with the
> appropriate parameters.
>
> Could you please check the attached patch on top of 1.7.10 ?
>
> Thanks,
> Willy
>
