Greetings I have two LDAP servers (master and Slave) with two eth NICs each. Heartbeat (Linux-HA) monitors the eth0 in both because of the Virtual IP address. the eth1 is used to replications of LDAP. When the connection of eth0 in Master comes down, the heartbeat in Slave starts the slapd as master, just like as I expected. But when this fail happens the MASTER heartbeat don't do nothing, keeping slapd master running, and so, since the replications are done via eth1, this kind of configuration can't happen because there are two LDAP masters running, with replications on eth1!
What I want to do is when the MASTERs eth0 comes down (line or something else...) hearbeat do something to the running script (start, stops or restart (whatever)), after that I could do whatever I want. I think this happens because heartbeat can't disting where is the fail! Is that on the other machine or is in my connection? because when something happens it sends the message: "node: xxxx is dead", and sometimes this is wrong because the node xxxx is up but heartbeats can't reach it. I know that heartbeats can/should use a serial connection to the other node, but, I try to heartbeat both NICs and it runs normally except when the MASTERS eth0 comes down nothing happens on SLAVE. cheers Hugo -- redhat-list mailing list unsubscribe mailto:redhat-list-request@;redhat.com?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
