Inquiry: Information, HAProxy

2017-10-04 Thread Logan Hicks
Aaron West, Thank you! Its great to know I'm not just tossing information into oblivion. Thank you for such a fast reply. All, I am looking for a good tutorial to help me truly understand how and why HAProxy works. My Intent: E.G: server server1 127.0.0.1:80 check ^^^ Understand options

Re: TCP ACL rules based on host name

2017-10-04 Thread Arnall
Le 22/09/2017 à 03:13, rt3p95qs a écrit : Is it possible to assign TCP (no HTTP) connections to a backend based on an alias haproxy has? For example: HAProxy has 3 alias names, server01.example.com , server02.example.com and

Re: Inquiry: Mailing List, HAProxy

2017-10-04 Thread Aaron West
Hey Logan, Sure is! Kind Regards Aaron West Loadbalancer.org Ltd. www.loadbalancer.org +1 888 867 9504 / +44 (0)330 380 1064 aa...@loadbalancer.org LEAVE A REVIEW | DEPLOYMENT GUIDES | BLOG On 5 October 2017 at 00:28, Logan Hicks wrote: > To whom it may concern: > >

Inquiry: Mailing List, HAProxy

2017-10-04 Thread Logan Hicks
To whom it may concern: Is this still the mailing list for the HAProxy project? Respectfully, Logan Hicks a.k.a Fallenour

Re: Haproxy refuses new connections when doing a reload followed by a restart

2017-10-04 Thread Niels Hendriks
Hi all, Thanks for the responses. I agree, in most cases having Ansible trigger a reload instead of a restart is better and it will prevent the situation I described. We have a few environments with very long running sessions where there are situations that we change the configuration and

Re: patch: allow to use any compiler

2017-10-04 Thread Илья Шипицин
2017-10-05 1:01 GMT+05:00 Vincent Bernat : > ❦ 4 octobre 2017 23:49 +0500, Илья Шипицин : > > > while some Makefiles allow to use CC, other just stick to gcc. > > I think we should change to > > > > CC ?= gcc > > This doesn't change much. You can already

Re: patch: allow to use any compiler

2017-10-04 Thread Vincent Bernat
❦ 4 octobre 2017 23:49 +0500, Илья Шипицин  : > while some Makefiles allow to use CC, other just stick to gcc. > I think we should change to > > CC ?= gcc This doesn't change much. You can already override gcc with "make TARGET=... CC=clang". The only thing "?=" is that

Re: Haproxy refuses new connections when doing a reload followed by a restart

2017-10-04 Thread Lukas Tribus
Hello Moemen, Am 04.10.2017 um 19:21 schrieb Moemen MHEDHBI: > > I am wondering if this is actually an expected behaviour and if maybe > that restart/stop should just shutdown the process and its open connections. > I have made the following tests: > 1/ keep an open connection then do a restart

patch: allow to use any compiler

2017-10-04 Thread Илья Шипицин
Hello, while some Makefiles allow to use CC, other just stick to gcc. I think we should change to CC ?= gcc everywhere Cheers, Ilya Shipitsin From 246341f636d085a4e99bdc9f66b5fa3c7bb2b7d3 Mon Sep 17 00:00:00 2001 From: Ilya Shipitsin Date: Wed, 4 Oct 2017 23:43:05 +0500

Re: Haproxy refuses new connections when doing a reload followed by a restart

2017-10-04 Thread Moemen MHEDHBI
Hi Lukas, On 04/10/2017 18:57, Lukas Tribus wrote: > Hello Niels, > > > a restart means stopping haproxy - and after haproxy exited completely, > starting haproxy again. When that happens, haproxy immediately stops > listening to the sockets and then waits for existing connections to be > closed

Re: Haproxy refuses new connections when doing a reload followed by a restart

2017-10-04 Thread Lukas Tribus
Hello Niels, a restart means stopping haproxy - and after haproxy exited completely, starting haproxy again. When that happens, haproxy immediately stops listening to the sockets and then waits for existing connections to be closed (you can accelerate that with hard-stop-after [1], but that's

Haproxy refuses new connections when doing a reload followed by a restart

2017-10-04 Thread Niels Hendriks
Hello, First time mailing here, so hopefully I'm at the right place. I use Ansible to deploy our haproxy configuration, and the following scenario might happen: 1. Haproxy is running on an existing system 2. I execute the Ansible playbook. 3. This playbook changes the haproxy config (which will

Re: another cppcheck finding

2017-10-04 Thread Christopher Faulet
Le 04/10/2017 à 11:54, Илья Шипицин a écrit : Hi, I'm working on the DNS part to make it thread-safe. In my patch set, among other things, I fixed this one. I will send everything to Willy in few days. So don't bother with it. ... using ThreadSanitizer from google ? No. We

Re: another cppcheck finding

2017-10-04 Thread Илья Шипицин
2017-10-04 14:00 GMT+05:00 Christopher Faulet : > Le 04/10/2017 à 07:49, Илья Шипицин a écrit : > >> >> >> 2017-10-04 9:15 GMT+05:00 Willy Tarreau >: >> >> Hi Ilya, >> >> [also CCing Baptiste] >> >> On Tue, Oct 03, 2017 at

Re: Debian upgrade to haproxy 1.7.5: tcp-check fails with Socket error, info: "No port available for the TCP connection"

2017-10-04 Thread kolmann
On 07/13/17 18:26, Lukas Tribus wrote: Hello! Am 29.06.2017 um 16:14 schrieb Philipp Kolmann: Hi Lukas, On 06/19/17 21:23, Lukas Tribus wrote: Am 19.06.2017 um 11:27 schrieb Philipp Kolmann: This config works in 1.5.8 but fails to tcp-check in 1.7.5. The errors in the logfile look like

Re: another cppcheck finding

2017-10-04 Thread Christopher Faulet
Le 04/10/2017 à 07:49, Илья Шипицин a écrit : 2017-10-04 9:15 GMT+05:00 Willy Tarreau >: Hi Ilya, [also CCing Baptiste] On Tue, Oct 03, 2017 at 05:25:17PM +0500, ??? wrote: > [src/dns.c:2502]: (error) Memory leak: buffer > >

Re: TCP ACL rules based on host name

2017-10-04 Thread Igor Cicimov
On 22 Sep 2017 11:15 am, "rt3p95qs" wrote: Is it possible to assign TCP (no HTTP) connections to a backend based on an alias haproxy has? For example: HAProxy has 3 alias names, server01.example.com, server02.example.com and server03.example.com. The haproxy.conf file