Service GUIs Fail to Be Displayed Because the Apache Cluster Process on a Service Node Is Abnormal

Publication Date:  2012-07-17 Views:  163 Downloads:  0
Issue Description
Related information about the product and version: CSE V100R001C00 (The CSE includes the storage operation management system, business self-management system, online storage, and online backup.)

Storage Operation Management System, Business Self-Management System, Online Storage, and Online Backup are deployed in clustering on a service node.
Service GUIs fail to be displayed when users attempt to access service GUIs on the ISM.
Alarm Information
None
Handling Process
Step 1     Run the service heartbeat stop command on the service node to stop the Apache cluster process.

                               Step 2     Run the service heartbeat start command on the service node to start the Apache cluster process.

                               Step 3     Run the ps ef|grep httpd command to check whether the Apache cluster process is running properly.

                               Step 4     Run the ifconfig command to check whether the virtual IP address of the service node is correctly displayed.

                               Step 5     Check whether CSE service GUIs can be displayed. If yes, the fault is removed. If no, contact technical support engineers.

----End

Root Cause
On the ISM interface, the alarm listed in Table 1-1 is reported.
Table 1-1 Alarm on a service node response failure
Alarm Severity Alarm ID Alarm Name Alarm Description
Critical 0xB02230002 Service node response failure The service node does not respond. (The service node name will be displayed.)
1.         Log in to the service node by using KVM. Then run the ping command on the Base plane (external). The execution result shows that the network connection between this node and the ISM server is interrupted.
2.         Check the switches, T8000 server, and system data nodes. These devices are properly powered on. Network cables among devices are correctly connected. Status of network port indicators are normal. Therefore, the service node response failure is not caused by hardware faults or abnormal network communication.
3.         Run the ps ef|grep httpd command. The Apache cluster process is found disabled. If the Apache cluster process is enabled, the following information will be displayed after the execution of the command:
root      4973     1  0 Apr20 ?        00:00:00 /opt/apache-2.2.11/bin/httpd -k start
daemon   10332  4973  0 16:16 ?        00:00:00 /opt/apache-2.2.11/bin/httpd -k start
daemon   10460  4973  0 16:18 ?        00:00:00 /opt/apache-2.2.11/bin/httpd -k start
daemon   11249  4973  0 16:24 ?        00:00:00 /opt/apache-2.2.11/bin/httpd -k start
daemon   11428  4973  0 16:25 ?        00:00:00 /opt/apache-2.2.11/bin/httpd -k start
daemon   11433  4973  0 16:25 ?        00:00:00 /opt/apache-2.2.11/bin/httpd -k start
daemon   11713  4973  0 16:27 ?        00:00:00 /opt/apache-2.2.11/bin/httpd -k start
daemon   11714  4973  0 16:27 ?        00:00:00 /opt/apache-2.2.11/bin/httpd -k start
daemon   11835  4973  0 16:28 ?        00:00:00 /opt/apache-2.2.11/bin/httpd -k start
daemon   11956  4973  0 16:29 ?        00:00:00 /opt/apache-2.2.11/bin/httpd -k start
daemon   11959  4973  0 16:29 ?        00:00:00 /opt/apache-2.2.11/bin/httpd -k start
daemon   11960  4973  0 16:29 ?        00:00:00 /opt/apache-2.2.11/bin/httpd -k start
daemon   12117  4973  0 16:30 ?        00:00:00 /opt/apache-2.2.11/bin/httpd -k start
root     12592  3468  0 16:34 pts/1    00:00:00 grep httpd
4.         Run the ifconfig command. The virtual IP address of the service node is not included in bond1:0. bond1:0 generally includes inet x.x.x.x. x.x.x.x indicates the virtual IP address of the service node.
Therefore, the service node response failure is caused by the abnormal Apache cluster process on this node.
 
Suggestions
None

END