Re: Lots of mail from email alert on 1.9.x

Op 13-01-19 om 18:47 schreef Willy Tarreau: > Hi Olivier, > > On Sun, Jan 13, 2019 at 06:40:56PM +0100, Olivier Houchard wrote: >>> Indeed, this function should not have any special effect in this case, >>> it is needed to prepend this at the beginning of chk_report_conn_err() : >>> >>> if

Re: Lots of mail from email alert on 1.9.x

: > Hi Johan, Olivier, Willy, > > Op 10-1-2019 om 17:00 schreef Johan Hendriks: >> I just updated to 1.9.1 on my test system. >> >> We noticed that when a server fails we now get tons of mail, and with >> tons we mean a lot. >> >> After a client backen

Lots of mail from email alert on 1.9.x

11.22.33.44:80 check Has something changed in 1.9.x (it was on 1.9.0 also) regards Johan Hendriks

Re: SSL certs

Op 27-11-18 om 02:53 schreef Azim Siddiqui: > Hello, > > Hope you are doing good. We are using HAproxy in our company. But the ssl > certs has been expired. I want to renew it. As i can see HAproxy only takes > .pem format for certs. So what files should be included in that .pem file ? > And

Re: email alert not working with 1.8.5

Op 27/03/2018 om 16:01 schreef Christopher Faulet: > Le 26/03/2018 à 16:58, Johan Hendriks a écrit : >> I just updated haproxy to 1.8.5 on my FreeBSD 11-Stable server. >> >> I just noticed we do not receive any email notifications anymore when a >> server goes down. >

email alert not working with 1.8.5

-alert to p...@haproxy.mydomain.nl In the maillog nothing comes in. I can send mail normally from the system. Also can connect and send with telnet from localhost on port 25. regards Johan Hendriks

Re: nss_getpwnam: name 't...@my.dom@localdomain' does not map into domain 'nix.my.dom'

Tom, this list is for the loadbalancer software haproxy, so i think you mailed the wrong list. Regards Johan Hendriks Op 6 mrt. 2018 06:41 schreef "TomK" <tomk...@mdevsys.com>: > Hey Guy's, > > Getting below message which in turn fails to list proper UID / GID on &

Re: Is the data on stats page global across all processes?

at way you can use a single stats page. mind that this is marked as experimental! You need to change nbproc to nbthread. Then a single stat page is available. The bind-process line is not needed anymore. regards, Johan Hendriks

Re: Haproxy 1.8.4 crashing workers and increased memory usage

ose >>> option http-pretend-keepalive >> Same comment here as above regarding close vs keep-alive. > Yes I will take a look at this as well. > >> Aside this I really see nothing suspicious in your configuration that could >> justify a problem. Let's hope you can at least either catch a core or attach >> a gdb to one of these processes. > I will let you know as soon as I'm able to get a backtrace. In the meanwhile > I will improve and test my new configuration changes. > > Thanks, > Frank Frank, >From your config it looks like you are using letsencrypt for the certificates. Maybe you can concatenate multiple domains in one certificate. For most domains you probably only use the www and non www domain names and I believe you can put 100 domain names in one certificate. This way you can store 50 domains in one certificate reducing the number of loaded domains significantly. Just a thought as I do not know if it is doable for your organization. Regards Johan Hendriks

Re: haproxy without balancing

Op 05/01/2018 om 11:46 schreef Jonathan Matthews: > On 5 January 2018 at 10:28, Johan Hendriks <joh.hendr...@gmail.com> wrote: >> BTW if this is the wrong list please excuse me. > This looks to me like it might be the right list :-) > >> We have an application running

haproxy without balancing

Hello. First off all I wish everyone a really good 2018. And hopefully 2018 will serve a lot of good memory's. BTW if this is the wrong list please excuse me. We have an application running over multiple servers which all have there own subdomain, there are about 12 of them. We can live without

Re: Status change from MAINT to UP

Op 16/12/2017 om 10:31 schreef Johan Hendriks: > > Op do 14 dec. 2017 om 22:12 schreef PiBa-NL <piba.nl@gmail.com > <mailto:piba.nl@gmail.com>> > > Hi Johan, > > Op 14-12-2017 om 9:35 schreef Johan Hendriks: > > Op 13/12/2017 om 2

Re: Haproxy SSl Termination performance issue

Op di 19 dec. 2017 om 16:16 schreef hongw...@163.com > Hi, Thierry. > > Thanks again. > > One more question about you talking about, can i just think like this way: > assume we got a 8core cpu, we use 7 of them for ssl termination and one is > for http forward? If it is, is

Re: Status change from MAINT to UP

Op do 14 dec. 2017 om 22:12 schreef PiBa-NL <piba.nl@gmail.com> > Hi Johan, > > Op 14-12-2017 om 9:35 schreef Johan Hendriks: > > Op 13/12/2017 om 20:48 schreef PiBa-NL: > >> Hi Johan, > >> > >> Op 13-12-2017 om 17:31 schreef Johan Hendri