[Pacemaker] [GUI][PATCH]An orphan resource was displayed by GUI.

renayama19661014 at ybb.ne.jp renayama19661014 at ybb.ne.jp
Fri Mar 5 00:36:55 UTC 2010 

Hi Yan,

A problem seems to occur after having applied your patch somehow or other.

However, in my environment, the problem does not reappear.

I send hard copy of log and GUI which occurred in our user.

After all the resources that are ORPHANED seem to increase when I watch log.

ha-log.cgl60(2525): Mar  2 19:48:28 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:0 on cgl62 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(2526): Mar  2 19:48:28 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:0 on cgl62 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(2749): Mar  2 19:48:32 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:0 on cgl62 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(2750): Mar  2 19:48:32 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:0 on cgl62 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(3079): Mar  2 19:49:18 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:1 on cgl60 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(3080): Mar  2 19:49:18 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:1 on cgl60 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(3083): Mar  2 19:49:18 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:0 on cgl62 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(3084): Mar  2 19:49:18 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:0 on cgl62 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(3303): Mar  2 19:49:22 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:1 on cgl60 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(3304): Mar  2 19:49:22 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:1 on cgl60 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(3307): Mar  2 19:49:22 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:0 on cgl62 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(3308): Mar  2 19:49:22 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:0 on cgl62 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(3577): Mar  2 19:50:07 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:1 on cgl60 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(3578): Mar  2 19:50:07 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:1 on cgl60 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(3582): Mar  2 19:50:07 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:0 on cgl62 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(3583): Mar  2 19:50:07 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:0 on cgl62 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(3801): Mar  2 19:50:12 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:1 on cgl60 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(3802): Mar  2 19:50:12 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:1 on cgl60 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(3805): Mar  2 19:50:12 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:0 on cgl62 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(3806): Mar  2 19:50:12 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:0 on cgl62 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(4219): Mar  2 19:51:22 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:1 on cgl60 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(4221): Mar  2 19:51:22 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:1 on cgl60 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(4224): Mar  2 19:51:22 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:0 on cgl62 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(4225): Mar  2 19:51:22 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:0 on cgl62 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(4454): Mar  2 19:51:26 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:1 on cgl60 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(4455): Mar  2 19:51:26 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:1 on cgl60 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(4457): Mar  2 19:51:26 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:0 on cgl62 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(4458): Mar  2 19:51:26 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:0 on cgl62 to clnUMdummy02:2 (ORPHAN)
ha-log.cgl60(4790): Mar  2 19:52:41 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:1 on cgl63 to clnUMdummy01:2 (ORPHAN)
ha-log.cgl60(4791): Mar  2 19:52:41 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:1 on cgl63 to clnUMdummy02:3 (ORPHAN)
ha-log.cgl60(4793): Mar  2 19:52:41 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy01:0 on cgl60 to clnUMdummy01:4 (ORPHAN)
ha-log.cgl60(4794): Mar  2 19:52:41 cgl60 pengine: [5981]: info: find_clone: Internally renamed
clnUMdummy02:0 on cgl60 to clnUMdummy02:5 (ORPHAN)


I think that GUI displays the resource that is this ORPHANED.

Best Regards,
Hideo Yamauchi.



--- renayama19661014 at ybb.ne.jp wrote:

> Hi Yan,
> 
> Thank you for a reply.
> 
> Probability of the reproduction of the problem is not high in my environment, but tries your
> patch for
> the moment. 
> I e-mail a result to you.
> 
> Best Regards,
> Hideo Yamauchi.
> 
> 
> --- Yan Gao <ygao at novell.com> wrote:
> 
> > Hi Hideo,
> > 
> > On 02/08/10 15:35, renayama19661014 at ybb.ne.jp wrote:
> > > Hi Yan,
> > > Hi Andrew,
> > > 
> > > The phenomenon of the problem does not reappear.
> > > I considerably try it, but do not readily reappear.
> > > 
> > > But, I found the interesting output from the log that the problem happened.
> > > 
> > > When a problem happened, GUI became the following display.
> > > 
> > > ----------------------------------------------------------
> > > clnUMgroup01　　　　
> > > 　clnUmResource:0 　
> > > 　　clnUMdummy01:0　on ['cgl60']　　ocf::heartbeat:Dummy
> > > 　　clnUMdummy02:0　on ['cgl60']　　ocf::heartbeat:Dummy
> > > 　clnUmResource:1　 
> > > 　　clnUMdummy01:1　on ['cgl63']　　ocf::heartbeat:Dummy
> > > 　　clmUMdummy02:1　on ['cgl63']　　ocf::heartbeat:Dummy
> > > 　clnUmResource:2　 
> > > 　　clnUMdummy01:2　not running (orphaned)
> > > 　　clnUMdummy02:2　not running (orphaned)
> > > ----------------------------------------------------------
> > > 
> > > Log has the output that pengine changes the name of the resource. 
> > > And the name is the resource name that is ORPHANED displayed in GUI.
> > > 
> > > ----------------------------------------------------------
> > > (snip)
> > > Jan 29 15:39:29 cgl60 pengine: [4338]: info: unpack_config: Node scores: 'red' = -INFINITY,
> > 'yellow' =
> > > 0, 'green' = 0
> > > Jan 29 15:39:29 cgl60 pengine: [4338]: WARN: unpack_nodes: Blind faith: not fencing unseen
> > nodes
> > > Jan 29 15:39:29 cgl60 pengine: [4338]: info: determine_online_status: Node cgl60 is online
> > > Jan 29 15:39:29 cgl60 pengine: [4338]: info: determine_online_status: Node cgl63 is online
> > > Jan 29 15:39:29 cgl60 pengine: [4338]: info: determine_online_status: Node cgl61 is online
> > > Jan 29 15:39:29 cgl60 pengine: [4338]: info: find_clone: Internally renamed clnUMdummy01:0
> on
> > cgl61 to
> > > clnUMdummy01:2 (ORPHAN)
> > > Jan 29 15:39:29 cgl60 pengine: [4338]: info: find_clone: Internally renamed clnUMdummy02:0
> on
> > cgl61 to
> > > clnUMdummy02:2 (ORPHAN)
> > > Jan 29 15:39:29 cgl60 pengine: [4338]: info: determine_online_status: Node cgl62 is online
> > > Jan 29 15:39:29 cgl60 pengine: [4338]: info: find_clone: Internally renamed clnUMdummy01:0
> on
> > cgl62 to
> > > clnUMdummy01:2 (ORPHAN)
> > > Jan 29 15:39:29 cgl60 pengine: [4338]: info: find_clone: Internally renamed clnUMdummy02:0
> on
> > cgl62 to
> > > clnUMdummy02:2 (ORPHAN)
> > > (snip)
> > > ----------------------------------------------------------
> > > 
> > > 
> > > Is there any probable cause?
> > > I thought that the problem did not happen with this patch.
> > > 
> > > I confirm that a problem appears again.
> > 
> > If you can reproduce the problem,  please try  the following:
> > 
> > --- a/mgmt/daemon/mgmt_crm.c    Tue Feb 02 17:40:36 2010 +0800
> > +++ b/mgmt/daemon/mgmt_crm.c    Tue Feb 23 18:54:54 2010 +0800
> > @@ -1475,7 +1475,7 @@
> >         ret = strdup(MSG_OK);
> >         while (cur != NULL) {
> >                 resource_t* rsc = (resource_t*)cur->data;
> > -               gboolean is_active = rsc->fns->active(rsc, FALSE);
> > +               gboolean is_active = rsc->fns->active(rsc, TRUE);
> >                 if (is_not_set(rsc->flags, pe_rsc_orphan) || is_active) {
> >                         ret = mgmt_msg_append(ret, rsc->id);
> >                 }
> > 
> > Regards,
> >   Yan
> > -- 
> > Yan Gao <ygao at novell.com>
> > Software Engineer
> > China Server Team, OPS Engineering, Novell, Inc.
> > 
> > _______________________________________________
> > Pacemaker mailing list
> > Pacemaker at oss.clusterlabs.org
> > http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> > 
> 
> 
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ha-log.zip
Type: application/x-zip-compressed
Size: 71174 bytes
Desc: 982958424-ha-log.zip
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100305/4ea4e408/attachment-0006.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: GUI-ORPHANED.zip
Type: application/x-zip-compressed
Size: 69362 bytes
Desc: 3365222045-GUI-ORPHANED.zip
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100305/4ea4e408/attachment-0007.bin>

More information about the Pacemaker mailing list