> > So I compared the /etc/ais/openais.conf in non-sp1 with > /etc/corosync/corosync.conf from sp1 and found this bit missing which > could be quite useful... > > service { > # Load the Pacemaker Cluster Resource Manager > ver: 0 > name: pacemaker > use_mgmtd: yes > use_logd: yes > } > > Added it and it works. Doh. > > It seems the example corosync.conf that is shipped won't start > pacemaker, I'm not sure if that's on purpose or not, but I found it a > bit confusing after being used to it 'just working' previously.
Ah. Understandably confusing. That got fixed post-SP1, in a maintenance update that went out in September or thereabouts. Regards, Tim -- Tim Serong <tser...@novell.com> Senior Clustering Engineer, OPS Engineering, Novell Inc. ------- Thanks Tim. Although the media that can be downloaded *now* from Novell downloads still has this issue, so any new clusters will fall foul of it. Generally with a test build you won't perform updates as it burns a licence you would need for the production system. Should the downloadable media have the issue fixed? Regards, Darren _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems