Sometimes the poweroff is caught by the OS, and therefore launches a soft
halt.
Try to see if those two imply similar response or not.
ipmitool -H host1 -U root1 -P secret1 power off
ipmitool -H host1 -U root1 -P secret1 power cycle
or whatever works with ipmilan
2013/1/21 zorg z...@probesys.com
(13.01.10 13:35), Andrew Beekhof wrote:
On Wed, Jan 9, 2013 at 8:57 PM, Kazunori INOUE
inouek...@intellilink.co.jp wrote:
Hi Andrew,
I have another question about this subject.
Even if pengine, stonithd, and attrd crash after pacemakerd is killed
(for example, killed by OOM_Killer), node
In fact ipmitool work like a charm
It's pacemaker witch decide to restart the cluster after send other
ipmitool command
It's seem we can change this behavior with stonith action
thanks
Le 22/01/2013 09:24, Emmanuel Saint-Joanis a écrit :
Sometimes the poweroff is caught by the OS, and
It's pacemaker witch decide to restart the cluster after send other
ipmitool command
Pacemaker can behave in fairly evil ways, but it's a bit stern to qualify
it as witch ;)
2013/1/22 zorg z...@probesys.com
In fact ipmitool work like a charm
It's pacemaker witch decide to restart the
HI,
on Fedora 17 corosync pacemaker version 1.1.7 (fedora update)
all nodes quit corosync pacemaker after a while
[root@node140 ~]# systemctl status corosync
corosync.service - Corosync Cluster Engine
Loaded: loaded (/usr/lib/systemd/system/corosync.service; enabled)
Active:
On 01/18/13 13:33, E-Blokos wrote:
Hi,
I got this doc
http://clusterlabs.org/doc/Cluster_from_Scratch.pdf
so I'm trying to follow the doc but got confused
when pcsd is not included in any Fedora 17 package
but this doc is including Fedora 17 installation.
I saw there
http://clusterlabs.org/doc/
OK. So you have a corosync cluster of nodes with pacemaker managing
resources on them, including (of course) STONITH.
What's the best/proper way to shut down a node, say, for maintenance
such that pacemaker doesn't go trying to fix that situation and
STONITHing it to try to bring it back up,
Hi Jiaju,
I understood about the complete solution.
However because this issue causes the critical problem that multiple
resources start, Could you apply this request or simply revert a
commit to tentatively handle this issue until you are resolved at the
summer? I think that we are difficult to
Hi All,
I registered a problem at bugzilla in place of Miss Ikeda.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5133
Best Regards,
Hideo Yamauchi.
--- On Thu, 2013/1/10, Junko IKEDA tsukishima...@gmail.com wrote:
Hi,
I'm running Stateful RA with Pacemaker 1.0.12, and found that its
