On Mon, Nov 12, 2012 at 3:52 PM, Robinson, Eric <[email protected]> wrote:
> Andrew,
>
>>
>> Um, are you setting a nodeid in corosync.conf?
>>
>> Because I see this:
>>
>> Nov 09 09:07:25 [2609] ha09a.mycharts.md crmd: crit:
>> crm_get_peer: Node ha09a.mycharts.md and ha09a share
>> the same cluster
>> node id '973777088'!
>>
>> Which could easily explain why the cluster is massively confused.
>>
>
> I am not setting a node id in corosync.conf. Here is the corosync.conf file
> (same on both nodes)...
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?
>
> compatibility: whitetank
>
> totem {
>
> version: 2
> token: 5000
> token_retransmits_before_loss_const: 10
> join: 1000
> consensus: 7500
> vsftype: none
> max_messages: 20
> secauth: off
> threads: 0
> clear_node_high_bit: yes
> rrp_mode: active
>
> interface {
> ringnumber: 0
> bindnetaddr: 192.168.10.0
> mcastaddr: 239.255.4.1
> mcastport: 4000
> ttl: 1
> }
>
> interface {
> ringnumber: 1
> bindnetaddr: 198.51.100.0
> mcastaddr: 239.255.4.2
> mcastport: 4000
> ttl: 1
> }
> }
>
> logging {
> fileline: off
> to_stderr: yes
> to_logfile: yes
> to_syslog: yes
> logfile: /var/log/corosync.log
> debug: on
> timestamp: on
> logger_subsys {
> subsys: AMF
> debug: off
> }
> }
>
> amf {
> mode: disabled
> }
>
> I will get you the logs from ha09b soon...
>
>
> --Eric
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Disclaimer - November 11, 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
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
