Hi Baptiste,
could you please have a look at this one, I suspect Raghu's proposal
is reasonable, I just want to be sure we don't break DNS and friends.
Thanks,
Willy
On Mon, Aug 13, 2018 at 08:16:31PM +0530, Raghu Udiyar wrote:
> Hi Willy, Baptiste
>
> On Fri, 29 Jun 2018 at 08:12 Willy
Hi Willy, Baptiste
On Fri, 29 Jun 2018 at 08:12 Willy Tarreau wrote:
> Hi Raghu,
> [...]
>
>[ALERT] 248/130258 (21960) : parsing [/etc/haproxy/test.cfg:53] :
> 'server bla' : no method found to resolve address '(null)'
>[ALERT] 248/130258 (21960) : Failed to initialize server(s)
Hi Raghu,
On Thu, Jun 28, 2018 at 02:46:36PM +0530, Raghu Udiyar wrote:
> Hi Willy, Baptiste
>
> I have been running this in production without any issues. Can you please
> review, verified that this will apply on current devel as well.
Thanks, however while looking if we had already merged it
Hi Willy, Baptiste
I have been running this in production without any issues. Can you please
review, verified that this will apply on current devel as well.
On Fri, 6 Apr 2018 at 22:36 Willy Tarreau wrote:
> Hi Raghu,
>
> On Wed, Mar 28, 2018 at 08:30:39PM +, Raghu Udiyar wrote:
> > Hi
Hi Raghu,
On Wed, Mar 28, 2018 at 08:30:39PM +, Raghu Udiyar wrote:
> Hi Willy, Baptiste
>
> It looks like this was the intended behaviour as per the documentation. But
> it looks to be simple to enable the init-addr behaviour for IP addresses as
> well. Can you please review the attached
Hi Willy, Baptiste
It looks like this was the intended behaviour as per the documentation. But
it looks to be simple to enable the init-addr behaviour for IP addresses as
well. Can you please review the attached patch, this is against devel.
Hi Baptiste
Were you able to look into this? A workaround is to use a dummy hostname,
and init-addr like so :
server testserver13 dummyhost:9003 check init-addr last,10.0.19.10
server testserver14 dummyhost:9003 check init-addr last,10.0.19.12
# disabled placeholder
server
Hi Raghu,
On Sun, Jan 14, 2018 at 05:59:16PM +0530, Raghu Udiyar wrote:
> 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.
>
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
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 :
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 :
-
# haproxy.cfg (replace below)
global
maxconn 3
11 matches
Mail list logo
