> Thats /really/ weird. > Corosync calculates the nodeid from the IP it bound to, a > conflict would seem to imply both nodes have the same address. > > Perhaps assign a nodeid manually? >
Don't I feel very special. :-) I can assign manual node ids if necessary, but I'd always wonder what other weirdness may ensue later. I think it would be better for me to understand what's going wrong here. Please see my follow-up email that I sent this morning with the full logs and output from corosync-objctl, which (to my untrained eye) seems to indicate that node ids are being calculated correctly. --Eric Disclaimer - November 12, 2012 This email and any files transmitted with it are confidential and intended solely for General Linux-HA mailing list. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
