https://bugzilla.novell.com/show_bug.cgi?id=725773 https://bugzilla.novell.com/show_bug.cgi?id=725773#c0 Summary: cluster corosync + pacemaker without heartbeat fails to start Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: marco@nucleus.it QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=458218) --> (http://bugzilla.novell.com/attachment.cgi?id=458218) Corosync config User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1 Opensuse 11.4 corosync-1.3.0-3.1.x86_64 pacemaker-1.1.5-3.2.x86_64 I'm preparing a new cluster env ( corosync + pacemaker (crmd,cib etc) , no heartbeat ), so in the first host i start the daemons and i'm expecting cib creates a new cib.xml. I tried with a prepared cib.xml in /var/lib/heartbeat/crm/cib.xml but the symptom is the same. Every time i start corosync ( rcopenais start ) crmd starts but fails to comunicate with this socket /var/run/crm/cib_rw and /var/run/crm/cib_callback . I try to start only the cib bin and it fails with this message: CRIT: get_cluster_type: This installation of Pacemaker does not support the '(null)' cluster infrastructure. Terminating. exit status: 100 So the cluster node is not starting the first time. In the attachment the corosync.conf I don't have others config in /etc/corosync/ dir /etc/corosync/ /etc/corosync/corosync.conf.example.udpu /etc/corosync/service.d /etc/corosync/uidgid.d /etc/corosync/amf.conf.example /etc/corosync/corosync.conf.example /etc/corosync/authkey /etc/corosync/corosync.conf With opensuse 11.1 all is fine with the same procedure. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.