Hi Andrew, > Odd. You might want to report this to the openais guys. All right.
> The problem goes away when you just downgrade pacemaker to 1.0.6 (and > leave corosync at the same version)? Sorry... It was my mistake. When I put corosync1.2.0 and Pacemaker1.0.6 together, the same problem occurred. > > Do not you hear any similar phenomenon? > > Nope, first I've heard of it. Thank you. Best Regards, Hideo Yamauchi. --- Andrew Beekhof <and...@beekhof.net> wrote: > On Fri, Feb 5, 2010 at 4:41 AM, <renayama19661...@ybb.ne.jp> wrote: > > Hi Andrew, > > > > The problem does not occur at single ring. > > Odd. You might want to report this to the openais guys. > > > It is strange that this problem does not happen in Pacemaker1.0.6. > > The problem goes away when you just downgrade pacemaker to 1.0.6 (and > leave corosync at the same version)? > > > > > Will this be a problem of corosync? > > Almost certainly > > > Do not you hear any similar phenomenon? > > Nope, first I've heard of it. > > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
