Re: Stick-table peers expiration time

Hi Igor, On Fri, Feb 19, 2016 at 06:48:13PM +1100, Igor Cicimov wrote: > Hi Willy, > > On 04/02/2016 3:11 PM, "Willy Tarreau" wrote: > > > > On Wed, Feb 03, 2016 at 11:05:03AM +1100, Igor Cicimov wrote: > > > Any comments on this? Shouldn't the expiration time get replicated upon >

Re: Stick-table peers expiration time

Hi Willy, On 04/02/2016 3:11 PM, "Willy Tarreau" wrote: > > On Wed, Feb 03, 2016 at 11:05:03AM +1100, Igor Cicimov wrote: > > Any comments on this? Shouldn't the expiration time get replicated upon > > restart or just the keys? Obviously the entry in the first server stick > > table

Re: Feature Request for log stdout ...

Hi Bryan. Am 18-02-2016 21:18, schrieb Bryan Talbot: Sorry I'm a bit late to this party but when running in a container it's also easy to configure haproxy to log to a unix socket and bind mount that socket to the host. in haproxy.cnf log /dev/log local2 Then when launching the container

[PATCH] CLEANUP: log

HI all, There is a tiny patch proposal for the log component. Cheers. From f1924d813f37cd6444d9251605fdd823efb7fe20 Mon Sep 17 00:00:00 2001 From: David Carlier Date: Thu, 18 Feb 2016 21:46:48 + Subject: [PATCH] CLEANUP: log The string to be escaped is not marked at

Re: Feature Request for log stdout ...

Sorry I'm a bit late to this party but when running in a container it's also easy to configure haproxy to log to a unix socket and bind mount that socket to the host. in haproxy.cnf log /dev/log local2 Then when launching the container an option like "-v /var/log:/var/log" works quite well to

Re: Truncated captured request headers

Hi Adam, Le 18/02/2016 11:54, Adam Renberg a écrit : Hi, Today I updated our HAProxy config to capture more request headers into the logs. I added the following configuration to our frontends: ``` http-request capture hdr(Host) len 40 http-request capture hdr(X-Real-IP) len 15 http-request

Re: config changes on the fly -- dynamically adding/removing backend servers

Alex, I think the following would be a good read: http://dasunhegoda.com/how-to-setup-haproxy-with-keepalived/833/ -- John Skarbek On February 18, 2016 at 12:20:15, alex.be...@yahoo.com (alex.be...@yahoo.com) wrote: Thank you Mehdi and John for replying. It

Re: check ssl

Hi, well, i finally find the problem : I was using bad CAfile (good one is /etc/ssl/certs/GlobalSign_Root_CA.pem) damned openssl that did not tell anything :( Regards, 2016-02-10 17:26 GMT+01:00 Beluc : > It's working, server is UP. > > 2016-02-10 17:21 GMT+01:00 Baptiste

Re: config changes on the fly -- dynamically adding/removing backend servers

Tying into Mehdi, I’ll share with you what we do at our organization which works pretty well. For one, we have two haproxy servers that run keepalived. That way if we need to do something invasive we have a backup to handle the traffic. The process to flip to that server has minimal impact and

Re: Feature Request for log stdout ...

Hi Aleks, On Thu, Feb 18, 2016 at 02:53:29PM +0100, Aleksandar Lazic wrote: > But this moves just the stdout handling to other tools and does not > solve the problem with blocking handling of std*, as far as I have > understood right. Yes it does because if the logging daemon blocks, logs are

Re: config changes on the fly -- dynamically adding/removing backend servers

A `restart` - is naturally an unconditional step thats required - especially in cases of new backends or server additions therein - which are not trivial changes. Network loss / disturbance - if any - is negligible as any existing connections should be migrated between process with a minute window

Re: Feature Request for log stdout ...

On 02/18/2016 07:53 AM, Aleksandar Lazic wrote: Thanks for answers and suggestions. But this moves just the stdout handling to other tools and does not solve the problem with blocking handling of std*, as far as I have understood right. haproxy will not block. If your logging system

Re: Feature Request for log stdout ...

Hi. Am 18-02-2016 11:47, schrieb Conrad Hoffmann: Two more cents from my side: socklog [1] also works pretty well... [1] http://smarden.org/socklog/ Conrad On 02/18/2016 11:28 AM, Baptiste wrote: On Thu, Feb 18, 2016 at 10:57 AM, Willy Tarreau wrote: Hi Aleks, On Wed, Feb

Re: Feature Request for log stdout ...

On Thu, Feb 18, 2016 at 11:47:03AM +0100, Conrad Hoffmann wrote: > Two more cents from my side: > > socklog [1] also works pretty well... > > [1] http://smarden.org/socklog/ Thanks for the links guys. These should probably be added to the management doc so that people find them more easily.

Truncated captured request headers

Hi, Today I updated our HAProxy config to capture more request headers into the logs. I added the following configuration to our frontends: ``` http-request capture hdr(Host) len 40 http-request capture hdr(X-Real-IP) len 15 http-request capture hdr(X-Forwarded-For) len 100 http-request capture

Re: Feature Request for log stdout ...

Two more cents from my side: socklog [1] also works pretty well... [1] http://smarden.org/socklog/ Conrad On 02/18/2016 11:28 AM, Baptiste wrote: > On Thu, Feb 18, 2016 at 10:57 AM, Willy Tarreau wrote: >> Hi Aleks, >> >> On Wed, Feb 17, 2016 at 04:30:06PM +0100, Aleksandar Lazic

Re: Feature Request for log stdout ...

On Thu, Feb 18, 2016 at 10:57 AM, Willy Tarreau wrote: > Hi Aleks, > > On Wed, Feb 17, 2016 at 04:30:06PM +0100, Aleksandar Lazic wrote: >> Hi. >> >> how difficult is it to be able to add "log stdout;" to haproxy? >> >> I ask because in some PaaS environment is it difficult to setup

Re: Feature Request for log stdout ...

Hi Aleks, On Wed, Feb 17, 2016 at 04:30:06PM +0100, Aleksandar Lazic wrote: > Hi. > > how difficult is it to be able to add "log stdout;" to haproxy? > > I ask because in some PaaS environment is it difficult to setup a > dedicated user yust for haproxy. > > It fits also a little bit better