You're looking for track
http://cbonte.github.io/haproxy-dconv/configuration-1.5.html#track
-Bryan
On Fri, May 1, 2015 at 5:34 PM, Michael Bushey wrote:
> I have a master-master-master MySQL DB cluster, but run into deadlocks
> if writes from one web node are across multiple DB servers, so I
I have a master-master-master MySQL DB cluster, but run into deadlocks
if writes from one web node are across multiple DB servers, so I have
this:
listen QA-Single-DB1:23321
bind 127.0.0.1:23321
option httpchk
default-server port 9200 inter 5000 fastinter 2000 rise 2 fall 2
serv
Le 01/05/2015 21:57, Shawn Heisey a écrit :
On 5/1/2015 12:30 PM, Cyril Bonté wrote:
Message from syslogd@ at Fri May 1 11:29:51 2015 ...
localhost.localdomain haproxy[23754]: backend be-services-dev-8443 has
no server available!
Any other ideas?
Please provide your configuration, I'm quite
On 5/1/2015 12:30 PM, Cyril Bonté wrote:
>> Message from syslogd@ at Fri May 1 11:29:51 2015 ...
>> localhost.localdomain haproxy[23754]: backend be-services-dev-8443 has
>> no server available!
>>
>> Any other ideas?
>
> Please provide your configuration, I'm quite sure it's a
> misconfiguration
Hi,
We're running a haproxy as a TLS unwrapping daemon (socket to socket) and
are running into some cases where processes will spin at 100% CPU for 5-30
seconds.
It looks related to half-closed or resetting TCP connections out to end
users, and always self-recovers after some amount of time.
The
I've built a shell script that will gather OCSP responses with the
'openssl' binary for a list of certificates. This will be very helpful
for me when I get a production haproxy running that does OCSP stapling.
It consists of a script, a config file, and a set of certificates that
probably need to
Le 01/05/2015 19:36, Shawn Heisey a écrit :
On 4/30/2015 4:08 PM, Cyril Bonté wrote:
No, you didn't provide "err" as the argument.
It should be something like :
log 127.0.0.1 local0 notice err
Also, ensure you don't have a "log global" somewhere in those backends
or in the previously decl
On 4/30/2015 4:08 PM, Cyril Bonté wrote:
> No, you didn't provide "err" as the argument.
> It should be something like :
> log 127.0.0.1 local0 notice err
>
> Also, ensure you don't have a "log global" somewhere in those backends
> or in the previously declared "defaults" section.
I now have
8 matches
Mail list logo