Ok, that fixed it. Actually, stopping acpid caused the system to never receive any power off message. But you got me on the right track of thinking and I modified the config file to read "poweroff -f" and now it turns off. It turns back on too, but I think that's because of ILO's autoboot setting, and beyond the control of redhat cluster :) Lon: you are THE MAN. Everyone: I appreciate all the help. -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Lon Hohberger Sent: Tuesday, July 19, 2005 4:26 PM To: linux clustering Subject: RE: kernel: CMANsendmsg failed: -101 On Mon, 2005-07-18 at 14:54 -0400, Jeff Harr wrote: > Well, its actually on a Proliant blade and I'm going in through a > virtual console (an ILO) to issue the ifdown commands. I'm doing > power-fencing on the ILO itself (its one of the ways you can do it with > Redhat Cluster). Eeeeek! Ok, so, it's trying to be fenced, but it's hanging in shutdown. The fencing is causing the shutdown, right? chkconfig --del acpid service acpid stop With ACPID running, the virtual power button press gets translated to "shutdown -h now" instead of "power off NOW", which is what the cluster wants. -- Lon -- Linux-cluster@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/linux-cluster