10.5.2 How to collect data in a UNIX environment

(1) Executing the data collection command

Use the jpcras command to collect data needed to determine the cause of an error. Note that an OS user with root user permissions must perform the procedure described below.

To execute the data collection command:

1. Log on to the host where the service subject to this data collection is installed.

2. Execute the jpcras command with the data to be collected and the data storage directory to be used specified.

   The following jpcras command stores all the available information in the /tmp/jpc/agt directory:

   jpcras /tmp/jpc/agt all all

   The data collected by the data collection command is compressed and stored in the specified directory by the tar and compress commands. The file name is as follows:

   jpcrasYYMMDD#.tar.Z

   #: YYMMDD is replaced with the year, month, and day.

When you execute the jpcras command, the jpctool service list -id * -host * command is executed internally in order to obtain a list of PFM services and to check their activity status. If there is a firewall between the host where the command is executed and the host for the Performance Management system or if the system configuration is large, it might take a while for the jpctool service list -id * -host * command to execute. In such a case, you can suppress execution of the jpctool service list -id * -host * command, thus reducing the command execution time, by specifying 1 in the JPC_COLCTRLNOHOST environment variable.

For details about the jpcras command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

To Page Top

(2) Executing the data collection command (for logical host operation)

Performance Management information for logical host information is on the shared disk and must be collected in both the executing system and the standby system. Use the jpcras command to collect data needed to determine the cause of an error. Note that an OS user with the root user permissions must perform the procedure described below.

To execute the data collection command for logical host operation:

1. Mount the shared disk.

   Information about the logical host is stored on the shared disk. At the executing node, make sure that the shared disk is mounted, and then collect the information.

2. Execute the jpcras command in both the executing system and the standby system, with the data to be collected and the data storage directory to be used specified.

   The following jpcras command stores all the available information in the /tmp/jpc/agt directory:

   jpcras /tmp/jpc/agt all all

   The data collected by the data collection command is compressed and stored in the specified directory by the tar and compress commands. The file name is as follows:

   jpcrasYYMMDD#.tar.Z

   #: YYMMDD is replaced with the year, month, and day.

   Executing the jpcras command without the lhost argument specified collects all the Performance Management information on the physical and logical hosts at that node. If there is a Performance Management in the logical host environment, the log files on the shared disk are acquired.

   If the jpcras command is executed at a node where the shared disk is not mounted, files will not be acquired from the shared disk, but the command will terminate normally without resulting in an error.

   Note

   Execute the data collection command at both the executing node and the standby node to collect information. To examine an event before and after failover, you need the information from both systems (executing and standby).

   For details about the jpcras command, see the chapter that describes commands in the manual JP1/Performance Management Reference.

3. Collect information about the cluster software.

   This information is needed to determine whether the problem occurred in the cluster software or in Performance Management. Collect the information that provides control requests, such as startup and termination of Performance Management from the cluster software, and their results.

To Page Top

(3) Checking information about the operation

Check and save information about the operation that was underway when the error occurred. The following lists the information that you should check and save:

• Details of the operation

• Time the error occurred

• Machine configuration (such as the version of each OS, host name, and configuration of PFM - Manager and PFM - RM for Platform)

• Whether the problem is repeatable

• Performance Management user name used during logon, if the user has logged on from PFM - Web Console

• Any arguments specified in a command, if the problem occurred during command execution

To Page Top

(4) Collecting error information on screen displays

Collect the following error information:

• The messages that were output to the console, if the error occurred during command execution

To Page Top