Thanks! I had seen the entry for pacemaker in
/etc/corosync/corosync.conf, didn't realize that it was a duplicate of
/etc/corosync/services.d/pcmk.
I rebuilt the VMs from scratch so I had a clean install, then applied my
configuration, removing the /etc/corosync/services.d/pcmk file, rebooted
the VMs and all was well.
On 10/16/2011 09:05 PM, Tim Serong wrote:
On 17/10/11 14:05, Earl Ruby wrote:
On 10/13/2011 08:33 PM, Tim Serong wrote:
What's the bug number please?
https://bugzilla.novell.com/show_bug.cgi?id=685470
The problem is that /etc/corosync/corosync.conf (based off the example
file shipped on openSUSE) already includes a service section which loads
Pacemaker. The documentation in Clusters from Scratch says to add a
separate service.d/pcmk file, which was also done in this case. So, two
Pacemaker service definitions means corosync tries to start Pacemaker
twice, which is not good. Just delete /etc/corosync/service.d/pcmk and
you'll be OK.
Regards,
Tim
--
Earl C. Ruby III
Director of Engineering
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
