On Mon, Dec 14, 2009 at 10:45 AM, Brian Ferris wrote:
> I don't see any corosync-1.2.0 rpms up at clusterlab.org 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?
Maybe not, I juts noticed that my f-12 pa
I don't see any corosync-1.2.0 rpms up at clusterlab.org 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?
On Mon, Dec 14, 2009 at 1:20 AM, Andrew Beekhof wrote:
> On Fri, Dec 11, 2009 at 5:34 PM, Brian Fer
On Fri, Dec 11, 2009 at 5:34 PM, Brian Ferris wrote:
> I checked to verify that there were no other openais or corosync processes
> running.
>
> I think that crm_signal_dispatch signal termination message you saw was me
> manually killing the corosync process tree, or at least attempting to stop
>
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 Fer
