Hi,

On Thu, Oct 08, 2009 at 11:06:45AM -0500, Terry L. Inzauro wrote:
> list,
> 
> I have a cluster that is not reporting the correct information.
> The Xen resource named XENVM is actually running on node1 when
> crm_mon and crm_resource both show it to be running on node2.

The information the "cluster" has (we should say CRM) may not
always correspond to reality if the resources are started/stopped
by hand and there's no monitor operation defined. It may also
happen if the RA is broken and doesn't report truth.

> I now this to be the case whenever I move the resource manually
> with crm_resrouce.

I'm slightly confused here as to what exactly happened.

> Furthermore, after I manually move the Xen
> resource named XENVM,

Manually? You mean by not using crm_resource?

> the original node that was
> running XENVM reboots (after a few minutes go by) with nothing
> logged (may be caused by a watchdog timer).
> 
> After stopping and starting heartbeat on both nodes I am unable
> to reproduce the issue, but I am curious nonetheless.  Can
> anyone suggest some steps I can take if I see this again?

I suppose that the logs are still there as well as the pengine
files, so you can just capture the incident using hb_report. That
is, if you know when the it actually started.

Thanks,

Dejan

> Version information:
> r...@node2:/var/lib/heartbeat/crm# apt-show-versions | grep heart
> heartbeat/lenny uptodate 3.0.beta1+hg20090915-1~bpo50+1
> libheartbeat2/lenny uptodate 3.0.beta1+hg20090915-1~bpo50+1
> pacemaker-heartbeat/lenny uptodate 1.0.5+hg20090915-1~bpo50+1
> 
> 
> On node1:
> -----------------
> r...@node1:/var/lib/heartbeat/crm#  crm_resource --resource XENVM --locate
> resource XENVM is running on: node2
> 
> 
> r...@node1:/var/lib/heartbeat/crm# xm list
> Name                                        ID   Mem VCPUs      State   
> Time(s)
> Domain-0                                     0  3727     2     r-----    119.0
> XENVM                                      2   256     1     -b----      2.3
> 
> 
> 
> On node2:
> -----------------
> r...@node2:/var/lib/heartbeat/crm# crm_mon -1
> 
> 
> ============
> Last updated: Thu Oct  8 10:39:46 2009
> Stack: Heartbeat
> Current DC: node1 (6f018041-6820-42d2-a14b-811dcf68454e) - partition with 
> quorum
> Version: 1.0.5-7d025385e2cd82f6c65be75007a36a83da72623a
> 2 Nodes configured, unknown expected votes
> 1 Resources configured.
> ============
> 
> Online: [ node2 node1 ]
> 
> XENVM (ocf::heartbeat:Xen):   Started node2
> 
> r...@node2:/var/lib/heartbeat/crm# xm list
> Name                                        ID   Mem VCPUs      State   
> Time(s)
> Domain-0                                     0  3729     2     r-----    125.4
> r...@node2:/var/lib/heartbeat/crm# crm_resource --resource XENVM --locate
> resource XENVM is running on: node2
> 
> 
> 
> kind regards,
> 
> 
> _Terry
> 
> 
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to