It appears the default timeout for SSL handshake is around 2 or 3 seconds,
and timed separately from the "connect" timeout setting for the frontend.
Is there a way to tune this please?
Many thanks.
On Thu, Apr 04, 2019 at 12:48:55PM +, Overbey, Patrick (Sioux Falls) wrote:
> That worked great. Thanks Willy!
Nice, thanks for your feedback!
Willy
I'm very sorry, it is probably "real" traffic that haproxy needs to handle.
Some local DDoS occurred just in time when I upgraded to 1.9 (what terribly
bad luck).
Please ignore previous email! Sorry for wasting your time.
czw., 4 kwi 2019 o 14:36 Maciej Zdeb napisał(a):
> Hi,
>
> After haproxy
That worked great. Thanks Willy!
Patrick Overbey
Fiserv
-Original Message-
From: Willy Tarreau [mailto:w...@1wt.eu]
Sent: Wednesday, April 03, 2019 10:01 PM
To: Overbey, Patrick (Sioux Falls)
Cc: maio...@gmail.com; haproxy@formilux.org
Subject: Re: Upcoming haproxy build fixes for
Hi,
After haproxy starts everything is fine, but after some time one of haproxy
processes uses 100% of CPU. I've managed to dump some "show" commands (I
have also "show fd", "show sess all" and "strace" but if needed I would
prefer to send it privately). If you could give any advice howto debug
Hi, everybody!
Got multiple incidents of failure with 1.9.6:
Core was generated by `/usr/sbin/haproxy -Ws -f /etc/haproxy/haproxy.cfg -p
/var/run/haproxy'.
Program terminated with signal SIGFPE, Arithmetic exception.
#0 0x559afb73c533 in fwrr_update_position (grp=0x559afbd9fb68,
6 matches
Mail list logo