No subject

messages it seems like the manager is getting unexpected exit codes from th=
e<br>
Apache resource. The server-status URL is accessible from 127.0.0.1 in both=
 nodes.<br>
<br></blockquote><div><br></div><div>Am I understanding correctly that Apac=
he is already running prior to your starting corosync/pacemaker? =A0You&#39=
;ll want to disable apache starting external to pacemaker, let the resource=
 agent start it. =A0You say it&#39;s accessible from loopback and you attac=
hed output of server-status, although your crm_mon output clearly shows tha=
t it hasn&#39;t successfully started the Apache2 resource. =A0When pacemake=
r is started, apache shouldn&#39;t be running on either node.</div>
<div><br></div><div>Sorry if I&#39;m misunderstanding the scenario, though.=
</div><div><br></div><div>Regards,</div><div>Mark</div></div>

--20cf307d03c2a804db04ae3ee7bb--