[ClusterLabs] "waiting for apache /usr/local/httpd/conf/httpd.conf to come up"
hunter86_bg at yahoo.com
Wed Feb 19 16:03:30 EST 2020
On February 19, 2020 9:48:07 PM GMT+02:00, Paul Alberts <Paul.Alberts at ibm.com> wrote:
>you are correct - that was my bad typing.
>The status url is using the virtual_ip and is accessible from either
>node of the cluster but from nowhere else.
>pcs resource create ContentServer ocf:heartbeat:apache
>statusurl="http://$VIRTUAL_IP:1090/server-status" op monitor
>interval=1min --group content_svc
>I get this:
> Resource Group: content_svc
> prodplmvg (ocf::heartbeat:LVM): Started ha1.company.com
> fs_plmlv (ocf::heartbeat:Filesystem): Started ha1.company.com
> fs_sapcslv (ocf::heartbeat:Filesystem): Started ha1.company.com
>content_vip (ocf::heartbeat:IPaddr2): Started
>ContentServer (ocf::heartbeat:apache): Starting
>until the ContentServer resource shows stopped.
>pcs resource debug-start ContentServer --full
> apache not running
> waiting for apache /usr/local/httpd/conf/httpd.conf to come up
>It seems something is getting miscommunicated to
>/usr/lib/ocf/resource.d/heartbeat/apache but I haven't yet been able to
>determine what exactly.
>thank you for your time and response,
>Paul.Alberts at ibm.com
>-----Strahil Nikolov <hunter86_bg at yahoo.com> wrote: -----
>To: Cluster Labs - All topics related to open-source clustering
>welcomed <users at clusterlabs.org>, Paul Alberts <Paul.Alberts at ibm.com>
>From: Strahil Nikolov <hunter86_bg at yahoo.com>
>Date: 02/19/2020 12:17
>Subject: [EXTERNAL] Re: [ClusterLabs] "apache httpd program not found"
>"environment is invalid, resource considered stopped"
>On February 19, 2020 6:27:54 PM GMT+02:00, Paul Alberts
><Paul.Alberts at ibm.com> wrote:
>>Manage your subscription:
>>ClusterLabs home: https://www.clusterlabs.org/
>I hope that the url is wrong due to copy/paste:
>Otherwise - check the protocol.As status URL should be available
>only from 127.0.0.1, you can use 'http' instead.
In the RA it is clearly stated:
If you set this, make sure that it succeeds *only* from localhost (127.0.0.1). Otherwise, it may happen that the cluster complains about the resource being active on multiple nodes.
It seems that you use local apache conf - this can cause trouble supporting any changes in the future. I would recommend you to create 2 directories on a shared storage:
A) for DocumentRoot
B) for Configurations
Set the proper selinux context and update the resource.
Also verify that the binary is available on all nodes. I think you mentioned compiling the binary from source .
Any reason behind that ?
More information about the Users