Hitachi

JP1 Version 12 JP1/Performance Management User's Guide


17.5.2 Data to be collected in the event of trouble (in UNIX)

Organization of this subsection

(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

System information

--

Y

Y

Patch information

--

Y

Y

Kernel information

--

Y

Y

Version information

--

Y

Y

Network status

--

Y

Y

Environment variables

--

Y

Y

Host name

--

Y

Y

Firewall information(Linux)

--

Y

N

Dump information

core file#4

--

Y#5

N

Legend:

Y: Can be collected

N: Cannot be collected

--: There is no default file.

#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.

#5

Dump information is not collected by the jpcras command if systemd-coredump is enabled in Linux. You can manually collect dump information of the Performance Management stored in the following directory.

/var/lib/system/coredump/

(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

Common message log (logical host use)

Message log output from Performance Management (sequential file method)

environment-directory/jp1pc/log/jpclog{01|02}#1

Y

Message log output from Performance Management (wrap-around file method)

environment-directory/jp1pc/log/jpclogw{01|02}#1

Y

Configuration information

Each configuration information file

  • Files under /opt/jp1pc

  • Files under /opt/jp1pc/sys

  • Files under environment-directory/jp1pc

  • Files under environment-directory/jp1pc/sys

  • Files under environment-directory

Y

Database information

Name Server

  • environment-directory/jp1pc/mgr/namesvr/*.DB

  • environment-directory/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#7

Agent Store and Remote Monitor Store

Store database 1.0:
  • /opt/jp1pc/xxxx#2/store/instance-name#3/*.DB

  • /opt/jp1pc/xxxx#2/store/instance-name#3/*.IDX

Store database 2.0:
  • /opt/jp1pc/xxxx#2/store/instance-name#3/*.DB

  • /opt/jp1pc/xxxx#2/store/instance-name#3/*.IDX

  • /opt/jp1pc/xxxx#2/store/instance-name#3/STPD\*

  • /opt/jp1pc/xxxx#2/store/instance-name#3/STPI\*

  • /opt/jp1pc/xxxx#2/store/instance-name#3/STPL\*

Y#7

Agent Store (health check agent)

Store database 1.0:
  • /opt/jp1pc/agt0/store/*.DB

  • /opt/jp1pc/agt0/store/*.IDX

Store database 2.0:
  • /opt/jp1pc/agt0/store/*.DB

  • /opt/jp1pc/agt0/store/*.IDX

  • /opt/jp1pc/agt0/store/STPD\*

  • /opt/jp1pc/agt0/store/STPI\*

  • /opt/jp1pc/agt0/store/STPL\*

Y#7

Database information (logical host use)

Name Server

  • environment-directory/jp1pc/mgr/namesvr/*.DB

  • environment-directory/jp1pc/mgr/namesvr/*.IDX

Y

Master Manager

  • environment-directory/jp1pc/mgr/manager/*.DB

  • environment-directory/jp1pc/mgr/manager/*.IDX

Y

Master Store

  • environment-directory/jp1pc/mgr/store/*.DB

  • environment-directory/jp1pc/mgr/store/*.IDX

Y

View Server

  • environment-directory/jp1pc/mgr/viewsvr/data/*

  • environment-directory/jp1pc/mgr/viewsvr/Reports/*

Y#7

Agent Store and Remote Monitor Store

Store database 1.0:Store database 1.0:
  • environment-directory/jp1pc/xxxx#2/store/instance-name#3/*.DB

  • environment-directory/jp1pc/xxxx#2/store/instance-name#3/*.IDX

Store database 2.0:
  • environment-directory/jp1pc/xxxx#2/store/instance-name#3/*.DB

  • environment-directory/jp1pc/xxxx#2/store/instance-name#3/*.IDX

  • environment-directory/jp1pc/xxxx#2/store/instance-name#3/STPD/*

  • environment-directory/jp1pc/xxxx#2/store/instance-name#3/STPI/*

  • environment-directory/jp1pc/xxxx#2/store/instance-name#3/STPL/*

Y#7

Agent Store (health check agent)

Store database 1.0:
  • environment-directory/jp1pc/agt0/store/*.DB

  • environment-directory/jp1pc/agt0/store/*.IDX

Store database 2.0:
  • environment-directory/jp1pc/agt0/store/*.DB

  • environment-directory/jp1pc/agt0/store/*.IDX

  • environment-directory/agt0/store/STPD/*

  • environment-directory/agt0/store/STPI/*

  • environment-directory/agt0/store/STPL/*

Y#7

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}

  • /opt/jp1pc/PSB/etc/.hitachi/.hitachi.log#6

  • /opt/jp1pc/PSB/etc/.hitachi/.install.log#6

N

Legend:

Y: Can be collected

N: Cannot be collected

N/A: There is no default file.

#1

For details on the output format of the log files, see 16.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 JP1/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 17.4.2 Details on log information.

#5

Collect this information if the installation fails.

#6

Collect this file when installation has failed but the file exists.

#7

Collected only when a directory name, a service key, or the all or data option is specified. If the option is omitted, the file is not collected.

(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/jpcwtracelog-file-number#2.log

Y

Message logs output from PFM - Web Console commands

For the jpcrpt command (one-execution-per-log recording method)#3

/opt/jp1pcwebcon/log/jpcrpt_process-ID-of-executed-command_log-file-number#2.log

For the jpcrpt command (multiple-executions-per-log recording method)#3

/opt/jp1pcwebcon/log/jpcrpt_loglog-file-number#2.log

For the jpcrdef, jpcasrec, jpcaspsv or jpcprocdef command

/opt/jp1pcwebcon/log/command-name_sub-command-name_log-file-number#2.log

For the jpcmkkey command

/opt/jp1pcwebcon/log/jpcmkkey_log-file-number#2.log

For all other commands

/opt/jp1pcwebcon/log/command-name_log-file-number#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

--: There is no default file.

#1

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

#2

The log file number is the number of output log files, starting from 1.

Operation status log output

The output size of the operation status log (excluding the log for the jpcrpt command) can be set by using logFileSize × logFileNumber in the initialization file (config.xml).

#3

For details about the log output format of the jpcrpt command, see 17.4.2(1)(a) Log output format of the jpcrpt command.

(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) Docker environment information (Linux)

If you are using Performance Management in a Linux Docker environment, you have to collect the following Docker environment information:

Type of information

Outline

Collected by the jpcras command

Docker environment information

Docker version

Y

Docker container list

Y

Process within the Docker container

Y

Docker container information

Y

Legend:

Y: Can be collected

(7) Podman environment information (Linux)

If you are using Performance Management in a Linux Podman environment, you have to collect the following Podman environment information:

Type of information

Outline

Collected by the jpcras command

Podman environment information

Podman version

Y

Podman container list

Y

Process within the Podman container

Y

Podman container information

Y

Legend:

Y: Can be collected

(8) Other Information

You also need to collect the following information:

To collect the Java VM thread dump:

  1. Execute the following command ten times at three-second intervals.

    # /opt/jp1pcwebcon/CPSB/CC/server/bin/cjdumpsv PFMWebConsole

    Note: Before you execute the command above, use the export command to set the following environment variables:

    Environment variable

    Settings

    CSCCFJ_SERVER_HOME

    /opt/jp1pcwebcon/CPSB/CC

    COSMINEXUS_PSB_HOME

    /opt/jp1pcwebcon/CPSB

  2. Execute the jpcwras command.

Note:

Because the operation of Java VM becomes unstable when collecting a thread dump, restart the PFM - Web Console service.