Could you check the ps axf output for a second corosync or openais process? Something out there is sending SIGTERM to the pacemaker daemons:
Dec 10 11:48:12 localhost pengine: [23775]: info: crm_signal_dispatch: Invoking handler for signal 15: Terminated On Thu, Dec 10, 2009 at 9:02 PM, Brian Ferris <bdfer...@gmail.com> wrote: > I'm running pacemaker-1.0.6 and corosync-1.1.2 on Fedora 11 using rpms > available from clusterlabs.org. > > I'm new to this stuff, and I've been having some trouble getting things > started. Specifically, I'm seeing the following messages in my logs when I > attempt to startup corosync: > > Dec 10 11:47:47 localhost attrd: [23774]: info: init_ais_connection: > Creating connection to our AIS plugin > Dec 10 11:47:47 localhost attrd: [23774]: info: init_ais_connection: > Connection to our AIS plugin (9) failed: Try again (6) > > I see that same sequence of messages for attrd, cib, stonithd. They are > repeated endlessly until the programs decide to stop retrying. This seems > to be the closest thing I can find to a root error, but I'm not sure how to > address this. > > I've attached my full message log, my corosync.conf, and cib.xml file, if > any of that helps. > > Any ideas? > > Thanks, > Brian > > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
