Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Performance Management User's Guide


17.5.1 Data to be collected in the event of trouble (in Windows)

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

Windows event log

N/A

Y

Y

Process information

List of processes

N/A

Y

Y

System file

hosts file

system-folder\system32\drivers\etc\hosts

Y

Y

services file

system-folder\system32\drivers\etc\service

Y

Y

OS information

System information

N/A

Y

Y

Network status

N/A

Y

Y

Host name

N/A

Y

Y

Windows Firewall information

N/A

Y

N

Dump information

(for Windows Server 2003)

Dr. Watson log files

system-drive\Documents and Settings\All Users\Application Data\Microsoft\DrWatson\drwtsn32.log#

system-drive\Documents and Settings\All Users\Application Data\Microsoft\DrWatson\user.dump#

Y

Y

Dump information

(for Windows Server 2008 or Windows Server 2012)

Log files regarding problem reports and solutions

output-destination-folder-for-user-mode-process-dump\program-name.process-ID.dmp

Example: jpcagtt.exe.2420.dmp

N

N

Legend:

Y: Can be collected

N: Cannot be collected

N/A: Not applicable

#

If your setup provides for output of log files to a different folder, be sure that you collect the data from the correct folder.

(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)

installation-folder\log\jpclog{01|02}#1

Y

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

installation-folder\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

installation-folder\mgr\namesvr\*.DB

installation-folder\mgr\namesvr\*.IDX

Y

Master Manager

installation-folder\mgr\manager\*.DB

installation-folder\mgr\manager\*.IDX

Y

Master Store

installation-folder\mgr\store\*.DB

installation-folder\mgr\store\*.IDX

Y

View Server

installation-folder\mgr\viewsvr\data\*

installation-folder\mgr\viewsvr\Reports\*

Y

Agent Store and Remote Monitor Store

installation-folder\xxxx#2\store\instance-name#3\*.DB

installation-folder\xxxx#2\store\instance-name#3\*.IDX

Y

Agent Store (health check agent)

installation-folder\agt0\store\*.DB

installation-folder\agt0\store\*.IDX

Y

Trace log

Trace information of each service in the Performance Management program

N/A#4

Y

Install log#5

Message log at the time of installation

%TEMP%#6\pfm_inst.log#7

system-folder\TEMP\HCDINST\*.LOG

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 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 service keys of each PFM - Agent or PFM - RM, see the description of 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 folder for each instance.

#4

For details on the trace log storage destination, see 17.4.2 Details on log information.

#5

Collect this information if the installation fails.

#6

%TEMP% indicates the folder that is set for the TEMP environment variable. To check the TEMP environment variable, execute the following command:

echo %TEMP%
#7

This is only applicable for Windows Server 2003.

(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 required 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

Registry information

Product registry information

N/A

Y

Operation status log#1

Message log output from PFM - Web Console

installation-folder\log\jpcwtracelog-file-number#2.log

Y

Message log output from a PFM - Web Console command

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

installation-folder\log\jpcrpt_process-ID-of-executed-command_log-file-number#2.log

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

installation-folder\log\jpcrpt_loglog-file-number#2.log

For the jpcrdef, jpcasrec, jpcaspsv or jpcprocdef command

installation-folder\log\command-name_sub-command-name_log-file-number#2.log

For the jpcmkkey command

installation-folder\log\jpcmkkey_log-file-number#2.log

For all other commands

installation-folder\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

installation-folder\config\*.*

installation-folder\sample\config\*.*

Y

PFM - Web Console log information

(Un)installer log file

installation-folder\log\pfmwebconinst.log#4

%TEMP%#5\pfmwebconinst.rtn#4

%TEMP%#5\pfmwebconuninst.log#4

%TEMP%#5\pfmwebconuninst.rtn#4

system-folder\TEMP\HCDINST\*.LOG

N

Legend:

Y: Can be collected

N: Cannot be collected

N/A: Not applicable

#1

For details on the output format of the operation status log, see the chapter explaining the log information in the manual Job Management Partner 1/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 x 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

In Windows Server 2003 only

#5

%TEMP% indicates the folder that is set for the TEMP environment variable. To check the TEMP environment variable, execute the following command:

echo %TEMP%

(4) Operation information

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

(5) Error information on window displays

Obtain printouts of the following:

(6) User mode process dump (Windows Server 2008 or Windows Server 2012)

You need to collect a user mode process dump if the OS is Windows Server 2008 or Windows Server 2012 and a Performance Management process stopped due to an application error.

(7) Problem reports (Windows Server 2008 or Windows Server 2012)

You need to collect problem reports if the OS is Windows Server 2008 or Windows Server 2012 and a Performance Management process stopped due to an application error.

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

    # installation-directory/CPSB/CC/web/bin/cjdumpweb PFMWebConsole

  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.