Installing Apache as cluster package

New Member

Installing Apache as cluster package



How to  install the  apache version 2.2.15  as a cluster package in 2 node MC SG 11.19 active passive  cluster ( HP UX 11.23B) .I need step by step  procedure.Please help


Thanks in advance


Honored Contributor

Re: Installing Apache as cluster package

  1. Understand the requirements of the website you'll be running on Apache: is it just simple static content, or will the client action produce some persistent state information that must be maintained? Is the persistent state stored locally, or in a remote database? How much content will there be (a rough estimate)? Are there any filesystem layout requirements built in the site content? Are there security or other requirements you must fulfill (example: "There will be multiple departments, each maintaining their section of the site independently. Each section must have a separate disk space, so if one department runs out of space it won't cause problems to the others.")?
  2. Read the cluster and package design chapters of the "Managing Serviceguard" book, to understand what is possible and what isn't.
  3. Design a directory layout and Apache configuration that fulfills your requirements. Remember that you aren't constrained by the default directories: you can specify the configuration file location when starting Apache, and the configuration file can specify the locations of everything else required by Apache. In general, Apache is very flexible, and so is Serviceguard. At this point, your design process will be guided primarily by the requirements of your site (see step 1).
  4. Once you know and understand what you want/need in a detailed technical level, use the package planning worksheets included in the "Managing Serviceguard" book to organize the information required to configure Serviceguard.
  5. Download the Apache depot (2.2.15, latest patch level) from HP website Install it to both nodes, but make sure it won't start automatically at system startup. Read the provided startup/shutdown script to understand the commands required to start and stop Apache: you will need to include those in your package configuration (most likely with some modifications to read the configuration file from a custom location). Add this to your package planning worksheet too.
  6. Once you have your package planning worksheet ready, follow the step-by-step instructions in the "Managing Serviceguard" book and your worksheet to configure the package. This includes creating all the shared LUNs, VGs, filesystems, directories and mountpoints you'll need. But this is the easiest part of the procedure: if you have a junior sysadmin that needs the practice, you could let him/her do this part under your supervision.
  7. Test your configuration carefully to make sure it does what you want. When starting a package, "cmrunpkg <package_name>" should be the only command you need to make it start successfully.  Then simulate some failures (disconnect a network cable or two) to verify it really works, and to measure the actual failover time you can expect in a real failure situation.
  8. Before putting the clustered site into production, make sure it is secure. Public web services are an easy target for network intrusion: you don't want easily-guessable passwords. If possible, don't allow remote admin access from the Internet at all. The admin access should be allowed from trusted networks only.


Once you've done all this, you should be able to understand the configuration you've built. This is important when something goes wrong and you need to troubleshoot it. The understanding is also important if it becomes necessary to add some extra functionality that was not originally required.


The "Managing Serviceguard" book for SG 11.19 is available at:


The documentation for Apache 2.2.* web server is available at: