On Thu, Mar 6, 2014 at 3:50 PM, Willy Tarreau w...@1wt.eu wrote:
We've been thinking about implementing a simple async resolver in
combination with health checks to at least automatically update server
addresses at EC2 and similar horrible environments where a reboot can
change your server's
Hi Lukas,
Thanks for replying.
Below the information:
HA-Proxy version 1.5-dev22-1a34d57 2014/02/03
Copyright 2000-2014 Willy Tarreau w...@1wt.eu
Build options :
TARGET = linux2628
CPU = generic
CC = gcc
CFLAGS = -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat
Hi,
backend b_catchall
log global
mode http
option httplog
option http-server-close
#--- speedtest
use-server www.speedtest.net if { hdr_dom(host) -i speedtest }
server www.speedtest.net *:80
This is an unsupported configuration, you cannot specify an asterisk
as address.
This
Thanks Lukas. But why does it say this here for server in the man?
Address “0.0.0.0″ or “*” has a special meaning.
It indicates that the connection will be forwarded to the same IP
address as the one from the client connection. This is useful in
transparent proxy architectures where the client’s
Hi,
Thanks Lukas. But why does it say this here for server in the man?
Address “0.0.0.0″ or “*” has a special meaning.
It indicates that the connection will be forwarded to the same IP
address as the one from the client connection. This is useful in
transparent proxy architectures where
I understand. Is this something that could be taken up for a future version?
Also, what maxconn value do you recommend?
Thanks
On 5 March 2014 16:11, Lukas Tribus luky...@hotmail.com wrote:
Hi,
Thanks Lukas. But why does it say this here for server in the man?
Address “0.0.0.0″ or “*” has
Hi,
I understand. Is this something that could be taken up for a
future version?
Not a trivial thing todo. I think an internal resolver implementation
in haproxy would be needed, as gethostbyname() and friends are blocking
(nginx has its own resolver for example).
I don't think there are use
Hi,
On Thu, Mar 06, 2014 at 01:31:33AM +0100, Lukas Tribus wrote:
Hi,
I understand. Is this something that could be taken up for a
future version?
Not a trivial thing todo. I think an internal resolver implementation
in haproxy would be needed, as gethostbyname() and friends are
Hello,
Is this a known bug in HAProxy 1.5?
When I use 0.0.0.0 or * as server address for a certain host, HAProxy
crashes with a oom_killer log. This is what is in the man page:
server
...
Address “0.0.0.0″ or “*” has a special meaning.
It indicates that the connection will be forwarded to the
Hi Fred,
Is this a known bug in HAProxy 1.5?
When I use 0.0.0.0 or * as server address for a certain host, HAProxy
crashes with a oom_killer log.
Thats certainly not expected. Does the OOM conditional really come
from HAProxy?
server
...
Address “0.0.0.0″ or “*” has a special
10 matches
Mail list logo
