InfoScale™ Cluster Server 9.0 Bundled Agents Reference Guide - Solaris
- Introducing bundled agents
- Storage agents
- DiskGroup agent
- DiskGroupSnap agent
- Notes for DiskGroupSnap agent
- Sample configurations for DiskGroupSnap agent
- Disk agent
- Volume agent
- VolumeSet agent
- Sample configurations for VolumeSet agent
- Mount agent
- Sample configurations for Mount agent
- Zpool agent
- VMwareDisks agent
- SFCache agent
- Network agents
- About the network agents
- IP agent
- NIC agent
- About the IPMultiNICB and MultiNICB agents
- IPMultiNICB agent
- Sample configurations for IPMultiNICB agent
- MultiNICB agent
- Sample configurations for MultiNICB agent
- DNS agent
- Agent notes for DNS agent
- About using the VCS DNS agent on UNIX with a secure Windows DNS server
- Sample configurations for DNS agent
- File share agents
- NFS agent
- NFSRestart agent
- Share agent
- About the Samba agents
- NetBios agent
- Service and application agents
- AlternateIO agent
- Apache HTTP server agent
- Application agent
- Notes for Application agent
- Sample configurations for Application agent
- CoordPoint agent
- LDom agent
- Dependencies
- Process agent
- Usage notes for Process agent
- Sample configurations for Process agent
- ProcessOnOnly agent
- Project agent
- RestServer agent
- Zone agent
- Infrastructure and support agents
- Testing agents
- Replication agents
Troubleshooting Apache service group issue
When you restart a node, zone, or LDom, the directory containing the PID file gets emptied and hence the Apache PID file directory is not present on the system.
For example, if /var/run/apache2 is missing, the PID file cannot be created and the start command $HttpdDir/httpd -f config_file -k start fails with the following error message:
No such file or directory: could not create /var/run/apache2/httpd.pid
As the startup command fails outside of VCS control, the Apache agent fails to bring the Apache service group online.
You can resolve this issue in one of the following ways:
Ensure that the directory to write Apache PID files is present persistently on the node, zone, or LDom.
For example, in the
httpd.conf
file, change the PidFile attribute to the persistently available location: /apache/my_conf/http.pid.Write a preonline trigger script to create the required directory for the Apache service group.
For example: mkdir /var/run/apache2
Refer to the Cluster Server Administrator's Guide for more details on VCS triggers.