On Wed, Jan 13, 2010 at 01:33:58PM -0800, Paul Hirose wrote:
> 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
>
On Thu, Jan 14, 2010 at 12:28:19AM +0100, Cyril Bonté wrote:
> Hi again Hervé,
>
> Le Mercredi 13 Janvier 2010 12:56:30, Hervé COMMOWICK a écrit :
> > Hi Cyril,
> >
> > I know the check is not perfect, because it doesn't handle a correct
> > disconnection.
> > Mysql expect the client to talk, an
Hello,
On Wed, Jan 13, 2010 at 07:12:45PM -0800, Jose Avila(Tachu) wrote:
> I have a theory on a recent issue i've been experiencing for the last 2 days
> that i would like some clarification on.
> I have a load balancer with 30 backend servers with a roundrobin balance line
> and a maxconn
> p
On Wed, Jan 13, 2010 at 08:47:00PM -0800, Craig Carl wrote:
> That cleared up the error, thanks Ryan.
>
> FYI I took that config straight out of the documentation -
> http://haproxy.1wt.eu/download/1.3/doc/architecture.txt
thanks for pointing it and sorry for this. I remember having
fixed them i
That cleared up the error, thanks Ryan.
FYI I took that config straight out of the documentation -
http://haproxy.1wt.eu/download/1.3/doc/architecture.txt
3.1. Alternate solution using Stunnel
===
Is the documentatio
Craig,
It looks like you're trying to specify the listen section's bind as its
name. I think this is what you want:
listen www 64.164.194.16:80
(Any name will work in place of www).
Ryan
On 01/13/2010 08:09 PM, Craig Carl wrote:
All -
I have a simple config using stunnel. I am trying to l
Le Jeudi 14 Janvier 2010 00:28:19, Cyril Bonté a écrit :
> "\x00\x00" /* client capabilities */
> "\x00\x00" /* extended client capabilities */
Well, this bytes are too simplified to work (it misses some bits for mysql 4.1
compatibility).
thos
Hi again Hervé,
Le Mercredi 13 Janvier 2010 12:56:30, Hervé COMMOWICK a écrit :
> Hi Cyril,
>
> 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 do a *
Hi Ross,
On Wed, Jan 13, 2010 at 12:12:04PM -0500, Ross West wrote:
> I can see a small confusion here because I've used the wrong
> terminology. Proxy is not the correct term, as there are actual proxy
> devices out there (eg: Squid) which are generally visible to the
> client/server and shouldn'
On Wed, Jan 13, 2010 at 1:15 PM, Willy Tarreau 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 appli
Hi Paul,
Le Mercredi 13 Janvier 2010 22:15:51, Willy Tarreau a écrit :
> On Wed, Jan 13, 2010 at 12:31:09PM -0800, Paul Hirose wrote:
> > (...)
> > So I
> > do have trouble with connections of a long duration but where there is
> > little actual data. Usually some client application that makes a
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 netwo
Hi Paul,
On Wed, Jan 13, 2010 at 12:31:09PM -0800, Paul Hirose wrote:
(...)
> >> as a workaround, you can disable the mysql connection_errors checking by
> >> adding max_connect_errors=9 in you my.cnf
(...)
> I don't know what the mysql-check does (sorry, haven't dug through the
> actual
2010/1/13 Cyril Bonté :
> 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 do a *real
Hi Hervé,
First of all, sorry, I wanted to contact you directly to know the status of
this development, but I didn't find your email.
I realized too late that I saw it in the commit sooner in the morning :)
Le Mercredi 13 Janvier 2010 12:56:30, Hervé COMMOWICK a écrit :
> Hi Cyril,
>
> I know t
>> That's more of an issue with the site than a (proxy based) load
>> balancer - the LB would be doing the exact same thing as the client.
WT> Precisely not and that's the problem. The proxy cannot ask the user
WT> if he wants to retry on sensible requests, and the cannot precisely
WT> know what
Hi Cyril,
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 do a *real* mysql ping, but at the
moment, the checks API doesn't let me handle this in a cleaner
Hi Willy,
Be careful with the new "mysql-check" option introduced in the development
branch.
http://haproxy.1wt.eu/git?p=haproxy.git;a=commit;h=698ae00fc272bf5f4e159922546347066bd66378
It won't work with distant backends :
mysql has a mechanism to block hosts that open connection whithout closing
18 matches
Mail list logo
