On Sat, Oct 1, 2011 at 5:32 AM, Miltiadis Koutsokeras < m.koutsoke...@biovista.com> wrote:
> From the > messages it seems like the manager is getting unexpected exit codes from > the > Apache resource. The server-status URL is accessible from 127.0.0.1 in both > nodes. > > Am I understanding correctly that Apache is already running prior to your starting corosync/pacemaker? You'll want to disable apache starting external to pacemaker, let the resource agent start it. You say it's accessible from loopback and you attached output of server-status, although your crm_mon output clearly shows that it hasn't successfully started the Apache2 resource. When pacemaker is started, apache shouldn't be running on either node. Sorry if I'm misunderstanding the scenario, though. Regards, Mark
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
