load balancer should not be listening on the virtual IP

Discussion in 'HOWTO-Related Questions' started by nickcasey, May 13, 2012.

  1. nickcasey

    nickcasey New Member

    I seem to be having a problem with the LB side of things.

    In http://www.howtoforge.com/setting-up-a-high-availability-load-balancer-
    with-haproxy-heartbeat-on-debian-lenny-p2 you have said that

    As lb2 is the passive load balancer, it should not be listening on the virtual IP address as long as lb1 is up. We can check that with:

    lb2:

    ip addr sh eth0

    but the result shows both lb1 and lb2 are listening to the vIP

    Please can you help.
     
  2. nickcasey

    nickcasey New Member

    heartbeat start output

    [email protected]:~# /etc/init.d/heartbeat start
    Starting High-Availability services: IPaddr[2805]: INFO: Running OK
    ResourceManager[2782]: CRITICAL: Resource 192.168.0.50 is active, and should not be!
    ResourceManager[2782]: CRITICAL: Non-idle resources can affect data integrity!
    ResourceManager[2782]: info: If you don't know what this means, then get help!
    ResourceManager[2782]: info: Read the docs and/or source to /usr/share/heartbeat/ResourceManager for more details.
    CRITICAL: Resource 192.168.0.50 is active, and should not be!
    CRITICAL: Non-idle resources can affect data integrity!
    info: If you don't know what this means, then get help!
    info: Read the docs and/or the source to /usr/share/heartbeat/ResourceManager for more details.
    ResourceManager[2782]: CRITICAL: Non-idle resources will affect resource takeback!
    ResourceManager[2782]: CRITICAL: Non-idle resources may affect data integrity!
    Done.
     
  3. nickcasey

    nickcasey New Member

    seems as though all i needed to do was a restart of heartbeat and let the conflicts resolve themselves
     

Share This Page