On Tue, Feb 9, 2010 at 9:48 AM, Willy Tarreau w...@1wt.eu wrote:
On Mon, Feb 08, 2010 at 12:35:32PM -0800, Paul Hirose wrote:
The error earlier reported during -dev7 about not compiling with
DEBUG_FULL is still present in rc1 and ss-20100208. As that msg
indicated, changing it f rom req
We use the VRRP part of the Keepalived system. I'm sure heartbeat (or
its sucessor pacemaker) would also work. I just found Keepalived
easier to implement. Whether it works across two separate datacenters
would depend on the network between them (my two HA haproxy systems
are in the same
I have the log entry
Jan 25 04:02:33 lbtest1 haproxy[24428]: Server LDAPFarm/dp1 is DOWN,
reason: Layer7 timeout, check duration: 5001ms. 2 active and 0 backup
servers online. 0 sessions requeued, 0 total in queue.
In my /var/logs/messages. I run a healthcheck (mode httpchk) via
xinetd on the
I have the following in my stats, and the below as my conf (running
1.4dev6, haven't gone to dev7 yet.)
==
pid = 14860 (process #1, nbproc = 1)
uptime = 0d 0h00m29s
system limits: memmax = unlimited; ulimit-n = 4023
maxsock = 4023; maxconn = 2000; maxpipes = 0
current conns = 164; current pipes =
I'm sending this again. I never saw it come back to me from the list
and the archive at
http://www.formilux.org/archives/haproxy/1001/date.html doesn't have
this copy either.
PH
-- Forwarded message --
From: Paul Hirose paulhir...@gmail.com
Date: Wed, Jan 20, 2010 at 2:51 PM
I'm having a bit of difficulty interperting the act/fe/be/srv
connection numbers in my option tcplog (definitions from manual
appended below.)
Sample entry from my logs:
Jan 20 14:33:49 lbtest1 haproxy[25582]: :34456
[20/Jan/2010:14:33:47.826] LDAPFarm LDAPFarm/dp2 0/0/1227 202 --
A simple question - is the data received from the back-end server
stored on haproxy until all the data is received, before that date
is then sent on to the client? I didn't think so, but I wasn't sure
now.
I'm now seeing a few cD connection status:
Jan 14 14:51:15 lbtest1 haproxy[18994]:
2010/1/13 Cyril Bonté cyril.bo...@free.fr:
Le Mercredi 13 Janvier 2010 12:56:30, Hervé COMMOWICK a écrit :
I know the check is not perfect, because it doesn't handle a correct
disconnection.
Mysql expect the client to talk, and i think it's weird... in the
future, i think it will be better to
I stumbled across a few SC results in my logs, which the docs say is:
SC The server or an equipement between it and haproxy explicitly refused
the TCP connection (the proxy received a TCP RST or an ICMP message
in return). Under some circumstances, it can also be the network
On Wed, Jan 13, 2010 at 1:15 PM, Willy Tarreau w...@1wt.eu wrote:
One thing I've had trouble with when doing mysql though was the
connection timeouts. I tried using tcpka but that didn't do it.
it would not change because tcpka enables tcp keepalives which just
the system is aware of. It is not
-- Forwarded message --
From: Paul Hirose paulhir...@gmail.com
Date: Tue, Jan 5, 2010 at 10:42 AM
Subject: Per-Server arguments for httpchk health-checking
To: haproxy@formilux.org
Is there a way to have haproxy send a per-server argument during a
health-check? Right now, I do server
Busy little haproxy beaver today :)
The docs under retries says if a connection attempt fails, it waits
one second, and then tries again. I was wondering how (if at all)
that works in conjunction with timeout connect, which is how long
haproxy waits to try to connect to a backend server. Is the
Thank you for your help.:)
2010/1/6 Krzysztof Olędzki o...@ans.pl:
On 2010-01-06 18:45, Paul Hirose wrote:
The docs under retries says if a connection attempt fails, it waits
one second, and then tries again.
This 1s timeout is only used in case of immediately error (like TCP RST
haproxy process running, processing one very long request. I run
another haproxy -sf, which does the whole reload, etc stuff. The long
request (ldap database query) continues on its way. :) So that's good
:)
But I thought the old process would stick around until that entire
request was done,
Is there a way to have haproxy send a per-server argument during a
health-check? Right now, I do server A check addr localhost 9000
and server B check addr localhost 9001 and so on, and have xinetd
monitor 9000/TCP and 9001/TCP. When haproxy connects to those, xinetd
in turn runs a health-check
Previously mentioned retries and option redispatch, with regard to
connecting to failed servers.
So retries 3 and option redispatch have nothing to do with the
inter, downinter, etc, right? A client connects to haproxy, which
in turn tries to send that request on to a back-end server. If the
) and my clients go merrily
on their way. But anything to smooth that out, or any gotchas I should watch
out for.
Thanks all,
PH
--
Paul Hirose : pthir...@ucdavis.edu : Sysadm Motto: rm -fr /MyLife
Is there a way to specify a program to run to do health checks with
HAProxy? Right now, I do custom health checking by running a checking
daemon started by x/inetd. So I set haproxy to do check against a
different port (server ... check address localhost port somethingelse
inter ). Then
I've stumbled into similar-ish problems, essentially the
haproxy-server connection timing out and closing. In my particular
case, the backend is a MySQL server, but I figure the issue is
essentially the same. I've not yet put my system into full
production, so I don't know if the MySQL servers
Not quite what you're looking for, but could you use weights on the
backend systems? It would work, while all three servers are up and
running. Say give the 3rd server that has other services on it a
weight of 1 and the other two a weight of 50. If I understand
weights, then the two servers
20 matches
Mail list logo
