Re: [Pacemaker] [corosync] Unable to join cluster from a newly-installed centos 6.2 node
On 03/02/2012 05:29 PM, Diego Lima wrote:
> Hello,
>
> I've recently installed Corosync on two CentOS 6.2 machines. One is
> working fine but on the other machine I've been unable to connect to
> the cluster. On the logs I can see this whenever I start
> corosync+pacemaker:
>
> Mar 2 21:33:16 no2 corosync[15924]: [MAIN ] Corosync Cluster
> Engine ('1.4.1'): started and ready to provide service.
> Mar 2 21:33:16 no2 corosync[15924]: [MAIN ] Corosync built-in
> features: nss dbus rdma snmp
> Mar 2 21:33:16 no2 corosync[15924]: [MAIN ] Successfully read main
> configuration file '/etc/corosync/corosync.conf'.
> Mar 2 21:33:16 no2 corosync[15924]: [TOTEM ] Initializing transport
> (UDP/IP Multicast).
> Mar 2 21:33:16 no2 corosync[15924]: [TOTEM ] Initializing
> transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> Mar 2 21:33:16 no2 corosync[15924]: [TOTEM ] The network interface
> [172.16.100.2] is now up.
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
> process_ais_conf: Reading configure
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
> config_find_init: Local handle: 4730966301143465987 for logging
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
> config_find_next: Processing additional logging options...
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
> Found 'off' for option: debug
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
> Found 'no' for option: to_logfile
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
> Found 'yes' for option: to_syslog
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
> Found 'daemon' for option: syslog_facility
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
> config_find_init: Local handle: 7739444317642555396 for quorum
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
> config_find_next: No additional configuration supplied for: quorum
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
> No default for option: provider
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
> config_find_init: Local handle: 5650605097994944517 for service
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
> config_find_next: Processing additional service options...
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
> Found '0' for option: ver
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
> Defaulting to 'pcmk' for option: clustername
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
> Defaulting to 'no' for option: use_logd
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
> Defaulting to 'no' for option: use_mgmtd
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: pcmk_startup:
> CRM: Initialized
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] Logging: Initialized
> pcmk_startup
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: pcmk_startup:
> Maximum core file size is: 18446744073709551615
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: pcmk_startup: Service:
> 10
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: pcmk_startup:
> Local hostname: no2.informidia.int
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
> pcmk_update_nodeid: Local node id: 40112300
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: update_member:
> Creating entry for node 40112300 born on 0
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: update_member:
> 0x766520 Node 40112300 now known as no2.informidia.int (was: (null))
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: update_member:
> Node no2.informidia.int now has 1 quorum votes (was 0)
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: update_member:
> Node 40112300/no2.informidia.int is now: member
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: spawn_child:
> Forked child 15930 for process stonith-ng
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: spawn_child:
> Forked child 15931 for process cib
> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: spawn_child:
> Forked child 15932 for process lrmd
> Mar 2 21:33:16 no2 lrmd: [15932]: info: G_main_add_SignalHandler:
> Added signal handler for signal 15
> Mar 2 21:33:16 no2 stonith-ng: [15930]: info: Invoked:
> /usr/lib64/heartbeat/stonithd
> Mar 2 21:33:16 no2 stonith-ng: [15930]: info: crm_log_init_worker:
> Changed active directory to /var/lib/heartbeat/cores/root
> Mar 2 21:33:16 no2 stonith-ng: [15930]: info:
> G_main_add_SignalHandler: Added signal handler for signal 17
> Mar 2 21:33:16 no2 stonith-ng: [15930]: info: get_cluster_type:
> Cluster type is: 'openais'
> Mar 2 21:33:16 no2 stonith-ng: [15930]: notice: crm_cluster_connect:
> Connecting to cluster infrastructure: classic openais (with plugin)
> Mar 2 21:33:16 no2 stonith-ng: [15930]: info:
> init_ais_connection_classic: Creating connection to our Corosync
> plugin
> Mar 2 21:
Re: [Pacemaker] [corosync] Unable to join cluster from a newly-installed centos 6.2 node
On Sat, Mar 3, 2012 at 2:53 PM, Steven Dake wrote:
> On 03/02/2012 05:29 PM, Diego Lima wrote:
>> Hello,
>>
>> I've recently installed Corosync on two CentOS 6.2 machines. One is
>> working fine but on the other machine I've been unable to connect to
>> the cluster. On the logs I can see this whenever I start
>> corosync+pacemaker:
>>
>> Mar 2 21:33:16 no2 corosync[15924]: [MAIN ] Corosync Cluster
>> Engine ('1.4.1'): started and ready to provide service.
>> Mar 2 21:33:16 no2 corosync[15924]: [MAIN ] Corosync built-in
>> features: nss dbus rdma snmp
>> Mar 2 21:33:16 no2 corosync[15924]: [MAIN ] Successfully read main
>> configuration file '/etc/corosync/corosync.conf'.
>> Mar 2 21:33:16 no2 corosync[15924]: [TOTEM ] Initializing transport
>> (UDP/IP Multicast).
>> Mar 2 21:33:16 no2 corosync[15924]: [TOTEM ] Initializing
>> transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
>> Mar 2 21:33:16 no2 corosync[15924]: [TOTEM ] The network interface
>> [172.16.100.2] is now up.
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
>> process_ais_conf: Reading configure
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
>> config_find_init: Local handle: 4730966301143465987 for logging
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
>> config_find_next: Processing additional logging options...
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
>> Found 'off' for option: debug
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
>> Found 'no' for option: to_logfile
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
>> Found 'yes' for option: to_syslog
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
>> Found 'daemon' for option: syslog_facility
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
>> config_find_init: Local handle: 7739444317642555396 for quorum
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
>> config_find_next: No additional configuration supplied for: quorum
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
>> No default for option: provider
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
>> config_find_init: Local handle: 5650605097994944517 for service
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
>> config_find_next: Processing additional service options...
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
>> Found '0' for option: ver
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
>> Defaulting to 'pcmk' for option: clustername
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
>> Defaulting to 'no' for option: use_logd
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: get_config_opt:
>> Defaulting to 'no' for option: use_mgmtd
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: pcmk_startup:
>> CRM: Initialized
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] Logging: Initialized
>> pcmk_startup
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: pcmk_startup:
>> Maximum core file size is: 18446744073709551615
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: pcmk_startup: Service:
>> 10
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: pcmk_startup:
>> Local hostname: no2.informidia.int
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info:
>> pcmk_update_nodeid: Local node id: 40112300
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: update_member:
>> Creating entry for node 40112300 born on 0
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: update_member:
>> 0x766520 Node 40112300 now known as no2.informidia.int (was: (null))
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: update_member:
>> Node no2.informidia.int now has 1 quorum votes (was 0)
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: update_member:
>> Node 40112300/no2.informidia.int is now: member
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: spawn_child:
>> Forked child 15930 for process stonith-ng
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: spawn_child:
>> Forked child 15931 for process cib
>> Mar 2 21:33:16 no2 corosync[15924]: [pcmk ] info: spawn_child:
>> Forked child 15932 for process lrmd
>> Mar 2 21:33:16 no2 lrmd: [15932]: info: G_main_add_SignalHandler:
>> Added signal handler for signal 15
>> Mar 2 21:33:16 no2 stonith-ng: [15930]: info: Invoked:
>> /usr/lib64/heartbeat/stonithd
>> Mar 2 21:33:16 no2 stonith-ng: [15930]: info: crm_log_init_worker:
>> Changed active directory to /var/lib/heartbeat/cores/root
>> Mar 2 21:33:16 no2 stonith-ng: [15930]: info:
>> G_main_add_SignalHandler: Added signal handler for signal 17
>> Mar 2 21:33:16 no2 stonith-ng: [15930]: info: get_cluster_type:
>> Cluster type is: 'openais'
>> Mar 2 21:33:16 no2 stonith-ng: [15930]: notice: crm_cluster_connect:
>> Connecting to cluster infrastructure: classic openais (with plug
