I am trying to set up Corosync + Pacemaker on a new CentOS 5.5 x86_64 install, 
but when I try to start corosync, it just says [FAILED] and does not provide 
any further information. I created the authkey using corosync-keygen and 
created a corosync.conf file. The log file remains empty and no errors are 
displayed on the console when it fails to start. I tried downgrading to 
1.2.1-1.el5, but that did not resolve the issue either. So I have re-upgraded 
back to 1.2.2-1.1.el5.

I also tried running corosync manually (as opposed to using the init script) 
and tried passing '-f' flag. Both of those attempts resulted in the same 
situation. It just gives me a prompt back and displays nothing in the way of 
errors either on the screen or in the log file. Finally, I tried running it 
under the GNU debugger. This says it exited with code 010. I have no idea what 
that means.

Anyone have any suggestions about how I can figure out what is causing the 
problem?

Eliot Gable
Senior Product Developer
1228 Euclid Ave, Suite 390
Cleveland, OH 44115

Direct: 216-373-4808
Fax: 216-373-4657
ega...@broadvox.net<mailto:ega...@broadvox.net>

[cid:image001.gif@01CB0ED8.F4F060B0]
CONFIDENTIAL COMMUNICATION.  This e-mail and any files transmitted with it are 
confidential and are intended solely for the use of the individual or entity to 
whom it is addressed. If you are not the intended recipient, please call me 
immediately.  BROADVOX is a registered trademark of Broadvox, LLC.


________________________________
CONFIDENTIAL. This e-mail and any attached files are confidential and should be 
destroyed and/or returned if you are not the intended and proper recipient.

<<inline: image001.gif>>

_______________________________________________
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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker

Reply via email to