Hi Daniel,
Op 20-5-2018 om 2:08 schreef Daniel Corbett:
Hi Pieter,
While I'm not sure what may be happening in regards to the
server-template messages that you have pointed out.
I have ran into the unix socket one a couple weeks ago and have been
meaning to send this patch to the mailing
Hi List,
With 1.8.8 ran into this, tried latest 1.9dev snapshot seems to have the
same issue..
Running with 3 threads, a template for 8 servers, and only 2 ip's in the
dns response, neither of which is actually 'up' one responds with
'L4TOUT in 1004ms' the other with 'L4CON in 0ms' on stats
Hi Pieter,
While I'm not sure what may be happening in regards to the
server-template messages that you have pointed out.
I have ran into the unix socket one a couple weeks ago and have been
meaning to send this patch to the mailing list.
What is happening is that currently only AF_INET
Hi List,
Is it expected to get warnings on unix-sockets and server-template that
don't have enough A records.
It seems like its trying to do something wrong..
Im using a global server state file with a defaults that loads it:
global
server-state-file /tmp/haproxy_server_state
defaults
Hi list, I'm playing with SPOE and modsecurity contrib from HAProxy 1.8.9. I've
a couple of doubts and issues that I'll describe just below my config and some
loggings:
= haproxy.conf
listen my-front
log 127.0.0.1:514 format rfc5424 local0
timeout client 5s
timeout connect 5s
Hello,
On 19 April 2018 at 11:09, Sander Hoentjen wrote:
> I just tried 1.1.1-pre5, and I still have the same issue.
I'm running 1.1.1-pre6 now with good results. You may want to check that out.
cheers,
lukas
6 matches
Mail list logo