> I'd need the logs from both nodes (in particular the one acting as DC). > Try using hb_report - it gathers all the relevant information
> On Thu, May 28, 2009 at 4:21 PM, <[email protected]> wrote: > > Hello All, > > > > I'm running a two-node cluster with pacemaker 1.0.2 and heartbeat 2.99 on > > SLES 10 SP2 and I'm having trouble migrating the resources for testing > > purposes. > > > > I've defined a single resource group (called websphere) and two clones - > > pingd, and stats. The group has an IP addr resource, an ipsrc resource, > > and two WAS7 resources (custom websphere RA adapted from WAS6). > > > > The cluster has been running with no obvious issues since late April. I > > began this morning by attempting a "crm node standby plapwas04", since > > plapwas04 was the active node, but this had no real effect on the cluster > > resources. > > > > As you can see from the attached logs, I've made several attempts to force > > the issue, including stopping and later starting heartbeat on the primary. > > The resources never transitioned during my attempts. > > > > Could this be related to STONITH - I had riloe resources configured, but I > > later removed them. You can also see where I did a cleanup of those > > orphaned resources in the logs. > > > > Also, the logs don't show any monitor operations happening for any of my > > resources. > > > > I'm at a loss for the moment - the resources are running, which is good - I shutdown all heartbeat processes on the secondary node (plapwas05) tonight. The primary node (plapwas04) became the DC, the cluster resources stopped on plapwas04, and then restarted on the secondary. I think that I had not restarted heartbeat on plapwas05 after I removed the stonith resources. I performed several "crm node standby" and "crm node online" commands and the resources failed over as expected each time. Thanks, Justin _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
