Re: Re: CPU 100% when waiting for the client timeout

Hi Willy, I prefer to choose the simple one: 1. re-enable the "option abortonclose" option. 2. disable "timeout client-fin" and "timeout server-fin". That's enough for this test, right? Thanks :-) -- Best Regards BaiYang baiy...@gmail.com http://baiy.cn < END OF EMAIL >

Re: Re: CPU 100% when waiting for the client timeout

Ok, no problem :-) The configuration has been updated to what you want, let's observe what will happen :-D -- Best Regards BaiYang baiy...@gmail.com http://baiy.cn < END OF EMAIL > From: Willy Tarreau Date: 2015-11-25 23:55 To: baiyang CC: CyrilBonté; Lukas Tribus;

RE: Owncloud through Haproxy makes upload not possible

> I'm not sure why, but after doing haproxy -vv I now get kevent() in > truss output. I'm attaching another truss output. Ok, so thats not the problem, good. > While browsing the logs I've notices that besides the usual 200 > output, when uploading was > finished (unsuccessfully) I got the

Re:Tungsten Alloy Swaging Rod for Armor Piercing

Dear Sir/Madam,           Maybe you are not in charge of purchasing.But as you know,the raw material of low price makes your product more competitive in the market.That means it will make your sell much easier.         Please kindly forward this email to the manager of purchase.Or if you would

[PATCH] wrong calloc call

HI all, there is it is a small patch which fix a wrong calloc call, I think. Kind regards. From 9ae38b310a9cb317373ec5748b1c5bd99d7bc986 Mon Sep 17 00:00:00 2001 From: David CARLIER Date: Wed, 25 Nov 2015 15:27:36 + Subject: [PATCH] BUG/MINOR: proxy: calloc call inverted

Re: Re: CPU 100% when waiting for the client timeout

On Wed, Nov 25, 2015 at 11:53:57PM +0800, baiyang wrote: > Hi Willy, > > I prefer to choose the simple one: > 1. re-enable the "option abortonclose" option. > 2. disable "timeout client-fin" and "timeout server-fin". > > That's enough for this test, right? Yup it is, I didn't know if it was

Re: [PATCH] wrong calloc call

Hi David, On Wed, 25 Nov 2015, 16:32:34 +0100, David CARLIER wrote: > HI all, > > there is it is a small patch which fix a wrong calloc call, I think. you are right, of course, but, in the end, 1 * sizeof (struct cap_hdr) == sizeof (struct cap_hdr) * 1, so we have been lucky here ;) > Kind

Re: Re: CPU 100% when waiting for the client timeout

Hi, On Wed, Nov 25, 2015 at 09:31:45PM +0800, baiyang wrote: > Hi > > Ok, I'll try to disable this option anyway to dig up more clues of this > issue. Could you please try the appended patch, or simply disable the client-fin and server-fin timeouts ? What I've seen in the code is stupid and

[PATCH] BUG/MINOR: lua: don't force-sslv3 LUA's SSL socket

Sander Klein reported an error messages about SSLv3 not being supported on Debian 8, although he didn't force-sslv3. Vincent Bernat tracked this down to the LUA initialization, which actually does force-sslv3. This patch removes force-sslv3 from the LUA initialization, so the LUA SSL socket can

RE: ssl parameters ignored

Hi, >> root@debianvm:/home/lukas/haproxy-1.6.2# haproxy -f /home/lukas/ssl.cfg -c >> [ALERT] 328/203304 (9873) : SSLv3 support requested but unavailable. >> Configuration file is valid >> root@debianvm:/home/lukas/haproxy-1.6.2# ./haproxy -f /home/lukas/ssl.cfg -c >> Configuration file is valid

Re: Healthchecks when fronting a proxy to HTTPS endpoints

Hi Tom, Try this: check-ssl ( http://cbonte.github.io/haproxy-dconv/snapshot/configuration-1.6.html#check-ssl ) It will cause healthchecks to use ssl. You will likely also add either a ca-cert or verify none. Regards, PiBa-NL Op 25-11-2015 om 11:34 schreef Tom Duckering: Hi, We’re in a

Retry on HAProxy1 -> HAproxy2 -> 1 backend

In a setup like this where HAProxy1 LBs over N other HAProxies (servers in a backend of HAProxy1): HAProxy1 | --> HAProxy2 -> 1 real backend server | --> HAProxy3 -> 1 real backend server Is there a way to trigger a retry by HAProxy to use HAProxy3 if it tried HAProxy2 and just its real

RE: ssl parameters ignored

Hi, >> I don't know. I got pre made packages from "http://haproxy.debian.net >> jessie-backports-1.6 main" maintained by Vincent Bernat if I'm correct. > > I think there's something wrong with that binary. I will try to reproduce > the problem with it. Confirmed. The 1.6.2 binary (haproxy)

Re: Retry on HAProxy1 -> HAproxy2 -> 1 backend

Mike, Help me understand: if haproxy 1 is just frontending haproxy 2 and 3, which each only have 1 backend.. what is the purpose of haproxy2 and 3, other than to just complicate the architecture? are they serving some other purpose that isn't being communicated? If not, I'd say follow the

Re: ssl parameters ignored

❦ 25 novembre 2015 20:36 +0100, Lukas Tribus  : >>> I don't know. I got pre made packages from "http://haproxy.debian.net >>> jessie-backports-1.6 main" maintained by Vincent Bernat if I'm correct. >> >> I think there's something wrong with that binary. I will try to

Re: Retry on HAProxy1 -> HAproxy2 -> 1 backend

Thanks Jeff, The 'backend' HAProxies do have a purpose - they: * allow stripping global routing information (e.g. from the http path) * allow rate limiting at the worker node (even with many 'client haproxies') * allow for real backends of different types on one node while just having one

Re: [PATCH] BUG/MINOR: lua: don't force-sslv3 LUA's SSL socket

Hi Lukas, On Thu, Nov 26, 2015 at 01:48:08AM +0100, Lukas Tribus wrote: > Sander Klein reported an error messages about SSLv3 not > being supported on Debian 8, although he didn't force-sslv3. > > Vincent Bernat tracked this down to the LUA initialization, which > actually does force-sslv3. > >

Healthchecks when fronting a proxy to HTTPS endpoints

Hi, We’re in a situation where we’d like to use HAProxy to sit in front of a couple of 3rd party HTTP(S) proxies to ensure that we’re resilient in the case that one of them fails. So far we have managed to configure a something basic, but we’re a little unsatisfied with using just a tcp-check

£260 Early Bird Discount Expiring Soon

Publishers Summit 2016 9th -10th Marcg, London, UK -- ACI's Publishers Summit will take place on 9th & 10th March 2016 in London, UK. This two day event will consist of a series of informative presentations followed by interactive Q

[SPAM] ptz cctv camera

DearMr./Mrs., Gladtogetyourcontactinformation!ThisisCarolfromHongm=ei,whichspecializesinR,design,productionandsalesoftheHDI=Pcamera,IPPTZcamera,Spycamera,NVRsystem,HDDVRsystem,DVRsy=stemetc. ThereareourIPSpeeddomecameraBigPromoti=onsnow!Kindlypleasefindthepicturebelow.

haproxy-1.6.2 memory consumption problem with rabbitmq

Hi, Haproxy-1.5.8 has been upgraded to 1.6.2 version and I have a problem with a rabbitmq now. RabbitMQ version 3.5.6 Debian 8 Jessie The working config for 1.5.8 (no timeouts): global chroot /var/lib/haproxy daemon maxconn 4000 pidfile /var/run/haproxy.pid stats socket

Re: Re: CPU 100% when waiting for the client timeout

Hi Baiyang, On Tue, Nov 24, 2015 at 11:09:33PM +0800, baiyang wrote: > Hi Willy > > I've found generally it is very peaceful with the first 24 hours after a > reboot. And usually one reproducing in the next day. And more frequently (2-3 > reproducing) at the third day. > > May be it's a tip?

Re: CPU 100% when waiting for the client timeout

Hi all, - Mail original - > De: "Willy Tarreau" > À: "baiyang" > Cc: "Lukas Tribus" , "haproxy" , > "Cyril Bonté" > Envoyé: Mercredi 25 Novembre 2015 12:52:03 > Objet: Re: Re: CPU 100% when

Re: CPU 100% when waiting for the client timeout

On Wed, Nov 25, 2015 at 01:56:29PM +0100, Cyril Bonté wrote: > Hi all, > > - Mail original - > > De: "Willy Tarreau" > > À: "baiyang" > > Cc: "Lukas Tribus" , "haproxy" , > > "Cyril Bonté"

Re: Re: CPU 100% when waiting for the client timeout

Hi Ok, I'll try to disable this option anyway to dig up more clues of this issue. :-) -- Best Regards BaiYang baiy...@gmail.com http://baiy.cn < END OF EMAIL > From: Willy Tarreau Date: 2015-11-25 21:07 To: CyrilBonté CC: Lukas Tribus; haproxy; baiyang Subject: Re: CPU

RE: ssl parameters ignored

> On 2015-11-23 22:36, Lukas Tribus wrote: >> Are you sure that the executable was cleanly build (first "make clean", >> only then "make ...")? > > I don't know. I got pre made packages from "http://haproxy.debian.net > jessie-backports-1.6 main" maintained by Vincent Bernat if I'm correct. I