[Pacemaker] Frustrating fun with Pacemaker / CentOS / Apache
Paul Graydon
paul at ehawaii.gov
Wed Feb 17 00:42:31 UTC 2010
On 2/16/2010 1:04 PM, Angie T. Muhammad wrote:
>
>
> On Wed, Feb 17, 2010 at 12:21 AM, Paul Graydon <paul at ehawaii.gov
> <mailto:paul at ehawaii.gov>> wrote:
>
> On 2/16/2010 10:48 AM, Andrew Beekhof wrote:
>> The first error doesn't concern me particularly, it's a known
>> Apache bug
>>> relating to the proxy module that doesn't actually break anything. It's the
>>> binding errors that are bothering me and presumably what is stopping
>>> pacemaker from starting the service successfully. Whats really odd about
>>> that error is I can run "/etc/init.d/httpd start" quite happily myself and
>>> it works. There is absolutely nothing sitting listening on port 80 at all
>>> for it to struggle with. Occasionally it seems to start it but I've no idea
>>> why it will succeed then when it fails in the large majority of the time.
>>> Really wild stab in the dark, but is there a chance pacemaker is attempting
>>> to start the httpd process multiple times?
>>>
>> Unlikely, usually its caused by LSB services being told to start at boot time.
>>
>
> That was one of the earliest thoughts I had, sorry I meant to put
> this in my first message:
>
> # chkconfig --list httpd
> httpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off
>
> I suffered from the same problem as you do. It is always highly
> recommended to use OCF modules written specifically for your service
> rather than LSB. Aside of your stack (openAIS or Heartbeat), errors
> will pop up when stopping httpd if you are using LSB..
That seems to be it in a nutshell. Switched over to
ocf::heartbeat:apache and all works a charm. Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20100216/c4cb3570/attachment-0002.htm>
More information about the Pacemaker
mailing list