Interstage Shunsaku Data Manager Troubleshooting - Microsoft(R) Windows(R) 2000/ Microsoft(R) Windows Server(TM) 2003 - - UNIX -
Contents Index PreviousNext

Chapter 1 Overview of Troubleshooting> 1.3 Analyzing and Handling Problems

1.3.4 Checking and Handling the Hang-up

Refer to the procedure below to identify the error event and to check and handle hang-ups.

Inform a Fujitsu systems engineer if the problem is identified.
Refer to Chapter 3 - Collecting Troubleshooting Information for more information on how to collect troubleshooting information.

A system may seem to be hung-up if execution takes more time than usual. To ascertain whether or not a system is hung-up, follow the procedure below:

Execute the following command from another window that is not hung-up. Then use the CPU use rate to consider whether or not the system is hang-up.
mpstat  -p  [execution time interval (sec.)]  [number of execution]

Note: Execution will not stop if the number of executions is omitted.
The following example will collect information every second for 60 times (1 minute):
mpstat  -p  1  60
Note the value of "usr" + "sys" in the information displayed. If the value dose not change, consider the system hung-up.

Execute the following command from another window that is not hung-up. Then use the CPU use rate to consider whether or not the system is hang-up.
mpstat  -P  ALL  [execution time interval (sec.)]  [number of execution]
Note: Execution will not stop if the number of executions is omitted.
The following example will collect information every second for 60 times (1 minute):
mpstat  -P  ALL  1  60
Note the value of "%user" + "%system" in the information displayed. If the value does not change, consider the system hung-up.

Start the Task Manager. Select the Processes tab and note the value of the "CPU" for the exe files that include "shun" in the file name. If the value does not change, consider the system hung-up.

Contents Index PreviousNext

All Rights Reserved, Copyright (C) FUJITSU LIMITED 2006