25.08.2011 23:22, mark - pacemaker list wrote:
[snip]
> So, I disabled pacemaker from starting via the normal route and just
> added a line to /etc/rc.local that starts it, since that's the absolute
> last thing done at boot. I didn't want to mess with the chkconfig
> settings in the init script a
Hello again,
Replying to my own message with a "for the archives" post, my issue with
services being started concurrently after a node reboot came down to the
fact that I'm using the VirtualDomain RA, but by default CentOS 6.0 and
Scientific Linux 6.1 (and presumably RHEL6 as well) start libvirtd
;ignore" \
stonith-action="reboot" \
stonith-timeout="30s" \
maintenance-mode="false" \
pe-error-series-max="5000" \
pe-warn-series-max="5000" \
pe-input-series-max="5000" \
dc-deadtime="2min" \
stonith-enabled="false"
Hi,
Has any one here come across this issue?.
--- On Wed, 17/8/11, ihjaz Mohamed wrote:
From: ihjaz Mohamed
Subject: [Pacemaker] How to prevent a node that joins the cluster after reboot
from starting the resources.
To: pacemaker@oss.clusterlabs.org
Date: Wednesday, 17 August, 2011, 12:23 PM
Hi All,
Am getting an unmanaged error as shown below when one of the node is rebooted
and comes back to join the cluster.
Online: [ aceblr101.com aceblr107.com ]
Resource Group: HAService
FloatingIP (ocf::heartbeat:IPaddr2): Started aceblr107.com
(unmanaged) FAILED
acesta
