How do I unsubscribe from this mailing list?
I have emailed haproxy+unsubscr...@formilux.org with and without
unsubscribe in the subject but it hasn't worked.
Anyone know how?
All those options are related to the networking performance of the
Kernel, have you also considered memory options for the applications
(such as HAProxy) ?
Does anyone know roughly (I know its hard to be specific with these
things) when 1.5 will become the latest stable version?
Whilst I understand this is a bit how long is a peice of string, I
mean loosely; This year (2013) ? Q3 this year? Before then, Q2?
=300, test result OK
poll : pref=200, test result OK
select : pref=150, test result OK
Total: 4 (4 usable), will use sepoll.
On 2 May 2013 22:39, Bryan Talbot btal...@aeriagames.com wrote:
On Thu, May 2, 2013 at 8:55 AM, James Bensley jwbens...@gmail.com wrote:
Thanks for clearing that up;
On 3 May 2013 12:28, Willy Tarreau w...@1wt.eu wrote:
As explained in the doc, monitor-net unconditionally returns 200 to
all connections coming from the specified network.
If your request comes from another network, then monitor fail will
On 3 May 2013 14:49, Lukas Tribus luky...@hotmail.com wrote:
I am packet capturing on a client (172.22.0.220, not in the monitor
subnet), browsing to the monitor uri (GET /oowahboh6eibooca) you can
see at 14:08:24 I get a response 200 OK. Then I refresh the page 2
seconds later at
When setting TCP keep alive options like tcpka, clitcpka and srvtcpka
Where are these controlled in the host? Are the docs refering to these timers?
On 3 May 2013 17:28, Lukas Tribus luky...@hotmail.com wrote:
Are the docs refering to these timers?
Thanks Lukas, just wanted to check before I start trashing my test servers :)
I have configured haproxy using the below configuration. No matter
what URL I browser to I always receive a HTTP 200 response to my
browser. If I comment out the ACL and three monitor lines from the
frontend configuration, normal behaviour is resumed. I have that gut
feeling that I have
On 18 April 2013 21:13, hapr...@serverphorums.com wrote:
cookie SERVERID insert indirect nocache
server server01 xxx.xxx.xxx.:8081 check cookie s1
server server02 xxx.xxx..xxx:8081 check cookie s2
Presumably you want this to be balance
I have just been through this exact exercise. I have just posted my
results to the Pound Proxy mailing list (so sorry to anyone that is a
subscriber there, here is comes again!). This is the post I just sent,
keepalived is so simple and I have it working with Pound and HAProxy;
I have Pound Proxy and HAProxy on the same box; HTTPS requests come
into Pound, Pound then passes them using plan text HTTP to HAProxy
listening on 127.0.0.1, HAProxy then balances the connections across
the back end servers. Plain text HTTP requests that come into the box
and go strait
Woops! Sorry guys,
log 127.0.0.1 local0
stats socket /var/run/haproxy/haproxy.sock mode 0600 level admin
On 24 January 2013 11:34, Chris Sarginson ch...@sargy.co.uk wrote:
This will allow haproxy to send each new request to a different server, and
then maintain sessions by tracking the appsession cookie you are inserting.
What an absolute
On 18 January 2013 00:03, Unai Rodriguez u...@sysbible.org wrote:
Yes that works in the way I mentioned (cookies then source IP)
Thanks very much for the info Unai!
I wondered if anyone could entertain me with some ideas and thoughts
on being able to load balance all connections that pass through
HAProxy, perhaps by using more that one method, to catch all
connections (I have a single box set up in mind which is troubling
me). I have placed a
On 17 January 2013 12:39, Jonathan Matthews cont...@jpluscplusm.com wrote:
From the fine documentation:
The otherwise caveat sounds like what you're looking for.
Thanks for the info Jonathan.
I am aware of the appsession feature, however when I trialled
You were absolutely right sir,
I was being a fool and overlooking the answer staring me right in the face.
I am having an issue on a load-balancer running Pound and HAProxy. I
believe the error is with HAProxy but it doesn't give an error.
Pound sits in front of HAProxy (on the same box) to perform SSL
off-load. Requests are passed to 127.0.0.1:80 where HAProxy then
balances the requests
Mail list logo