[Pacemaker] corosync/openais fails to start

Diego Remolina diego.remolina at physics.gatech.edu
Thu May 27 15:49:12 UTC 2010


Ok,

So for now the fix seems to be to remove the latest version of corosync:

1.2.2-1.1 and install the older rpms 1.2.1-1

Here is what I did:

[root at phys-ha01 corosync]# rpm -e --nodeps corosynclib corosync
[root at phys-ha01 corosync]# rpm -ivh 
http://www.clusterlabs.org/rpm/epel-5/x86_64/corosync-1.2.1-1.el5.x86_64.rpm 
http://www.clusterlabs.org/rpm/epel-5/x86_64/corosynclib-1.2.1-1.el5.x86_64.rpm

[root at phys-ha01 corosync]# /etc/init.d/corosync start
Starting Corosync Cluster Engine (corosync):               [  OK  ]
[root at phys-ha01 corosync]# crm status
============
Last updated: Thu May 27 11:46:53 2010
Stack: openais
Current DC: NONE
2 Nodes configured, 2 expected votes
3 Resources configured.
============

OFFLINE: [ phys-ha02.physics.gatech.edu phys-ha01.physics.gatech.edu ]

Diego

Steven Dake wrote:
> This is a known issue on some platforms, although the exact cause is 
> unknown.  I have tried RHEL 5.5 as well as CentOS 5.5 with clusterrepo 
> rpms and been unable to reproduce.  I'll keep looking.
> 
> Regards
> -steve
> 
> On 05/27/2010 06:07 AM, Diego Remolina wrote:
>> Hi,
>>
>> I was running the old rpms from the opensuse repo and wanted to change
>> over to the latest packages from the clusterlabs repo in my RHEL 5.5
>> machines.
>>
>> Steps I took
>> 1. Disabled the old repo
>> 2. Set the nodes to standby (two node drbd cluster) and turned of openais
>> 3. Enabled the new repo.
>> 4. Performed an update with yum -y update which replaced all packages.
>> 5. The configuration file for ais was renamed openais.conf.rpmsave
>> 6. I ran corosync-keygen and copied the key to the second machine
>> 7. I copied the file openais.conf.rpmsave to /etc/corosync/corosync.conf
>> and modified it by removing the service section and moving that to
>> /etc/corosync/service.d/pcmk
>> 8. I copied the configurations to the other machine.
>> 9. When I try to start either openais or corosync with the init scripts
>> I get a failure and nothing that can really point me to an error in the
>> logs.
>>
>> Updated packages:
>> May 26 14:29:32 Updated: cluster-glue-libs-1.0.5-1.el5.x86_64
>> May 26 14:29:32 Updated: resource-agents-1.0.3-2.el5.x86_64
>> May 26 14:29:34 Updated: cluster-glue-1.0.5-1.el5.x86_64
>> May 26 14:29:34 Installed: libibverbs-1.1.3-2.el5.x86_64
>> May 26 14:29:34 Installed: corosync-1.2.2-1.1.el5.x86_64
>> May 26 14:29:34 Installed: librdmacm-1.0.10-1.el5.x86_64
>> May 26 14:29:34 Installed: corosynclib-1.2.2-1.1.el5.x86_64
>> May 26 14:29:34 Installed: openaislib-1.1.0-2.el5.x86_64
>> May 26 14:29:34 Updated: openais-1.1.0-2.el5.x86_64
>> May 26 14:29:34 Installed: libnes-0.9.0-2.el5.x86_64
>> May 26 14:29:35 Installed: heartbeat-libs-3.0.3-2.el5.x86_64
>> May 26 14:29:35 Updated: pacemaker-libs-1.0.8-6.1.el5.x86_64
>> May 26 14:29:36 Updated: heartbeat-3.0.3-2.el5.x86_64
>> May 26 14:29:36 Updated: pacemaker-1.0.8-6.1.el5.x86_64
>>
>> Apparently corosync is sec faulting when run from the command line:
>>
>> # /usr/sbin/corosync -f
>> Segmentation fault
>>
>> Any help would be greatly appreciated.
>>
>> Diego
>>
>>
>>
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at 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
> 

-- 
Diego Julian Remolina
System Administrator - Systems Support Specialist IV
School of Physics
Georgia Institute of Technology
Phone: (404) 385-3499




More information about the Pacemaker mailing list