No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Service node Apache cluster process exception cause service window cannot display normally

Publication Date:  2012-09-24 Views:  41 Downloads:  0
Issue Description
Product and edition information: applied for CSE V100R001C00(including operating management platform, service self-management platform, storage online service and backup online service).
Service node deploys operating management platform, service self-management platform, storage online service and backup online service with a cluster way simultaneously.
When users access service interface window of CSE, the window cannot display normally. In ISM management interface window, the alarm reported by system is as the form1-1.

Alarm Information
na
Handling Process
Step 1 do service heartbeat start command on service node, start Apache cluster process
Step 2 do ps ef|grep httpd command, the process display normal.
Step 3 do ifconfig command, node virtual IP address display normal.
Step 4 log on CSE service node again, the interface page can be accessed normally. The failure is solved.

Root Cause
1. Do ping command on NM server, the network communication between this node and NM server is normal.
2. Check switch, T8000 server device and system data node, all is powered on. The connection between all devices is correct and indictor of network cable port is normal. So, device hardware failure and network exception can be eliminated.
3. Log on this service node with SSH, do ps ef|grep httpd command. Apache cluster process do not start normally, system would display like this when start normally:
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. Do ifconfig command, virtual IP address of this node can be found on system information bond1:0. Commonly, a line inet x.x.x.x is in bond1:0, and x.x.x.x is virtual IP address.
It is concluded that this failure is caused by service node Apache cluster process exception.

Suggestions
After devices reboot, please check if Apache cluster process and tomcat process start normally. If not, start them manually.

END