10.4.2 Data to be collected from a UNIX environment
- Organization of this subsection
(1) Log information about the OS
The following table lists the log information about the OS that needs to be collected.
|
No. |
Type of information |
Overview |
Default file name |
Collection by the jpcras command |
|---|---|---|---|---|
|
1 |
System log |
syslog |
-- |
Y# |
|
2 |
Process information |
List of processes |
-- |
Y |
|
3 |
System file |
hosts file |
/etc/hosts |
Y |
|
4 |
services file |
/etc/services |
Y |
|
|
5 |
OS information |
Patch information |
-- |
Y |
|
6 |
Kernel information |
-- |
Y |
|
|
7 |
Version information |
-- |
Y |
|
|
8 |
Network status |
-- |
Y |
|
|
9 |
Environment variable |
-- |
Y |
|
|
10 |
Host name |
-- |
Y |
|
|
11 |
Dump information |
core file |
-- |
Y |
- Legend:
-
Y: Can be collected
--: Not applicable
- #
-
If the system is set to output to a path and file name that are not the default, the information cannot be collected. Use an appropriate method to collect the data.
(2) Information about Performance Management
The following table lists the Performance Management information that needs to be collected. In the case of a network connection error, you must also collect applicable files from the machine at the connection destination.
|
No. |
Type of information |
Overview |
Default file name |
Collection by the jpcras command |
|---|---|---|---|---|
|
1 |
Common message log |
Message log output from Performance Management (sequential file method) |
/opt/jp1pc/log/jpclog{01|02}#1 |
Y |
|
2 |
Message log output from Performance Management (wrap-around file method) |
/opt/jp1pc/log/jpclogw{01|02}#1 |
Y |
|
|
3 |
Configuration information |
Each configuration information file |
-- |
Y |
|
4 |
Output results of the jpctool service list command |
-- |
Y |
|
|
5 |
Version information |
Product version |
-- |
Y |
|
6 |
Historical information |
-- |
Y |
|
|
7 |
Database information |
Remote Monitor Store service |
|
Y |
|
8 |
Trace log |
Trace information for each service of the Performance Management program |
--#2 |
Y |
|
9 |
Agent log |
Normal log of the processing related to record collection by PFM - RM for Platform |
|
Y |
|
10 |
Work data |
Work data during performance data collection |
|
Y |
|
11 |
Install log#4 |
Standard log of Hitachi Program Product Installer |
|
N |
- Legend:
-
Y: Can be collected
N: Cannot be collected
--: Not applicable
- #1
-
For details about how to output log information to the log files, see the chapter that describes detection of Performance Management failures in the JP1/Performance Management User's Guide.
- #2
-
For details about the trace log storage directory, see 10.3.2 Log files and directories to check.
- #3
-
For details about the agent log output method and the storage directory, see 10.3.2 Log files and directories to check.
- #4
-
Collect this log information if installation fails.
(3) Operation information
You need the following information about the operation that was underway when the error occurred:
-
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
(4) Error information on screen displays
Obtain a hardcopy of the following information:
-
The window operation when the application error occurred
-
The messages output to the console, if the error occurred during command execution