Installing and Configuring Apache Toolkit for Serviceguard for Linux

ManualsBrandsHP ManualsSoftwareHP Serviceguard for Linux ProLiant Cluster

INSTALLING AND CONFIGURING APACHE TOOLKIT

FOR SERVICEGUARD FOR LINUX

Executive Summary.........................................................................................................................2

Intended Audience..........................................................................................................................2

Introduction to the High Availability Apache Toolkit..............................................................................2

STORAGE CONFIGURATIONS.........................................................................................................3

SETTING UP THE APACHE WEB SERVER APPLICATION FOR AN SG/LX CLUSTER....................................4

Setting Up the Apache Web Server...............................................................................................4

Installing the High Availability Apache Toolkit..................................................................................5

CONFIGURING APACHE WEB SERVER PACKAGES IN AN SG/LINUX ENVIRONMENT...........................6

Configuring a Single Instance.......................................................................................................6

Configuring Multiple Instances....................................................................................................11

Maintenance Mode................................................................................................................... 13

SECURITY POLICIES IN LINUX.................................................................................................... 14

SELinux..................................................................................................................................14

AppArmor................................................................................................................................ 15

CONCLUSION ............................................................................................................................ 16

Summary of content (16 pages)

PAGE 1
INSTALLING AND CONFIGURING APACHE TOOLKIT FOR SERVICEGUARD FOR LINUX Executive Summary ......................................................................................................................... 2 Intended Audience.......................................................................................................................... 2 Introduction to the High Availability Apache Toolkit .............................................................................. 2 STORAGE CONFIGURATIONS..
PAGE 2
Executive Summary This document describes how to configure and run an Apache Web Server using the High Availability Apache Toolkit in the HP Serviceguard for Linux environment. This white paper introduces you to the High Availability Apace toolkit and outlines the procedures and tasks that you need to complete to install and configure the toolkit in your Linux environment with Serviceguard. In addition, this whitepaper also discusses security policies that have an impact on your Linux environment.
PAGE 3
To use the Apache Web Server application in your environment, the Apache web server must be installed on all cluster nodes configured to run an Apache package. A typical configuration of an Apache Web Server application is one where one node is configured as a primary node and the others are configured as standby or secondary nodes. The Apache Web Server application runs on the primary node and accepts (HTTP/S) requests and serves clients.
PAGE 4
SETTING UP THE APACHE WEB SERVER APPLICATION FOR AN SG/LX CLUSTER Once you decide on the storage configuration option, you can install the High Availability Apache Web Server Toolkit.
PAGE 5
exist by default. This file is used to define any user defined parameters. The Apache server fails to start if this file is not present. To start Apache successfully, either use the touch command to create a file or comment out the Include parameter in the httpd.conf file. 3) Create a separate, distinct server root directory and server configuration file for each Apache SG/Linux package. This server root directory corresponds to the Apache ServerRoot directive specified in the configuration file.
PAGE 6
This command installs the Apache toolkit. By default, the Apache toolkit directory is created in the following location: #/usr/local/cmcluster/apachetoolkit On SUSE Linux Enterprise Server: Change to your rpm package directory and enter the following command: #rpm –i apache-toolkit-.product.suse.noarch.rpm This command installs the Apache toolkit.
PAGE 7
In this method, the server root directory and the document root directory are maintained on a volume group that is shared among nodes of the cluster. Following is a sample procedure that indicates the steps that you must complete to configure an Apache instance that uses shared storage for all Apache instance data.
PAGE 8
toolkit.sh pkg.conf pkg.cntl Script that acts as an Interface between the package control script and main script (hahttp.sh) The package configuration file The package control script 2. Edit the package configuration file. Enter the following command to open the package configuration file: #vi /usr/local/cmcluster/pkg/apache1/pkg.conf You can edit the following variables in the package configuration file.
PAGE 9
FS_UMOUNT_OPT[0]=""; FS_FSCK_OPT[0]="" FS_UMOUNT_COUNT=1 FS_MOUNT_RETRY_COUNT=0 CONCURRENT_FSCK_OPERATIONS=1 CONCURRENT_MOUNT_AND_UMOUNT_OPERATIONS=1 IP[0]="15.70.191.6" SUBNET[0]="15.70.191.0" SERVICE_NAME[0]="apache1_service" SERVICE_CMD[0]="/usr/local/cmcluster/pkg/apache1/toolkit.sh monitor" SERVICE_RESTART[0]="" b.
PAGE 10
d Set the maintenance flag depending on whether you configure the package in the maintenance mode or not. If the maintenance flag is set, the package enters the maintenance mode when the file apache.debug is present in the package directory. MAINTENANCE_FLAG="no" e Set the rest of the parameters based on the requirement of your environment. MONITOR_INTERVAL=5 RETRY_TIMES=2 5. Edit the Listen parameter. • On a Red Hat system: This parameter is specified in httpd.
PAGE 11
Once the package starts, it starts an Apache server instance comprising of the Apache daemon, httpd, which spawns a number of sub-processes to handle numerous http requests. It also launches the Apache monitor script. Configuring Multiple Instances This section describes how to integrate multiple Apache Web Server instances using the High Availability Apache Web Server toolkit. Before integrating the instances, you must first create an instance of the Apache server.
PAGE 12
4. Edit the package control script. You must specify the following parameters to integrate multiple instances of the Apache server. The remaining parameters in the file must be configured as per the instructions for configuring a single instance package. VG[0]="/dev/vgtry2" LV[0]="/dev/vgtry2/lvol"; FS[0]="/mnt/vgtry2/apache"; IP[0]="15.70.191.7" SUBNET[0]="15.70.191.0" SERVICE_NAME[0]="apache2_service" SERVICE_CMD[0]="/usr/local/cmcluster/pkg/apache2/toolkit.
PAGE 13
If the AUTORUN parameter has disabled as the value, you must change it to enable. Run the following command to enable the AUTORUN parameter: For example: #cmmodpkg –e APACHE2 If switching is disabled for any node, enable it using the cmmodpkg command: For example: #cmmodpkg –e –n APACHE2 On completing this procedure, you would have created multiple Apache packages for multiple Apache instances that will be running on the cluster.
PAGE 14
5. Enter the following command to start the monitoring process: # rm -f /usr/local/cmcluster/pkg/apache1/apache.debug The following message is recorded in the Serviceguard package control script log: Starting Apache toolkit monitoring again after maintenance. 6. Enter the following command to enable package failover: #cmmodpkg -e APACHE1 NOTE: If the package fails during maintenance, the package does not automatically failover to an adoptive node.
PAGE 15
Access to the newly created directory or file is denied to Apache as the default Apache's security policy does not allow access to the file with the above set security context user_home_t. To make these new directories and files accessible to Apache processes, modify the security context of the directory /home/www/site1 to Apache's default security context using chcon utility, as shown below. The following example defines the steps to change the context for the Document Root.
PAGE 16
Access to the shared directory and files is denied to Apache because the default Apache's AppArmor profile does not allow access to these files. To grant access to the shared directory, complete the following steps: 1. To make the shared directory and files accessible by Apache, edit the Apache’s AppArmor profile (/etc/apparmor.d/usr.sbin.httpd2-prefork) by adding entries to grant access to the shared directory and files. For this, use a text editor or the YaST interface (Edit AppArmor Profile).