LAMP - perbal and wackamole - suggestions pls.

Ashish Padave ashishpadave at
Fri May 11 21:42:44 UTC 2007


The answer I hoped for!

So does that mean, perlbal is running on both machines?

Requests always go to say Machine A (IP 1), perlbal decides where the
request should be completed, Machine A (IP 1) or Machine B (IP 2), is that

If Machine A fails, wackamole moves IP 1 to IP machine B, so that all future
requests are served by Machine B.

Please correct me if I am missing something here

Thanks a lot!! :)


----- Original Message ----- 
From: "Ask Bjørn Hansen" <ask at>
To: "Ashish Padave" <ashishpadave at>
Cc: <perlbal at>
Sent: Friday, May 11, 2007 10:06 PM
Subject: Re: LAMP - perbal and wackamole - suggestions pls.

> On May 11, 2007, at 1:41 PM, Ashish Padave wrote:
>> If one of the machines were to go down you can tell perlbal to only 
>> server from the single apache without having to restart anything.
> perlbal will do that automatically.
>> This works very well if apache/mysql goes down, but if the entire  box 
>> fails then you are in trouble. Generally speaking having  services that 
>> reconfigure network settings and take ownership of  ips are prone to 
>> failure.
> wackamole is extremely robust and in simple configurations heartbeat  is 
> too.  Have you tried it?
>> My BIG question is can perbal with wackamole or something else,  help me 
>> to serve requests even if the machine hosting perlbal  (Machine A) went 
>> down completely.
> Yup - to make sure the users always reach a working perlbal, you can  use 
> wackamole or heartbeat to move the public IP or IPs to the  working server 
> when the other one fails.
>   - ask
> -- 
> -

More information about the perlbal mailing list