[Pacemaker] Stopping 300 Resources Causes Node To Go Offline

Gruen, Wolfgang wgruen at idirect.net
Sun Jan 29 19:40:37 EST 2012

We are running a cluster with 15 nodes and are running with 300 resources.

*** Stopping 300 Resources Causes Node 2 To Go Offline
Used the command cibadmin --replace --scope resources --xml-text "<resources/>"
result was all running resources stopped, but node 2 went offline
[root at pcs_linuxha_2 ~]# crm status

Connection to cluster failed: connection failed
[root at pcs_linuxha_2 ~]# /etc/init.d/pacemaker status
pacemakerd dead but pid file exists
[root at pcs_linuxha_2 ~]# /etc/init.d/corosync

This electronic message and any files transmitted with it contains
information from iDirect, which may be privileged, proprietary
and/or confidential. It is intended solely for the use of the individual
or entity to whom they are addressed. If you are not the original
recipient or the person responsible for delivering the email to the
intended recipient, be advised that you have received this email
in error, and that any use, dissemination, forwarding, printing, or
copying of this email is strictly prohibited. If you received this email
in error, please delete it and immediately notify the sender.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120130/7524f291/attachment-0002.html>

More information about the Pacemaker mailing list