The error messages that might be displayed during the Apache hierarchy creation are listed below, along with a suggested explanation for each. Error messages displayed by the LifeKeeper core and by other recovery kits are not listed in this guide. Note that you may stop to correct any of the problem(s) described here, and then continue with hierarchy creation from the point where you left off – including creating any new LifeKeeper resources you might need for your Apache configuration.

During Validation of Web Server Binary Location

“Error: valid_httpd_path: Must specify absolute path to httpd executable.”

Enter the full, absolute path name to a valid Apache httpd executable.


“Error: valid_httpd_path: File does not exist at path specified.”

A valid Apache httpd executable does not exist at the location specified.


“Error: valid_httpd_path: Httpd failed to display Server version.”

The httpd executable at the location specified does not display the standard Apache “Server version.”


“Error: valid_httpd_path: Incorrect version $MAJOR.$MINOR.$POINT of Apache at $HTTPD_PATH.

The Apache httpd executable at the location specified displays the incorrect “Server version.”



During Validation of Web Server Root Directory

“Error: valid_http_root: Cannot find Apache configuration file at $CONF_FILE.”

Must have valid Apache configuration file at conf/httpd.conf relative to the Server Root directory specified. Note that the default installation of Apache on SuSE does not place the httpd.conf configuration file in a subdirectory of ServerRoot called conf. If you are using the default installation of Apache on SuSE, you must relocate the configuration file to the directory /etc/httpd/conf.


“Error: valid_http_root: Must specify absolute path to Apache server root directory.”

Enter full, absolute path name to a Server Root directory.


“Error: valid_http_root: Apache instance at $HTTP_ROOT is already under LifeKeeper protection.”

Each instance must have its own, unique Server Root directory, with configuration file located at conf/httpd.conf. The Server Root directory specified is already being used by another Apache instance.


“Syntax error on line <line number> of <configuration file path>, etc…”

Syntax error(s) were found in the Apache configuration file. These error messages were displayed by the httpd -T command when used to check the syntax of $CONF_FILE. See the error messages displayed for details.


“Error: valid_http_root: Since $HTTPD_PATH is shareable on $HTTPD_PATH_SHARED, $HTTP_ROOT must be also.”

If the httpd executable is on shared/shareable storage, the Server Root and all DocumentRoot directories must be also.


“Error: valid_http_root: Since $HTTP_ROOT is shareable on $HTTP_ROOT_SHARED, all document root directories must shareable on this same filesystem.”

If the Server Root is on shared/shareable storage, all DocumentRoot directories must be also.


“Error: http_docs_shared: Since one/more Apache document root directories are shareable on $docs_shared, $curr_root must be also.

If any DocumentRoot directories are on a shared/shareable file system, all DocumentRoot directories must be located on the same file system.


“Error: valid_http_root: Must include BindAddress or Listen directives for each Apache instance. Check the Apache configuration file at $CONF_FILE.”

In order to run multiple instances of Apache, each configuration file must contain BindAddress or Listen directives. Please refer to the Configuration Considerations for Apache Web Server section earlier in this guide for further detail.


“Error: valid_http_root: Default IP address * not allowed for LifeKeeper protection. Check the Apache configuration file at $CONF_FILE.”

You must specify at least one specific LifeKeeper protected IP address for each Apache instance.


“Error: valid_http_root: A Listen directive is being used which specifies an IP address but no port. Check the Apache configuration file at $CONF_FILE.”

The correct syntax for the Listen directive is Listen [IPaddress:] port number. This is not caught as a syntax error by Apache, but is interpreted incorrectly (as though the first number in the IP address was a port number specification).


“Error: valid_http_root: IP address $ip is not LifeKeeper protected.”

The Apache configuration file refers to an IP address or domain name not configured under LifeKeeper protection. You must create these LifeKeeper IP address resources in advance.



During Apache Resource Hierarchy Creation

“Error: Could not find IP resource for $IP_ADD on machine $MACH.”

You must create this resource before the Apache resource creation will succeed.


“Error: Create Apache file system hierarchy failure for filesystem $FSNAME used by server root $HTTP_ROOT.”

“Error: Failure bringing Apache Resource $TAG into service on machine $MACH.”

Check the Apache error logs for messages (default location is /var/log/httpd/error_log, but other logs may be listed).

The most likely cause of this problem is an error in the Apache configuration file. You may be able to bring this resource into service manually after correcting the problem.

“LifeKeeper: RESTORE: *ERROR* Apache: The instance is Password Protected.”

The LifeKeeper Apache Web Server Recovery Kit cannot support password protected Private Key files for SSL-enabled web servers, since this would require manual interaction each time Apache starts up, and would prevent automatic restart and failover. The section Specific Configuration Considerations for Apache Web Server in this document explains how to remove password protection from the Private Key file (specified by the SSLCertificateKeyFile directive). This message applies only in an environment where the SSL module is used with Apache.

Feedback

Thanks for your feedback.

Post your comment on this topic.

Post Comment