I just installed and configured corosync-1.2.3-21.el6_0.1.x86_64 on
RHEL6. At startup, the corosync log appears to be complete except for
the line, " A processor joined or left the membership and a new
membership was formed." I cannot connect to the cluster, and
corosync-cfgtool states:
 
Local node ID 923445440
Could not get the ring status, the error is: 6

There is precious little about this on Google. Any ideas? I verified
nothing else was on that mcast group and port, adn iptables is off.
 
Here is my full corosync config and startup log.
 
# Please read the corosync.conf.5 manual page
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: passive
        # nodeid:         1234
 
        interface {
                ringnumber: 0
                bindnetaddr: 192.168.10.0
                mcastaddr: 226.94.2.1
                mcastport: 4002
        }
 
#       interface {
#               ringnumber: 1
#               bindnetaddr: 198.51.100.0
#               mcastaddr: 226.94.2.2
#               mcastport: 4004
#       }
 
}
 
logging {
        fileline: off
        to_stderr: yes
        to_logfile: yes
        to_syslog: no
        logfile: /var/log/corosync.log
        debug: off
        timestamp: on
        logger_subsys {
                subsys: AMF
                debug: off
        }
}
 
amf {
        mode: disabled
}

 
 
Oct 30 16:39:02 corosync [MAIN  ] Corosync Cluster Engine ('1.2.3'):
started and ready to provide service.
Oct 30 16:39:02 corosync [MAIN  ] Corosync built-in features: nss rdma
Oct 30 16:39:02 corosync [MAIN  ] Successfully read main configuration
file '/etc/corosync/corosync.conf'.
Oct 30 16:39:02 corosync [TOTEM ] Initializing transport (UDP/IP).
Oct 30 16:39:02 corosync [TOTEM ] Initializing transmit/receive
security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
Oct 30 16:39:02 corosync [TOTEM ] Could not set traffic priority.
(Socket operation on non-socket)
Oct 30 16:39:02 corosync [TOTEM ] The network interface [192.168.10.55]
is now up.
Set r/w permissions for uid=0, gid=0 on /var/log/corosync.log
Oct 30 16:39:02 corosync [pcmk  ] info: process_ais_conf: Reading
configure
Oct 30 16:39:02 corosync [pcmk  ] info: config_find_init: Local handle:
4835695805891346434 for logging
Oct 30 16:39:02 corosync [pcmk  ] info: config_find_next: Processing
additional logging options...
Oct 30 16:39:02 corosync [pcmk  ] info: get_config_opt: Found 'off' for
option: debug
Oct 30 16:39:02 corosync [pcmk  ] info: get_config_opt: Found 'yes' for
option: to_logfile
Oct 30 16:39:02 corosync [pcmk  ] info: get_config_opt: Found
'/var/log/corosync.log' for option: logfile
Oct 30 16:39:02 corosync [pcmk  ] info: get_config_opt: Found 'no' for
option: to_syslog
Oct 30 16:39:02 corosync [pcmk  ] info: process_ais_conf: User
configured file based logging and explicitly disabled syslog.
Oct 30 16:39:02 corosync [pcmk  ] info: config_find_init: Local handle:
4552499517957603331 for quorum
Oct 30 16:39:02 corosync [pcmk  ] info: config_find_next: No additional
configuration supplied for: quorum
Oct 30 16:39:02 corosync [pcmk  ] info: get_config_opt: No default for
option: provider
Oct 30 16:39:02 corosync [pcmk  ] info: config_find_init: Local handle:
8972265949260414980 for service
Oct 30 16:39:02 corosync [pcmk  ] info: config_find_next: Processing
additional service options...
Oct 30 16:39:02 corosync [pcmk  ] info: get_config_opt: Found '1' for
option: ver
Oct 30 16:39:02 corosync [pcmk  ] info: process_ais_conf: Enabling MCP
mode: Use the Pacemaker init script to complete Pacemaker startup
Oct 30 16:39:02 corosync [pcmk  ] info: get_config_opt: Defaulting to
'pcmk' for option: clustername
Oct 30 16:39:02 corosync [pcmk  ] info: get_config_opt: Defaulting to
'no' for option: use_logd
Oct 30 16:39:02 corosync [pcmk  ] info: get_config_opt: Defaulting to
'no' for option: use_mgmtd
Oct 30 16:39:02 corosync [pcmk  ] info: pcmk_startup: CRM: Initialized
Oct 30 16:39:02 corosync [pcmk  ] Logging: Initialized pcmk_startup
Oct 30 16:39:02 corosync [pcmk  ] info: pcmk_startup: Maximum core file
size is: 18446744073709551615
Oct 30 16:39:02 corosync [pcmk  ] info: pcmk_startup: Service: 10
Oct 30 16:39:02 corosync [pcmk  ] info: pcmk_startup: Local hostname:
ha08a.mycharts.md
Oct 30 16:39:02 corosync [pcmk  ] info: pcmk_update_nodeid: Local node
id: 923445440
Oct 30 16:39:02 corosync [pcmk  ] info: update_member: Creating entry
for node 923445440 born on 0
Oct 30 16:39:02 corosync [pcmk  ] info: update_member: 0xf42ce0 Node
923445440 now known as ha08a.mycharts.md (was: (null))
Oct 30 16:39:02 corosync [pcmk  ] info: update_member: Node
ha08a.mycharts.md now has 1 quorum votes (was 0)
Oct 30 16:39:02 corosync [pcmk  ] info: update_member: Node
923445440/ha08a.mycharts.md is now: member
Oct 30 16:39:02 corosync [SERV  ] Service engine loaded: Pacemaker
Cluster Manager 1.1.2
Oct 30 16:39:02 corosync [SERV  ] Service engine loaded: corosync
extended virtual synchrony service
Oct 30 16:39:02 corosync [SERV  ] Service engine loaded: corosync
configuration service
Oct 30 16:39:02 corosync [SERV  ] Service engine loaded: corosync
cluster closed process group service v1.01
Oct 30 16:39:02 corosync [SERV  ] Service engine loaded: corosync
cluster config database access v1.01
Oct 30 16:39:02 corosync [SERV  ] Service engine loaded: corosync
profile loading service
Oct 30 16:39:02 corosync [SERV  ] Service engine loaded: corosync
cluster quorum service v0.1
Oct 30 16:39:02 corosync [MAIN  ] Compatibility mode set to whitetank.
Using V1 and V2 of the synchronization engine.

 
 
 
 
--
Eric Robinson


Disclaimer - October 30, 2011 
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
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to