Thanks for the help, Eric. Its interesting that you mentioned taking down cman BEFORE taking the interfaces down, because when I was testing my failover I did: ifdown bond0. My thinking was that the heartbeat would die and everything would work. It didn't occur to me that it would mess up cman - do you think that's what's doing it? Should I instead just pull the cables? (I'm asking because it's a long drive to the site just for the test, but will if you think that's the problem). Thanks again, Jeff -----Original Message----- From: Eric Kerin [mailto:eric@xxxxxxxxxxx] Sent: Monday, July 18, 2005 1:51 PM To: Jeff Harr Cc: linux clustering Subject: RE: kernel: CMANsendmsg failed: -101 On Mon, 2005-07-18 at 11:26 -0400, Jeff Harr wrote: > First of all, thanks for the reply. I've run "service cman stop" so > many times my fingers hurt and I've never had a problem. I've never run > /etc/init.d/cman stop before and its going to be difficult for me to do > it atm. I suppose if I run it and it outputs something dreadful then > I've found my answer :) Thanks for the response...at least I have > something better than a google search to confirm the most likely > problem. > > Jeff One thing to check, make sure you have the Kill entries in the rc0 and rc6 directories: ls /etc/rc.d/rc0.d/K??cman Also check that cman is set to stop before the network interfaces are taken down. (Mine is set to stop cman at 79 and network at 90.) If you want to reset cman's startup/shutdown scripts back to their default settings, use "chkconfig --del cman", and then "chkconfig --add cman". Thanks, Eric Kerin <eric@xxxxxxxxxxx> -- Linux-cluster@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/linux-cluster
