On Fri, Dec 21, 2012 at 10:48 AM, Michael Papet <mpa...@yahoo.com> wrote: > I may be doing the impossible trying to get a pacemaker+corosync cluster to > work on Centos 5.8 building from source.
Any particular reason not to use pre-built packages? http://clusterlabs.org/rpm-next/ > I have some system constraints I > cannot ignore. > > Corosync finds the nodes just fine. (kslinux1, kslinux2) SELinux and the > firewall is turned off. > Pacemakerd starts just fine on kslinux1. kslinux2 seems to be the problem. > > Starting pacemakerd -f -V on kslinux2 returns > > Could not establish pacemakerd connection: Connection refused (111) > info: crm_ipc_connect: Could not establish pacemakerd connection: > Connection refused (111) > info: get_cluster_type: Detected an active 'corosync' cluster > info: read_config: Reading configure for stack: corosync > notice: crm_add_logfile: Additional logging available in > /var/log/cluster/corosync.log > info: read_config: User configured file based logging and explicitly > disabled syslog. > notice: main: Starting Pacemaker 1.1.8 (Build: 3035414): > generated-manpages agent-manpages ncurses libqb-logging libqb-ipc > lha-fencing upstart systemd corosync-native snmp > info: main: Maximum core file size is: 4294967295 > info: qb_ipcs_us_publish: server name: pacemakerd > notice: corosync_node_name: Unable to get node name for nodeid 0 > notice: get_local_node_name: Defaulting to uname(2).nodename for the > local corosync node name > notice: update_node_processes: 0x9415ea0 Node 2222 now known as > kslinux2, was: > notice: find_and_track_existing_processes: Tracking existing lrmd > process (pid=23794) > notice: find_and_track_existing_processes: Tracking existing cib > process (pid=24068) > notice: find_and_track_existing_processes: Tracking existing attrd > process (pid=24069) > info: start_child: Forked child 25857 for process stonith-ng > info: start_child: Forked child 25858 for process pengine > info: start_child: Forked child 25859 for process crmd > info: main: Starting mainloop > > And then this is in /var/log/cluster/corosync.log > > Dec 20 15:42:02 [27261] kslinux2 crmd: info: crm_ipc_connect: > Could not establish cib_shm connection: Connection refused (111) > Dec 20 15:42:02 [27261] kslinux2 crmd: info: do_cib_control: > Could not connect to the CIB service: Transport endpoint is not connected > Dec 20 15:42:02 [27261] kslinux2 crmd: warning: do_cib_control: > Couldn't complete CIB registration 16 times... pause and retry > Dec 20 15:42:04 [27261] kslinux2 crmd: info: crm_timer_popped: > Wait Timer (I_NULL) just popped (2000ms) > Dec 20 15:42:04 [27261] kslinux2 crmd: info: crm_ipc_connect: > Could not establish cib_shm connection: Connection refused (111) > Dec 20 15:42:05 [27261] kslinux2 crmd: info: crm_ipc_connect: > Could not establish cib_shm connection: Connection refused (111) > Dec 20 15:42:05 [27261] kslinux2 crmd: info: do_cib_control: > Could not connect to the CIB service: Transport endpoint is not connected > Dec 20 15:42:05 [27261] kslinux2 crmd: warning: do_cib_control: > Couldn't complete CIB registration 17 times... pause and retry > Dec 20 15:42:07 [27261] kslinux2 crmd: info: crm_timer_popped: > Wait Timer (I_NULL) just popped (2000ms) > Dec 20 15:42:07 [27261] kslinux2 crmd: info: crm_ipc_connect: > Could not establish cib_shm connection: Connection refused (111) > Dec 20 15:42:08 [27261] kslinux2 crmd: info: crm_ipc_connect: > Could not establish cib_shm connection: Connection refused (111) > Dec 20 15:42:08 [27261] kslinux2 crmd: info: do_cib_control: > Could not connect to the CIB service: Transport endpoint is not connected > Dec 20 15:42:08 [27261] kslinux2 crmd: warning: do_cib_control: > Couldn't complete CIB registration 18 times... pause and retry > Dec 20 15:42:10 [27261] kslinux2 crmd: info: crm_timer_popped: > Wait Timer (I_NULL) just popped (2000ms) > Dec 20 15:42:10 [27261] kslinux2 crmd: info: crm_ipc_connect: > Could not establish cib_shm connection: Connection refused (111) > Dec 20 15:42:11 [27261] kslinux2 crmd: info: crm_ipc_connect: > Could not establish cib_shm connection: Connection refused (111) > Dec 20 15:42:11 [27261] kslinux2 crmd: info: do_cib_control: > Could not connect to the CIB service: Transport endpoint is not connected > Dec 20 15:42:11 [27261] kslinux2 crmd: warning: do_cib_control: > Couldn't complete CIB registration 19 times... pause and retry > Dec 20 15:42:13 [27261] kslinux2 crmd: info: crm_timer_popped: > Wait Timer (I_NULL) just popped (2000ms) > Dec 20 15:42:13 [27261] kslinux2 crmd: info: crm_ipc_connect: > Could not establish cib_shm connection: Connection refused (111) > Dec 20 15:42:14 [27261] kslinux2 crmd: info: crm_ipc_connect: > Could not establish cib_shm connection: Connection refused (111) > Dec 20 15:42:14 [27261] kslinux2 crmd: info: do_cib_control: > Could not connect to the CIB service: Transport endpoint is not connected > Dec 20 15:42:14 [27261] kslinux2 crmd: warning: do_cib_control: > Couldn't complete CIB registration 20 times... pause and retry > Dec 20 15:42:16 [27261] kslinux2 crmd: info: crm_timer_popped: > Wait Timer (I_NULL) just popped (2000ms) > Dec 20 15:42:16 [27261] kslinux2 crmd: info: crm_ipc_connect: > Could not establish cib_shm connection: Connection refused (111) > Dec 20 15:42:17 [27261] kslinux2 crmd: info: crm_ipc_connect: > Could not establish cib_shm connection: Connection refused (111) > Dec 20 15:42:17 [27261] kslinux2 crmd: info: do_cib_control: > Could not connect to the CIB service: Transport endpoint is not connected > Dec 20 15:42:17 [27261] kslinux2 crmd: warning: do_cib_control: > Couldn't complete CIB registration 21 times... pause and retry > Dec 20 15:42:19 [27261] kslinux2 crmd: info: crm_timer_popped: > Wait Timer (I_NULL) just popped (2000ms) > Dec 20 15:42:19 [27261] kslinux2 crmd: info: crm_ipc_connect: > Could not establish cib_shm connection: Connection refused (111) > > Any clue? Or, should I just do a heartbeat/pacemaker cluster and be done? > > Michael > > > > > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
