httpd.conf to come up"

Paul Alberts Thu, 20 Feb 2020 08:32:17 -0800

Strahil,

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.

_______________

After this:
pcs resource create ContentServer ocf:heartbeat:apache configfile=/usr/local/httpd/conf/httpd.conf port=1090 httpd=/usr/local/httpd/bin/apachectl statusurl="http://$VIRTUAL_IP:1090/server-status" op monitor interval=1min --group content_svc

I get this:
pcs resource
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 ha1.company.com
     ContentServer      (ocf::heartbeat:apache):        Starting ha1.company.com

until the ContentServer resource shows stopped.

then

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.albe...@ibm.com

-----Strahil Nikolov <hunter86...@yahoo.com> wrote: -----

To: Cluster Labs - All topics related to open-source clustering welcomed <users@clusterlabs.org>, Paul Alberts <paul.albe...@ibm.com>
From: Strahil Nikolov <hunter86...@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.albe...@ibm.com> wrote:
>_______________________________________________
>Manage your subscription:
>https://lists.clusterlabs.org/mailman/listinfo/users
>
>ClusterLabs home: https://www.clusterlabs.org/

I hope that the url is wrong due to copy/paste:
httpd://local/host:1090/server-status

Otherwise - check the protocol.As status URL should be available only from 127.0.0.1, you can use 'http' instead.

Best Regards,
Strahil Nikolov

_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users


ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] "waiting for apache /usr/local/httpd/conf/httpd.conf to come up"

Reply via email to