Job Management Partner 1/Performance Management User's Guide

[Contents][Glossary][Index][Back][Next]

14.4.2 Data to be collected in the event of an error (in UNIX)

Organization of this subsection
(1) Log information about the OS
(2) Performance Management information
(3) PFM - Web Console information
(4) Operation information
(5) Error information
(6) Other information

(1) Log information about the OS

The following table lists the log information about the OS to be collected.

Type of information Outline Default file name Collected by the jpcras command Collected by the jpcwras command
System log syslog
  • In HP-UX
    /var/adm/syslog/syslog.log
  • In Solaris
    /var/adm/messages*
  • In AIX
    /var/adm/syslog*
  • In Linux
    /var/log/messages*
 Y#1 Y#1
Process information List of processes N/A Y Y
System file hosts file /etc/hosts Y Y
/etc/inet/ipnodes#2 Y#3 N
services file /etc/services Y Y
OS information Patch information N/A Y Y
Kernel information N/A Y Y
Version information N/A Y Y
Network status N/A Y Y
Environment variables N/A Y Y
Host name N/A Y Y
Dump information core file#4 N/A Y N

Legend:
Y: Can be collected
N: Cannot be collected
N/A: Not applicable

#1
This cannot be collected in a system where output is not set to the default path or file name. In this case, use a different method to collect this information.

#2
The /etc/inet/ipnodes file is available only under Solaris. Collect it together with the /etc/hosts file.

#3
This file can only be collected with the jpcras command included in PFM - Manager 09-00 or PFM - Base 09-00 or later.

#4
Under HP-UX 11i V3 (IPF), you can use the coreadm command to rename the core file. If the core file is renamed to a file name that does not start with core, the jpcras command cannot collect it. In this case, collect the file manually.

(2) Performance Management information

You need to collect the information about Performance Management listed below. In the case of a network error, you also need to collect applicable files from the connection-destination machine. The Performance Management information required to be collected is shown below.

Type of information Outline Default file name Collected by the jpcras command
Common message log Message log output from Performance Management (sequential file method) /opt/jp1pc/log/jpclog{01|02}#1 Y
Message log output from Performance Management (wraparound file method) /opt/jp1pc/log/jpclogw{01|02}#1 Y
Configuration information Each configuration information file N/A Y
Output results of the jpctool service list command N/A Y
Version information Product version N/A Y
History information N/A Y
Database information Name Server /opt/jp1pc/mgr/namesvr/*.DB
/opt/jp1pc/mgr/namesvr/*.IDX		 Y
Master Manager /opt/jp1pc/mgr/manager/*.DB
/opt/jp1pc/mgr/manager/*.IDX		 Y
Master Store /opt/jp1pc/mgr/store/*.DB
/opt/jp1pc/mgr/store/*.IDX		 Y
View Server /opt/jp1pc/mgr/viewsvr/data/*
/opt/jp1pc/mgr/viewsvr/Reports/*		 Y
Agent Store and Remote Monitor Store /opt/jp1pc/xxxx#2/store/instance-name#3/*.DB
/opt/jp1pc/xxxx#2/store/instance-name#3/*.IDX		 Y
Agent Store (health check agent) /opt/jp1pc/agt0/store/*.DB
/opt/jp1pc/agt0/store/*.IDX		 Y
Trace log Trace information of each service in the Performance Management program N/A#4 Y
Install log#5 Standard log of Hitachi Program Product Installer /etc/.hitachi/.hitachi.log
/etc/.hitachi/.hitachi.log{01|02|03|04|05}
/etc/.hitachi/.install.log
/etc/.hitachi/.install.log{01|02|03|04|05}		 N

Legend:
Y: Can be collected
N: Cannot be collected
N/A: Not applicable

#1
For details on the output format of the log files, see 13.5 Detecting problems by linking with the integrated system monitoring product.

#2
xxxx indicates the service key of each PFM - Agent or PFM - RM. For details on the service keys of each PFM - Agent or PFM - RM, see the naming rules in an appendix of the Job Management Partner 1/Performance Management Planning and Configuration Guide.

#3
For a PFM - Agent or PFM - RM monitoring an application program which can start multiple service sets on a single host, there is a directory for each instance.

#4
For details on the trace log destination directory, see 14.3.2 Log information files.

#5
Collect this information if the installation fails.

(3) PFM - Web Console information

You need to collect the information about PFM - Web Console listed below. In the case of a network error, you also need to collect applicable files from the connection-destination machine. The PFM - Web Console information that needs to be collected is shown below.

Type of information Outline Default file name Collected by the jpcwras command
Web server information Server log of Web server or Web container N/A Y
Operation status log#1 Message log output from PFM - Web Console /opt/jp1pcwebcon/log/jpcwtrace1#2.log Y
Message logs output from PFM - Web Console commands

For the jpcrpt command
/opt/jp1pcwebcon/log/ jpcrpt_process-ID-of-executed-command_log1#2.log

For the jpcrdef, jpcasrec, or jpcaspsv command
/opt/jp1pcwebcon/log/command-name_sub-command-name_log1#2.log

For the jpcmkkey command
/opt/jp1pcwebcon/log/jpcmkkey_log1#2.log

For all other commands
/opt/jp1pcwebcon/log/command-name_log1#2.log
 Y
File information List of PFM - Web Console installation files N/A Y
Configuration Info PFM - Web Console configuration information /opt/jp1pcwebcon/conf/*.*/opt/jp1pcwebcon/sample/conf/*.* Y

Legend:
Y: Can be collected
N/A: Not applicable

#1
For details on the output format of the operation status log, see the chapter describing the log information in the manual Job Management Partner 1/Performance Management Reference.

#2
The value 1 is appended to the file name of the operation status log.

(4) Operation information

You need to collect the following information about the operation being performed when an error occurs:

(5) Error information

You need to obtain the following error information:

(6) Other information

You also need to collect the following information:

[Contents][Back][Next]

[Trademarks]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.