On Mon, Nov 10, 2008 at 05:42:50PM +0100, Jvrg Streckfu_ wrote: > It seems that the first ip (10.0.0.1) which is also the public ip for the > webserver pool is unavailable. Each request, which should be forwarded to the > first webserver will stuck for a moment and then relayd redirects it to > the next server in the pool. The ip address 10.0.0.1 will be skipped at any > time. > > For me it looks like an ip conflict between relayd and the first webserver > If I take a different ip for $www_public, e.g 10.0.0.4 relayd works as > expected.
Are they running on separate machines? Have you assigned the same IP to two boxes? I guess you're looking for CARP between the loadbalancer and first web server, but I think it'd be cleaner to have two loadbalancers and redundancy between them.
