My apologies for being unclear on that - I'm using the corosync 1.4.1
rpm provided by CentOS/RHEL 6.4.
I'll try using the member objects within the interface block to see if
that has my setup behave any better. Thanks!
On Wed, May 22, 2013 at 05:12:43PM +0200, Jan Friesse babbled thus:
> Actually,
> I've reviewed that config file again and it looks like you are using
> corosync 1.x. There nodelist is really not supported, and supported is
> member object inside of interface (see corosync.conf.example.udpu). For
> corosync 2.x, member object inside interface object works also, but it's
> internally converted to recommended version with nodelist (so that's
> what you've sent).
>
> Regards,
> Honza
>
> Mike Edwards napsal(a):
> > Yep. The config I pasted has the bindnetaddr set to 10.10.23.50, which
> > also happens to be defined as node 1.
> >
> >
> > On Wed, May 22, 2013 at 09:28:13AM +0200, Jan Friesse babbled thus:
> >> Mike,
> >> did you entered local node in nodelist? Because this may explain
> >> behavior you were describing.
> >>
> >> Honza
> >
--
Mike Edwards | If this email address disappears,
Unsolicited advertisments to | assume it was spammed to death. To
this address are not welcome. | reach me in that case, s/-.*@/@/
"Our progress as a nation can be no swifter than our progress in education.
The human mind is our fundamental resource."
-- John F. Kennedy
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
