Remi Broemeling wrote:
The second QUIT signal on boot2 cleans this situation up somewhat, as corosync then treats that as a harder termination and actually makes it happen (apparently does, anyway). Thus stopping with the init script does actually kill corosync; but it does so slowly -- and, to my mind, quite dangerously; as a momentary split-brain is implicit in each shutdown.
After some debugging, I'd bet on lrmd and heartbeat as a problem here. If you send QUIT signal to corosync, it will send TERM signal to crmd, which will notice that and send TERM signal to lrmd. That one doesn't do a thing about it.
Since lrmd keeps track of local resources, crmd sends information to DC which then starts resources on another machine. Since lrmd on local machine doesn't stop, we end up with two different machines running the same resources.
_______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
