I don't see any corosync-1.2.0 rpms up at <a href="http://clusterlab.org">clusterlab.org</a> rpm site. It looks like corosync-1.2.0 has only been out for six days? Would the pacemaker-1.0.6 from Nov 04 really be built against it?<div>
<br><br><div class="gmail_quote">On Mon, Dec 14, 2009 at 1:20 AM, Andrew Beekhof <span dir="ltr"><<a href="mailto:andrew@beekhof.net">andrew@beekhof.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Fri, Dec 11, 2009 at 5:34 PM, Brian Ferris <<a href="mailto:bdferris@gmail.com">bdferris@gmail.com</a>> wrote:<br>
> I checked to verify that there were no other openais or corosync processes<br>
> running.<br>
><br>
> I think that crm_signal_dispatch signal termination message you saw was me<br>
> manually killing the corosync process tree, or at least attempting to stop<br>
> things. I've attached a new trace that shows me running corosync for a good<br>
> six minutes before attempting to kill it. You still see the<br>
> crm_signal_dispatch about six minutes in when I'm attempting to shut things<br>
> down. I'm not sure it's a symptom of the actual underlying problem (of<br>
> course, I could be wrong).<br>
><br>
> Any other ideas? Anything additional I could enable in terms of logging /<br>
> debugging that might show useful diagnostic info?<br>
<br>
</div>perhaps adding "debug: on" in corosync.conf, but I see:<br>
<br>
Dec 11 08:22:49 localhost corosync[1632]: [MAIN ] Corosync Cluster<br>
Engine ('1.1.2'): started and ready to provide service.<br>
<br>
IIRC, the packages were built against 1.2.0... maybe thats causing the problem.<br>
Check for a corosync update?<br>
<div><div></div><div class="h5"><br>
><br>
> Thanks,<br>
> Brian<br>
><br>
><br>
> On Fri, Dec 11, 2009 at 2:13 AM, Andrew Beekhof <<a href="mailto:andrew@beekhof.net">andrew@beekhof.net</a>> wrote:<br>
>><br>
>> Could you check the ps axf output for a second corosync or openais<br>
>> process?<br>
>> Something out there is sending SIGTERM to the pacemaker daemons:<br>
>><br>
>> Dec 10 11:48:12 localhost pengine: [23775]: info: crm_signal_dispatch:<br>
>> Invoking handler for signal 15: Terminated<br>
>><br>
>> On Thu, Dec 10, 2009 at 9:02 PM, Brian Ferris <<a href="mailto:bdferris@gmail.com">bdferris@gmail.com</a>> wrote:<br>
>> > I'm running pacemaker-1.0.6 and corosync-1.1.2 on Fedora 11 using rpms<br>
>> > available from <a href="http://clusterlabs.org" target="_blank">clusterlabs.org</a>.<br>
>> ><br>
>> > I'm new to this stuff, and I've been having some trouble getting things<br>
>> > started. Specifically, I'm seeing the following messages in my logs<br>
>> > when I<br>
>> > attempt to startup corosync:<br>
>> ><br>
>> > Dec 10 11:47:47 localhost attrd: [23774]: info: init_ais_connection:<br>
>> > Creating connection to our AIS plugin<br>
>> > Dec 10 11:47:47 localhost attrd: [23774]: info: init_ais_connection:<br>
>> > Connection to our AIS plugin (9) failed: Try again (6)<br>
>> ><br>
>> > I see that same sequence of messages for attrd, cib, stonithd. They are<br>
>> > repeated endlessly until the programs decide to stop retrying. This<br>
>> > seems<br>
>> > to be the closest thing I can find to a root error, but I'm not sure how<br>
>> > to<br>
>> > address this.<br>
>> ><br>
>> > I've attached my full message log, my corosync.conf, and cib.xml file,<br>
>> > if<br>
>> > any of that helps.<br>
>> ><br>
>> > Any ideas?<br>
>> ><br>
>> > Thanks,<br>
>> > Brian<br>
>> ><br>
>> > _______________________________________________<br>
>> > Pacemaker mailing list<br>
>> > <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
>> > <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
>> ><br>
>> ><br>
>><br>
>> _______________________________________________<br>
>> Pacemaker mailing list<br>
>> <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
><br>
><br>
> _______________________________________________<br>
> Pacemaker mailing list<br>
> <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
><br>
><br>
<br>
_______________________________________________<br>
Pacemaker mailing list<br>
<a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
</div></div></blockquote></div><br></div>