[Pacemaker] A problem to fail in a stop of Pacemaker.

renayama19661014 at ybb.ne.jp renayama19661014 at ybb.ne.jp
Wed Sep 30 00:51:11 UTC 2009


Hi Remi,

> It appears that this is a similar problem to the one that I reported, 
> yes.  It appears to not be a bug in Corosync, but rather one in 
> Pacemaker.  This bug has been filed in Red Hat Bugzilla, see it at:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=525589
> 
> Perhaps you could add any additional details that you have found 
> (affected packages, etc.) to the bug; it may help the developers fix it.

All right.
Thank you.

Best Regards,
Hideo Yamauchi.

--- Remi Broemeling <remi at nexopia.com> wrote:

> Hello Hideo,
> 
> It appears that this is a similar problem to the one that I reported, 
> yes.  It appears to not be a bug in Corosync, but rather one in 
> Pacemaker.  This bug has been filed in Red Hat Bugzilla, see it at:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=525589
> 
> Perhaps you could add any additional details that you have found 
> (affected packages, etc.) to the bug; it may help the developers fix it.
> 
> Thanks.
> 
> 
> renayama19661014 at ybb.ne.jp wrote:
> > Hi,
> >
> > I started a Dummy resource in one node by the next combination.
> >  * corosync 1.1.0
> >  * Pacemaker-1-0-05c8b63cbca7
> >  * Reusable-Cluster-Components-6ef02517ee57
> >  * Cluster-Resource-Agents-88a9cfd9e8b5
> >
> > The Dummy resource started in a node.
> >
> > I was going to stop a node(service Corosync stop), but did not stop.
> >
> > --------------log----------
> > (snip)
> >
> > Sep 29 13:52:01 rh53-1 crmd: [11193]: info: crm_signal_dispatch: Invoking handler for signal
> 15:
> > Terminated
> > Sep 29 13:52:01 rh53-1 crmd: [11193]: info: crm_shutdown: Requesting shutdown
> > Sep 29 13:52:01 rh53-1 crmd: [11193]: info: do_state_transition: State transition S_IDLE ->
> > S_POLICY_ENGINE [ input=I_SHUTDOWN cause=C_SHUTDOWN origin=crm_shutdown ]
> > Sep 29 13:52:01 rh53-1 crmd: [11193]: info: do_state_transition: All 1 cluster nodes are
> eligible to
> > run resources.
> > Sep 29 13:52:01 rh53-1 crmd: [11193]: info: do_shutdown_req: Sending shutdown request to DC:
> rh53-1
> > Sep 29 13:52:30 rh53-1 corosync[11183]:   [pcmk  ] notice: pcmk_shutdown: Still waiting for
> crmd
> > (pid=11193) to terminate...
> > Sep 29 13:53:30 rh53-1 last message repeated 2 times
> > Sep 29 13:55:00 rh53-1 last message repeated 3 times
> > Sep 29 13:56:30 rh53-1 last message repeated 3 times
> > Sep 29 13:58:01 rh53-1 last message repeated 3 times
> > Sep 29 13:59:31 rh53-1 last message repeated 3 times
> > Sep 29 14:00:31 rh53-1 last message repeated 2 times
> > Sep 29 14:00:46 rh53-1 cib: [11189]: info: cib_stats: Processed 94 operations (11489.00us
> average, 0%
> > utilization) in the last 10min
> > Sep 29 14:01:01 rh53-1 corosync[11183]:   [pcmk  ] notice: pcmk_shutdown: Still waiting for
> crmd
> > (pid=11193) to terminate.......
> >
> > (snip)
> > --------------log----------
> >
> >
> > Possibly is the cause same as the next email?
> >  * http://www.gossamer-threads.com/lists/linuxha/pacemaker/58127
> >
> > And, the same problem was taking place by the next combination.
> >  * corosync 1.0.1
> >  * Pacemaker-1-0-595cca870aff
> >  * Reusable-Cluster-Components-6ef02517ee57
> >  * Cluster-Resource-Agents-88a9cfd9e8b5
> >
> > I attach a file of hb_report.
> >
> > Best Regards,
> > Hideo Yamauchi.
> >   
> 
> -- 
> 
> Remi Broemeling
> Sr System Administrator
> 
> Nexopia.com Inc.
> direct: 780 444 1250 ext 435
> email: remi at nexopia.com <mailto:remi at nexopia.com>
> fax: 780 487 0376
> 
> www.nexopia.com <http://www.nexopia.com>
> 
> You are only young once, but you can stay immature indefinitely.
> www.siglets.com
> > _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 





More information about the Pacemaker mailing list