Re: Logs full TCP incoming and outgoing packets

2018-04-09 Thread Jonathan Matthews
On 10 April 2018 at 00:04, wrote: > Hello everybody, > > For an application, I use haproxy in TCP mode but I would need to log, from > the main load balancer machine, all the TCP transactions (incoming packets > sent to the node then the answer that is sent back from the

Logs full TCP incoming and outgoing packets

2018-04-09 Thread florent
Hello everybody, For an application, I use haproxy in TCP mode but I would need to log, from the main load balancer machine, all the TCP transactions (incoming packets sent to the node then the answer that is sent back from the node to the client through the haproxy load balancer machine).

Re: Only start on CentOS7 in debug...

2018-04-09 Thread Geert Van Muylem
Hi Aleks, I've recompiled with make TARGET=linux2628 USE_PCRE=1 USE_OPENSSL=1 USE_ZLIB=1 USE_SYSTEMD=1 And used the system file as you proposed... (The -Ws gave a problem when compiling without USE_SYSTEMD) It seems to work! Thanks Only when stopping the service: Should I worry about

Re: Only start on CentOS7 in debug...

2018-04-09 Thread Aleksandar Lazic
Hi Geert. Am 09.04.2018 um 20:54 schrieb Geert Van Muylem: > Hi, > > > I've downloaded and compiled haproxy version 1.8.7 on CentOS7 > > (make TARGET=linux2628 USE_PCRE=1 USE_OPENSSL=1 USE_ZLIB=1) > > > The proxy only starts as it should be if I add the "-d" > > My haproxy.service > > >

Only start on CentOS7 in debug...

2018-04-09 Thread Geert Van Muylem
Hi, I've downloaded and compiled haproxy version 1.8.7 on CentOS7 (make TARGET=linux2628 USE_PCRE=1 USE_OPENSSL=1 USE_ZLIB=1) The proxy only starts as it should be if I add the "-d" My haproxy.service [Unit] Description=HAProxy Load Balancer After=syslog.target network.target

[PATCH] BUG/MEDIUM: threads: Fix the max/min calculation because of name clashes

2018-04-09 Thread Christopher Faulet
Hi, This patch fixes a bug affecting HAProxy compiled with gcc < 4.7 (with threads). It must be merged in 1.8. Thanks, -- Christopher Faulet >From 12456b597dbfe231ba5ea33457676ea59b505ed5 Mon Sep 17 00:00:00 2001 From: Christopher Faulet Date: Fri, 6 Apr 2018 15:33:30

Re: Haproxy 1.8.4 crashing workers and increased memory usage

2018-04-09 Thread Robin Geuze
Hey, Won't that be a bit pointless since we don't use threads? Regards, Robin Geuze On 4/9/2018 10:31, Илья Шипицин wrote: can you try thread sanitizer (in real time)? https://github.com/google/sanitizers/wiki#threadsanitizer I'd like to try myself, however, we do not observe bad things

Re: Haproxy 1.8.4 crashing workers and increased memory usage

2018-04-09 Thread Илья Шипицин
can you try thread sanitizer (in real time)? https://github.com/google/sanitizers/wiki#threadsanitizer I'd like to try myself, however, we do not observe bad things in our environment 2018-04-09 13:24 GMT+05:00 Robin Geuze : > Hey Willy, > > So I made a build this morning

Re: Haproxy 1.8.4 crashing workers and increased memory usage

2018-04-09 Thread Robin Geuze
Hey Willy, So I made a build this morning with libslz and re-enabled compression and within an hour we had the exit code 134 errors, so zlib does not seem to be the problem here. Regards, Robin Geuze On 4/7/2018 00:30, Willy Tarreau wrote: Hi Robin, On Fri, Apr 06, 2018 at 03:52:33PM

Re: DNS resolver and mixed case responses

2018-04-09 Thread Baptiste
So, it seems that responses that does not match the case should be dropped: https://twitter.com/PowerDNS_Bert/status/983254222694240257 Baptiste

Re: DNS resolver and mixed case responses

2018-04-09 Thread Baptiste
On Fri, Apr 6, 2018 at 11:10 AM, Dennis Jacobfeuerborn < denni...@conversis.de> wrote: > On 04.04.2018 16:30, Tim Düsterhus wrote: > > Dale, > > > > Am 03.04.2018 um 16:17 schrieb Dale Smith: > >> I'm trying to understand what system is at fault here; the DNS server > for > >> not responding with

Re: resolvers - resolv.conf fallback

2018-04-09 Thread Baptiste
On Fri, Apr 6, 2018 at 4:54 PM, Willy Tarreau wrote: > On Fri, Apr 06, 2018 at 04:50:54PM +0200, Lukas Tribus wrote: > > > Well, sometimes when you're debugging a configuration, it's nice to be > > > able to disable some elements. Same for those manipulating/building > > > configs