Transformez votre moue en sourire and changez votre vie pour toujours -
inscrivez-vous maintenant
Http://www.vipplaysbonus.net/fr/
Hi,
On Fri, Mar 19, 2010 at 07:03:47PM +0100, Daniele Genetti wrote:
Hello,
I have one big problem with HAproxy compiled with tproxy support.
This is the situation...
HAPROXY_SERVER
os: ubuntu server
kernel: 2.6.31 (so with tproxy support)
iptables: 1.4.4 (so with tproxy support)
Hello,
first off - thank you very much for such a wonderful piece of software!
I'm using HAProxy on Linux/x86 and it's been a wonderful experience so far.
Things are a bit different on z/Linux, using s390 architecture. HAProxy
was running very nicely for several hours and then suddenly
Also for some reason if you are using the new kernel and the new
iptables (as you seem to be)
you need to specify the firewall mark on EVERY interface:
ip rule add dev eth0 fwmark 111 lookup 100
ip rule add dev eth1 fwmark 111 lookup 100
ip rule add dev eth2 fwmark 111 lookup 100
ip rule add dev
Willy Tarreau wrote:
Hi,
There's something easy you can do to check if it's that : in
src/stream_sock.c, there's only one recv() call. Simply check
that the max value is within bounds :
+ if (max 0 || max b-size)
+ abort();
ret = recv(fd,
I verify default gw and it seems correct.
I also add rules suggested, but nothing change.
The error 503 Service Unavailable persist.
So, now I try to do this test.
1) Without transparent proxy
on HAPROXY_SERVER:
netstat -ctnup | grep 192.168.1.20:80 (ok, connection established showed)
on
hi,
i remember somewhere in the archives mention of a plan to make health
checks get queued like any other request. did that happen in 1.4.x
branch with all the work to health checks. i searched the archives,
but didn't turn up what i remembered. my use case is rails/mongrel
with maxconn = 1 so i
8 matches
Mail list logo