[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [Linux-cluster] kernel: CMANsendmsg failed: -101

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 redhat com
[mailto:linux-cluster-bounces redhat com] On Behalf Of Lon Hohberger
Sent: Tuesday, July 19, 2005 4:26 PM
To: linux clustering
Subject: RE: [Linux-cluster] 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
> Redhat Cluster). 


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

-- Lon

Linux-cluster mailing list
Linux-cluster redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]