Hello,
OK, here is my setup
I am running 2 load balancers with a bare CentOS 5.3 install with heartbeat. We are trying to balance 2 windows 2008 web servers with IIS. (but the problem is with the load balancers)
here is the config files for Load Balancer1
Quote:
DEVICE=eth0
BOOTPROTO=none
BROADCAST=192.168.4.255
HWADDR=**:**:**:**:**:**
IPADDR=192.168.4.231
NETMASK=255.255.255.0
NETWORK=192.168.4.0
GATEWAY=192.168.4.1
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
------------------------
DEVICE=eth0:0
BOOTPROTO=none
BROADCAST=192.168.4.255
IPADDR=192.168.4.232
NETMASK=255.255.255.0
NETWORK=192.168.4.0
GATEWAY=192.168.4.1
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
ONPARENT=yes
-----------------------
DEVICE=eth0:1
BOOTPROTO=none
BROADCAST=192.168.4.255
IPADDR=192.168.4.233
NETMASK=255.255.255.0
NETWORK=192.168.4.0
GATEWAY=192.168.4.1
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes
ONPARENT=yes
|
...and the same applies with Load Balancer2 except different IP addresses (same network and subnet though)
There is a python script that should run on LB2 to try to connect to LB1 every 2 seconds and runs continuously until it will not communicate with LB1 for so many seconds then fails over to LB2 and changes IP's to match LB1's originals.
The output should say "Trying to Reconnect. Attempt number 1."
and that would repeat to number 2,3,4 and so on.
I am able to ping the boxes from one another but LB2 doesn't even try to connect to LB1, it fails over immediately.
Quote:
[root@LB2 ~]# python failover_prod.py
Thu Apr 9 14:03:13 2009 Failover Script Started.
Thu Apr 9 14:03:13 2009 Heartbeat Check Started.
Thu Apr 9 14:03:16 2009 Becoming Primary Load Balancer for 192.168.4.231
111
111
111
111
111
222
222
222
222
222
333
333
333
333
333
Thu Apr 9 14:03:26 2009 Failover Complete.
|
Is the problem with the systems? Am I missing a package for heartbeat? Is heartbeat even the problem? Any ideas would be much appreciated.
Thank you very much for looking!