On 12/13/2012 10:00 AM, Josh Bowling wrote: > I have a two node cluster running Ubuntu 12.04 and had everything working > just fine (STONITH, failover, etc.) until I changed up the virtual machines > and the crm configuration to match (my virtual machines get booted by > pacemaker on the survivor node when a failover occurs). The primary node > currently has a status of "UNCLEAN (online)" as it tried to boot a VM that > no longer existed - had changed the VMs but not the crm configuration at > this point. I have since modified the configuration and synced data with > DRBD so everything is good to go except for pacemaker.
So the second node was offline? ... as it did not fence the primary node? > > Is there a way to remove the error and set the UNCLEAN node to just > online? I think since it's currently seen as unclean, the new > configuration won't propagate to the secondary node. In order to make > ensure high availability, both machines need to be clean, online, and have > the same crm configuration. Assuming the second node does not run pacemaker .... switch the cluster into maintenance-mode, adjust your crm configuration to reflect your changes to the VMs and restart pacemaker. Once you made sure all is in place and all vm configurations are successfully probed disable maintenance-mode and start pacemaker on the second node. > > I'm hoping there's a quick way to get this cluster back on track. I doubt > one of my servers are going to fail any time soon, but you never know. Regards, Andreas -- Need help with Pacemaker? http://www.hastexo.com/now > > Thanks in advance, > > Josh > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
