 | ||
| Starting the Apache HTTP Server instance outside ApplicationHA control | ||
|---|---|---|
| Prev | Troubleshooting the agent for Apache HTTP Server | Next |
| ||
| Starting the Apache HTTP Server instance outside ApplicationHA control | ||
|---|---|---|
| Prev | Troubleshooting the agent for Apache HTTP Server | Next |
If you face problems while working with an instance, you must disable the instance within the ApplicationHA framework. A disabled instance is not under the control of the ApplicationHA framework, and so you can test the Apache HTTP Server instance independent of the ApplicationHA framework. Refer to the Symantec Cluster Server Administrator's Guide for information about disabling a resource.
You can then restart the Apache HTTP Server instance outside the ApplicationHA framework.
Note: |
When you restart the instance outside the ApplicationHA framework, use the same parameters that the instance attributes define within the ApplicationHA framework. |
When you bring an Apache HTTP Server online outside of ApplicationHA control, first source its environment file. Start the server with the -f option so the server knows which instance to start.
A sample procedure to start an Apache HTTP Server instance outside the ApplicationHA framework is illustrated as follows.
To restart the Apache HTTP Server outside the framework
# su ApacheUser
$ httpdDir/envvars; Apache_HTTP_Server_executable -f ConfigFile
For example:
$ /apache/v2.2/bin/envars;/apache/v2.2/bin/httpd -f \
/apache/v2.2/conf/httpd.conf -k start
If the Apache HTTP Server works correctly outside the ApplicationHA framework, you can then attempt to implement the Apache HTTP Server within the ApplicationHA framework.