Hi Richard
I think in your crm-configuration is the parameter "port" and "statusurl" obsolete. IMHO, you can delete this entries, because it will take the default-http-port 80 and the default-statusurl.
Can you please check, if you
don't have a running apache2 instance before you start the cluster-resource? If your apache2 is already started, you have to stop and disable it with "
rcapache2 stop; chkconfig apache2 off". Then you can start your cluster.
The following errormessage
|
Code:
|
/usr/lib/ocf/resource.d/heartbeat/apache: line 39: /resource.d/heartbeat/.ocf-shellfuncs: No such file or directory" |
is normal, because you have to call the ocf-apache-script with the OCF_ROOT like this:
|
Code:
|
node01:/ # OCF_ROOT=/usr/lib/ocf /usr/lib/ocf/resource.d/heartbeat/apache
usage: /usr/lib/ocf/resource.d/heartbeat/apache action
action:
start start the web server
stop stop the web server
status return the status of web server, run or down
monitor return TRUE if the web server appears to be working.
For this to be supported you must configure mod_status
and give it a server-status URL. You have to have
installed wget for this to work.
meta-data show meta data message
validate-all validate the instance parameters |
You can try to start your cluster manually with the ocf-script like this:
|
Code:
|
chvzg442:/ # OCF_ROOT=/usr/lib/ocf /usr/lib/ocf/resource.d/heartbeat/apache OCF_RESKEY_configfile=/etc/apache2/httpd.conf OCF_RESKEY_httpd=/usr/sbin/httpd2 start |
I hope this helps.
Kind regards,
Tom