Hi,
On Fri, Apr 25, 2014 at 02:51:36AM +, Stefan wrote:
Hello,
I'm stuck with one issue. Can you help me, please.
I have a service that gets about 1K connections/second
and 15K requests/sec in top.
And my service should response maximum in 120 ms.
The client, that sends me these
Thank you very much, Willy.
timeout http-request and dontlognull hellped.
But as i understand, i won't see 4xx errors in log,
but they are still in statistics: Frontend requests errors?
I have Munin plugin for HAProxy and the diagram shows
me Frontend errors: from 20 to 150 (in high
load)
On Fri, Apr 25, 2014 at 07:23:31AM +, Stefan wrote:
Thank you very much, Willy.
timeout http-request and dontlognull hellped.
But as i understand, i won't see 4xx errors in log,
but they are still in statistics: Frontend requests errors?
I have Munin plugin for HAProxy and the diagram
Ok.
And the last question about 4xx errors;
At this moment i also have a lot of errors:
0/0/0/-1/317 400 187 - - CH-- 30142/19850/93/4/0 0/0 POST
In docs it describes as:
The client aborted while waiting for the server to start responding.
It might be the server taking too long to
Hi,
At this moment i also have a lot of errors:
0/0/0/-1/317 400 187 - - CH-- 30142/19850/93/4/0 0/0 POST
In docs it describes as:
The client aborted while waiting for the server to start responding.
It might be the server taking too long to respond or the client
clicking the 'Stop'
Hi,
I noticed a dramatic increase in CPU usage between HAProxy ss-20140329
and ss-20140425. With the first haproxy uses around 20% of CPU and with
the latter it eats up 80-90% of cpu and sites start to become sluggish.
Health checks take much more time to complete 1100ms vs 2ms normal
Am 25.04.14 04:25, schrieb Ben Timby:
My only feedback is that haproxy has a lot of features that make it useful as
a MySQL frontend. The stats are great for
sizing and monitoring purposes. Timeouts and queuing are also great for
managing load etc. I used to run haproxy in
front of a single
Hey Willy,
On 25.04.2014 14:39, Willy Tarreau wrote:
On Fri, Apr 25, 2014 at 02:12:23PM +0200, Sander Klein wrote:
Hi,
I noticed a dramatic increase in CPU usage between HAProxy ss-20140329
and ss-20140425. With the first haproxy uses around 20% of CPU and
with
the latter it eats up 80-90
, then move the
block rules before http-request and the warning will go away).
Just to make sure I didn't give you a bogus report is
upgraded/downgraded a couple of times, but every time I install 20140425
the CPU spikes and sites become sluggish.
OK. Does it happen immediately or does it take some
On 25.04.2014 15:46, Willy Tarreau wrote:
Just to make sure I didn't give you a bogus report is
upgraded/downgraded a couple of times, but every time I install
20140425
the CPU spikes and sites become sluggish.
OK. Does it happen immediately or does it take some time ?
It happens
rules *after* http-request rules, then move the
block rules before http-request and the warning will go away).
Just to make sure I didn't give you a bogus report is
upgraded/downgraded a couple of times, but every time I install
20140425
the CPU spikes and sites become sluggish.
OK. Does it happen
Hi,
I've done a search and it breaks between 20140413 and 20140415.
Are you using static DH parameters? If not, could you try using some?
Until 20140415 the default was (1024 bits DH parameters):
-BEGIN DH PARAMETERS-
On Fri, Apr 25, 2014 at 04:56:06PM +0200, Sander Klein wrote:
I've done a search and it breaks between 20140413 and 20140415.
OK, that's already very useful. I'm assuming this covers the period
between commits 01193d6ef and d988f2158. During this period, here's
what changed that could possibly
Hi Paul
We use haproxy to multiple https servers. After this we have a separate tomcat
server for each http server. So a one to one relationship between Apache and
tomcat. We then use apache to shop to the tomcat servers.
--
| haproxy1 HA haproxy2 | using
Just a quick note to let you know that Emeric and I have found how
to detect heartbeats and the heartbleed attack at the application
layer and how to block it regardless of the OpenSSL version. So we
have added two new error messages for the logs depending on what
type of handshake failure happens
On 25.04.2014 17:22, Willy Tarreau wrote:
On Fri, Apr 25, 2014 at 04:56:06PM +0200, Sander Klein wrote:
I've done a search and it breaks between 20140413 and 20140415.
OK, that's already very useful. I'm assuming this covers the period
between commits 01193d6ef and d988f2158. During this
On Fri, Apr 25, 2014 at 08:37:39PM +0200, Sander Klein wrote:
Thus given your setup, I'd start with the think I understand the least
which is the SSL change. Could you please revert the attached patch
by applying it with patch -Rp1 ?
Well, I can confirm that reverting that patch fixes my
HAProxy, what else
Baptiste
On Fri, Apr 25, 2014 at 8:15 PM, Willy Tarreau w...@1wt.eu wrote:
Just a quick note to let you know that Emeric and I have found how
to detect heartbeats and the heartbleed attack at the application
layer and how to block it regardless of the OpenSSL version.
Hi Pradeep,
On Sat, Apr 26, 2014 at 12:26:17AM +0200, Pradeep Kiruvale wrote:
Hi All,
I am new to HAProxy. For one of my project I am planning to
add some functionality to HAProxy.
I dont know where to start.
I would like to know where in code base the calls are forwarded to
backed
19 matches
Mail list logo
