On 08/17/2009 01:08 PM, Dominik Klein wrote: > > The constraints look okay, but without logs, we cannot say why it does > not do what you want. > > Also: look at the stonith device configuration: Is it okay for both > primitives to have the same ip configured? I'd guess that will not > successfully start the resource!? Maybe that's it already. > > I'd guess there was some failure before which brought up this situation > (probably stonith start fail and stop fail)? > > It shouldn't turn off nodes at random. There's usually a pretty good > reason when the cluster does this. > > Btw: the better way to make sure, a particular resource is only started > on one node but never on the other is usually to configure -INFINITY for > the "other" node instead of INFINITY for the node you want it to run on. > > Regards > Dominik
Well I can certainly change the constraints to neg INFINITY. Well as for the ip addr, like I said it's confusing. Each IPMI card is directly attached to one NIC in each host. That's why I can use the same IP. The connection is fine as well, I can go the ipmi webinterface using a browser just fine. I did monitor the logs and tried to start it again and the only thing I found was this: Aug 17 11:07:13 nagios2 stonithd: [5768]: info: external_run_cmd: Calling '/usr/lib/stonith/plugins/external/ipmi status' returned 256 then it went into failed state and tried to start on the other node, which of course failed as well. Still this seems to be the problem. I just happened to find out that I can't connect using ipmitool from nagios2 to nagios1. Via Webbrowser it works fine and ipmitool works fine for nagios1 to nagios2. But this explains why the resource could not be started. [r...@nagios2 ~]# ipmitool -H 11.0.0.2 -U root -P xxx power status Error: Unable to establish LAN session Unable to get Chassis Power Status So I first have to fix this but then I have to look into why heartbeat tried to start it on the wrong node - maybe rewriting my constraints will work. Thanks for the input Dominik - as always you are my saviour :) _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
