haproxy

I have 2 virtual machines with opensuse 12.2 VM1 ip: 192.168.88.96 apache2: 192.168.88.96:80 haproxy: ? ? virtual ip: 192.168.88.99 VM2 ip: 192.168.88.97 apache2: 192.168.88.97:80 haproxy: ?

RE: haproxy

Hi, you probably need to set the transparent keyword on the bind line, if you want to bind to a possible non-existing ip address. See docs [1]. > how will keepalived communicate with haproxy? It doesn't communicate with haproxy afaik. Why should it? Cheers, Lukas [1] http://cbonte.github.io

RE: haproxy

In that case what is haproxy for? I thought it is suppose to be a load balancer and keepalived is a heartbeat to detect the balancer? On 16 Apr 2013 17:05, "Lukas Tribus" wrote: > Hi, > > you probably need to set the transparent keyword on the bind line, if > you want to bind to a possible non-ex

Re: haproxy

Hi Joshua, Keepalived doesn't communicate with haproxy. It keeps track of processes, interfaces, etc. Generally you use vrrp_script option in keepalived configuration to keep track of processes (are they running? In your case haproxy) and if the process is not running, reduce prio by X which caus

Re: haproxy

Thank you. Thats what i was confused about. Vrrp_script needs to keep track, do i keep track of the server lan ip or the virtual ip or the haproxy ip? If it is not running then increase the weight of the other server. On 16 Apr 2013 17:16, "Pär Åslund" wrote: > > Hi Joshua, > > Keepalived doesn'

RE: haproxy

> In that case what is haproxy for? To load-balance traffic on different backends. Haproxy can't load-balance its own load, that would be a catch-22. > I thought it is suppose to be a load balancer HAproxy is a reverse proxy and a load balancer, yes. > keepalived is a heartbeat to detect the

RE: haproxy

> So do i broadcast the ip for haproxy to the web? Or the virtual ip? > Which do i connect from the WAN? Configuration would usually look like this: HAproxy server 1 (active): physical IP: 192.168.0.11/24 virtual IP: 192.168.0.20/24 (active) HAproxy server 2 (standby): physical IP: 192.168.0.12/2

RE: haproxy

Thank you. In short it doesnt matter what ip i assign haproxy to? It can be 192.168.0.20:8080 since its on a different port. For the virtual ip i got it, added it in my yast>network devices, however unable to get it to listen for connections. Guess i need to readup more on it. Once again thanks,

Re: haproxy

Ok, breakthrough. I finally got the picture sorted out. The flow should be query vip, keepalived will detect which LB is alive and sends the query to them, the LB will then round robin the query to the appropriate server. With that i will need min 2vm for 2lb and 4apache to demo it. Question: If

Layer4 connection problem: Resource temporarily unavailable

I run about 50 FTP server clusters. Each cluster consists of 3 backend FTP servers. I am using haproxy to load balance each of these clusters to three backends. I am using smtpchk to verify the FTP banner. I run the HTTP admin interface, which shows the status of all the front/backends. Running ha

RE: Layer4 connection problem: Resource temporarily unavailable

Hi Ben! > Running haproxy 15 development snapshot from 12/30/2012 I suggest you upgrade to the latest snapshot available from [1]. It doesn't make sense to troubleshoot problems on old development snapshots if you are 155 commits back (you are missing critical bug fixes!): > #:~/haproxy$ git lo

Re: 'maxconn' usages

Thanks a lot for the clarifications. So now I understand the differences between 'maxconn' in different places: 1. if it is in the global section, it specifies the maximum number of concurrent connections the HAProxy process will handle at any point of time. 2. if it is in a frontend section, it s

RE: 'maxconn' usages

Hi Merton, > Please let me know if the above understanding is correct. Yes, thats the concept. > if I have multiple backends (multiple server options), does the > sum of 'maxconn' of their server options have to be no more than > the 'maxconn' of their corresponding frontend? Yes that does ma

proxy name filtering introduced in haproxy 1.5

Hi Guillaume and Willy, I've just recompiled haproxy 1.5 with the latest commits. The patch containing a box to filter proxies is useful but I think we should remove the "autofocus" keyword from the generated html. Currently, it prevents using the keyboard to scroll the page without having to

Re: proxy name filtering introduced in haproxy 1.5

Hi Cyril, On Wed, Apr 17, 2013 at 12:34:56AM +0200, Cyril Bonté wrote: > Hi Guillaume and Willy, > > I've just recompiled haproxy 1.5 with the latest commits. > The patch containing a box to filter proxies is useful but I think we > should remove the "autofocus" keyword from the generated html.

Re: 'maxconn' usages

Hi Lukas, Thanks very much for your confirmations and the Stackoverflow post. I just want to expand a little on the last question relating to websockets connections. Let's say I have a backend which exclusively deal with long-lived connections: websockets and xdr-streaming. These connections tend

HA Proxy FTP Load Balancing Timeout

I have a HA Proxy server(1.4), thzt is load balacing FTP traffic to Six FTP servers. I noticed that Load Balancer is dropping traffic after 50 sec, where as there was a valid ftp control port and Large file transfer was in progress over data port. I tried using tcpka in defaults section, but

Re: [PATCH 0/3] Add http-check agent-hdr option

Hi Willy, On Mon, Apr 01, 2013 at 11:29:12PM +0200, Willy Tarreau wrote: > Hi Simon, > > Sorry for the long delay and thanks for waiting. I've just reviewed your > two patch series (16 total). They're pretty good in my opinion. likewise, sorry for the delay. > I'm seeing a few points we'll prob

Re: [PATCH 0/3] Add http-check agent-hdr option

Hi Simon, On Wed, Apr 17, 2013 at 02:36:36PM +0900, Simon Horman wrote: > Hi Willy, > > On Mon, Apr 01, 2013 at 11:29:12PM +0200, Willy Tarreau wrote: > > Hi Simon, > > > > Sorry for the long delay and thanks for waiting. I've just reviewed your > > two patch series (16 total). They're pretty go

Re: [PATCH 0/3] Add http-check agent-hdr option

On Wed, Apr 17, 2013 at 08:03:11AM +0200, Willy Tarreau wrote: > Hi Simon, > > On Wed, Apr 17, 2013 at 02:36:36PM +0900, Simon Horman wrote: > > Hi Willy, > > > > On Mon, Apr 01, 2013 at 11:29:12PM +0200, Willy Tarreau wrote: > > > Hi Simon, > > > > > > Sorry for the long delay and thanks for wa