Re: [ANNOUNCE] haproxy-1.6-dev6

Hi, 2015-09-29 0:35 GMT+02:00 Willy Tarreau : > Hi everyone, > > this is the end of a harrassing week! I wanted to issue dev6 last monday > to have a calm week dedicated to bug fixes and documentation updates only > and it ended up completely differently with numerous painful bugs

[PATCH]: BUG/MINOR: Wrong setsockopt for TTL fallback, "silent-drop" function

Hi, This little patch avoids a build issue on systems different than Linux. Hope it is useful. Kindest regards. From 24d0feb7981ebabf987ee881768eaf2aea685319 Mon Sep 17 00:00:00 2001 From: David CARLIER Date: Tue, 29 Sep 2015 14:48:28 +0100 Subject: [PATCH] BUG/MINOR:

[PATCH] BUILD: IP_TTL: Fix compilation on almost FreeBSD and OpenBSD.

IP_TTL socket option is defined on some systems that don't have SOL_IP. Use IPPROTO_IP in this case. --- src/proto_tcp.c | 4 1 file changed, 4 insertions(+) diff --git a/src/proto_tcp.c b/src/proto_tcp.c index f698889..3642398 100644 --- a/src/proto_tcp.c +++ b/src/proto_tcp.c @@ -1456,7

Re: segfault writing to log from Lua

Hi, Thank you for reporting this bug. I'll fix it as soon as possible. Best regards, Dragan Dosen On 29.09.2015 14:01, Thierry FOURNIER wrote: > Michael, thank you for the bug repport. I reproduce it. > > It is introduced with the support of the RFC5424 for the logs format > sublitted by

Lua usage question - log format variables

We have "fetches" accessible from Lua, but I have not found a mechanism that allows me to access the value of log format variables. Examples of useful variables: %b | backend_name %f | frontend_name %rt | request_counter Is there a way to access values like these from Lua, since they

Re: [ANNOUNCE] haproxy-1.6-dev6

Hi Willy 2015-09-29 13:59 GMT+02:00 Willy Tarreau : > Hi Joris, > > On Tue, Sep 29, 2015 at 08:56:54AM +0200, joris dedieu wrote: >> > - TCP actions: "silent-drop". Finally it got merged as the actions >> > registration mechanism made it a no-brainer. It works like a deny >> >

Re: segfault writing to log from Lua

ps: a temporary workaround waiting for the fix, is to add the following line at the start of the first loaded lua script. core.Alert = function(msg) print(msg) end Thierry On Tue, 29 Sep 2015 07:37:12 -0400 Michael Ezzell wrote: > Although I am seeing this in Lua, it

Re: segfault writing to log from Lua

This a clean build, on both systems, using a freshly-extracted tarball of 1.6-dev6 downloaded from http://www.haproxy.org/download/1.6/src/devel/haproxy-1.6-dev6.tar.gz. I'll recheck and send files to replicate. On Sep 29, 2015 4:47 AM, "Thierry FOURNIER" wrote: >

Execution order of some directives

hi, After reading the config manual, I have some questions about the directives’ executing order: 1. `reqadd` VS. `http-request add-header`. I can see the warning in the log about the reqadd must be added before http-request, but it’s not documented(or I miss it). 2. `http-request

Re: segfault writing to log from Lua

On Mon, 28 Sep 2015 20:50:44 -0400 Michael Ezzell wrote: > I fired up HA-Proxy version 1.6-dev6-e7ae656 2015/09/28 for testing, and > was greeted with... > > Segmentation fault (core dumped) > > Since I've been primarily testing Lua, I started by commenting out my Lua >

Re: [ANNOUNCE] haproxy-1.6-dev6

Hi Joris, On Tue, Sep 29, 2015 at 08:56:54AM +0200, joris dedieu wrote: > > - TCP actions: "silent-drop". Finally it got merged as the actions > > registration mechanism made it a no-brainer. It works like a deny except > > that it tries to prevent the TCP RST from reaching the client,

Re: segfault writing to log from Lua

Michael, thank you for the bug repport. I reproduce it. It is introduced with the support of the RFC5424 for the logs format sublitted by dragan. Hi Dragan, after your patch about the RFC5424, the funcion __send_log() no longer support NULL for the "*p" param. Can you fix this ? It seems that

Re: segfault writing to log from Lua

Although I am seeing this in Lua, it does not appear (to me) to a the fault in the Lua code... recent changes in __send_log() in log.c appear to assume p is never null (there's a test for this condition earlier, then p is referenced later), and that is not valid behavior in this case, because

Re: [ANNOUNCE] haproxy-1.6-dev6

On Tue, Sep 29, 2015 at 02:58:04PM +0200, joris dedieu wrote: > kevent(3,0x0,0,{},5,{1.0 }) = 0 (0x0) > kevent(3,0x0,0,{0x4,EVFILT_READ,0x0,0,0x1,0x0},5,{1.0 }) = 1 (0x1) > accept(4,{ AF_INET 80.247.233.242:48068 },0x7fffe804) = 5 (0x5) > fcntl(5,F_SETFL,O_NONBLOCK)

Address selection policy in dual-stack environments

Hello, in case when machine has both A and records, there is an address selection policy algorithm which determines which address to use first. https://www.freebsd.org/cgi/man.cgi?query=ip6addrctl=8 I use it in "prefer ipv4" form, to use ipv4 first when available. All programs like ssh

Re: [ANNOUNCE] haproxy-1.6-dev6

On Tue, Sep 29, 2015 at 02:58:04PM +0200, joris dedieu wrote: > kevent(3,0x0,0,{},5,{1.0 }) = 0 (0x0) > kevent(3,0x0,0,{0x4,EVFILT_READ,0x0,0,0x1,0x0},5,{1.0 }) = 1 (0x1) > accept(4,{ AF_INET 80.247.233.242:48068 },0x7fffe804) = 5 (0x5) > fcntl(5,F_SETFL,O_NONBLOCK)

Re: Health check and flapping

Le 2015-08-28 16:40, Baptiste a écrit : Le 28 août 2015 15:45, a écrit : > > Hello, > > We have tcp-check configured on some backends, which works fine, except when service is flapping. > > If the backend server is in transitional state, for example transitionally DOWN

Re: Lua usage question - log format variables

On Tue, 29 Sep 2015 09:57:46 -0400 Michael Ezzell wrote: > We have "fetches" accessible from Lua, but I have not found a mechanism > that allows me to access the value of log format variables. > > Examples of useful variables: > > %b | backend_name > %f | frontend_name

Re: Execution order of some directives

Oops, It’s "`reqadd` must come before the `http-request add-header`". > On Sep 29, 2015, at 5:38 PM, Ruoshan Huang wrote: > > 1. `reqadd` VS. `http-request add-header`. I can see the warning in the log > about the reqadd must be added before http-request, but it’s

Re: segfault writing to log from Lua

On Tue, Sep 29, 2015 at 02:01:59PM +0200, Thierry FOURNIER wrote: > Michael, thank you for the bug repport. I reproduce it. > > It is introduced with the support of the RFC5424 for the logs format > sublitted by dragan. > > Hi Dragan, after your patch about the RFC5424, the funcion __send_log()

Re: Address selection policy in dual-stack environments

Hi Dmitry, On Tue, Sep 29, 2015 at 08:08:51PM +0300, Dmitry Sivachenko wrote: > Hello, > > in case when machine has both A and records, there is an address > selection policy algorithm which determines which address to use first. > https://www.freebsd.org/cgi/man.cgi?query=ip6addrctl=8 >

haproxy 1.5.4 with ssl-bridging

Hello group. I'm new to haproxy. I have read the documentation but still require some assistance. I'm trying to configure haproxy to: 1. accept https connection with client certs required. 2. pass the client cert to a backend https server based on https url path First, can I accomplish this with

Implementing HAProxy First Time: Conditional backend issue

Dear HAProxy Developers, We are implementing HAProxy for reverse proxy load balancing for the first time in our LAN. We are seeking your guidance below to optimize our HAProxy configuration. Currently, we are unable to access our fully working products via HAProxy on two different servers.

Re: Address selection policy in dual-stack environments

> On 29 сент. 2015 г., at 21:26, Willy Tarreau wrote: > > Hi Dmitry, > > On Tue, Sep 29, 2015 at 08:08:51PM +0300, Dmitry Sivachenko wrote: >> Hello, >> >> in case when machine has both A and records, there is an address >> selection policy algorithm which determines which