On Thu, Mar 1, 2012 at 8:47 AM, Stefan Schloesser <[email protected]> wrote: > Hi Florian, > > thanks for the link, I added the > COROSYNC_DEFAULT_CONFIG_IFACE="openaisserviceenableexperimental:corosync_parser" > Param to no avail, also tried stonith (though I don't see why this should be > required as long both nodes are up - I am not even there yet!). > Does this mean this type of config is not yet production ready? If so, what > is the recommended stack for: > Apache & mysql in a dual primary setup?
None, because dual-Primary and OCFS2 are utterly pointless for Apache and MySQL. Apache and MySQL can be easily built on single-Primary DRBD with a regular filesystem (ext3/4, XFS, you name it). > I tried a > /usr/sbin/ocfs2_controld.pcmk -D > ocfs2_controld[10624]: 2012/03/01_08:41:26 ERROR: init_ais_connection_once: > Invalid cluster type: heartbeat (4) > 1330587686 setup_stack@158: Connection to our AIS plugin (9) failed Well, a Corosync service won't work too well if your cluster is built on Heartbeat, which it looks like it is. :) So if you really must use OCFS2 (which I think you don't), switch that Heartbeat/Pacemaker cluster to Corosync/Pacemaker. Cheers, Florian -- Need help with High Availability? http://www.hastexo.com/now _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
