[Openais] corosync ring marked FAULTY - administrative intervention required

Christine Caulfield ccaulfie at redhat.com
Fri Apr 9 08:16:14 PDT 2010


On 09/04/10 12:45, Vadym Chepkov wrote:
> Hi,
>
> I experience this issue  on every cluster I have, not just this one, so it could be a common misconfiguration on my part.
> I am using the latest version of the corosync:
>
> corosync-1.2.1-1.el5
>
> Here is my config:
>
> compatibility: none
>
> aisexec {
>          user:   root
>          group:  root
> }
>
> service {
>          name: pacemaker
>          ver:  0
> }
>
> totem {
>          version: 2
>          token: 5000
>          token_retransmits_before_loss_const: 20
>          join: 1000
>          consensus: 7500
>          vsftype: none
>          max_messages: 20
>          secauth: off
>          threads: 0
>          clear_node_high_bit: yes
>          rrp_mode: passive
>          interface {
>                  ringnumber: 0
>                  broadcast: yes
>                  bindnetaddr: 10.0.0.0
>                  mcastport: 5405
>          }
>          interface {
>                  ringnumber: 1
>                  broadcast: yes
>                  bindnetaddr: 207.207.163.0
>                  mcastport: 5406
>          }
> }

try choosing a different port number for ring 1. corosync uses port 
numbers <n> and <n-1> so it could be interfering with ring 0.

chrissie



More information about the Openais mailing list