10.3.2 In UNIX
- Organization of this subsection
(1) OS system information
You need to collect the OS-related information listed in the table below. These types of information can be collected using data collection tools.
Information type |
Collected data |
File name#1 |
---|---|---|
Installed Hitachi product information |
/etc/.hitachi/pplistd/pplistd |
|
Hitachi PP Installer installation log file |
/etc/.hitachi/.install.log* |
|
Hitachi PP Installer uninstallation log file |
/etc/.hitachi/.uninstall.log* |
|
Common definition information |
Files under /opt/jp1/hcclibcnf/ |
|
JP1/IM - Manager (JP1/IM - Central Console) core analysis information (back trace) |
Analysis result from seraph /var/opt/jp1cons |
|
Analysis result from seraph shared-directory/jp1cons/log#2 |
|
|
JP1/IM - Manager (JP1/IM - Central Scope) core analysis information (back trace) |
Analysis result from seraph /var/opt/jp1scope |
|
Analysis result from seraph shared-directory/jp1scope/log#2 |
|
|
JP1/Base installation log file |
/tmp/HITACHI_JP1_INST_LOG/jp1base_inst{1|2|3|4|5}.log |
|
JP1/IM - Manager installation log file |
/tmp/HITACHI_JP1_INST_LOG/jp1imm_inst{1|2|3|4|5}.log |
|
File list |
|
|
|
|
|
Data collection date/time |
date execution result |
|
Disk information |
df -k execution result |
|
Machine's environment variable |
env execution result |
|
Host name settings that are set in the machine |
|
|
Status of shared memory for inter-process communication |
ipcs -ma execution result |
|
Host name for resolving network address |
jbsgethostbyname execution result |
|
jbsgethostbyname logical-host-name execution result#2 |
|
|
Health check |
jbshcstatus -debbug -a execution result |
|
jbshcstatus -debbug -a -h logical-host-name execution result#2 |
|
|
Process operation status of Event Service |
jevstat execution result |
|
Process operation status of items other than Event Service |
jbs_spmd_status execution result |
|
jbs_spmd_status -h logical-host-name execution result#2 |
|
|
Automated action execution result |
jcashowa execution result |
|
jcashowa -h logical-host-name execution result#2 |
|
|
Automated action function status |
jcastatus execution result |
|
jcastatus -h logical-host-name execution result#2 |
|
|
Automated action definition file content |
jcastatus -d execution result |
|
jcastatus -d -h logical-host-name execution result#2 |
|
|
Event Generation Service status |
jcoegsstatus execution result |
|
jcoegsstatus -h logical-host-name execution result#2 |
|
|
Process operation status |
jco_spmd_status execution result |
|
jco_spmd_status -h logical-host-name execution result#2 |
|
|
Data collection command execution result |
jim_log.sh command execution result |
|
NIC installation status |
netstat -i execution result |
|
Network statistical information |
netstat -na execution result |
|
List of users that are set in the machine |
/etc/passwd |
|
Process list |
ps -elfa execution result |
|
Service port settings that are set in the machine |
|
|
Memory information |
|
|
System diagnostic information |
|
|
Syslog (syslog) |
|
|
JP1/IM - Manager (JP1/IM - Central Console) core analysis information (back trace) output by the jcogencore command |
Analysis result from seraph /var/opt/jp1cons |
|
Analysis result from seraph shared-directory/jp1cons/log (core output by jcogencore)#2 |
|
|
OS version information |
uname -a execution result |
|
Kernel parameter information |
In Solaris:
In AIX:
In Linux:
|
In Solaris:
In AIX:
In Linux:
|
Page size information |
|
|
OS patch application information |
In Solaris 10:
In Solaris 11:
In AIX:
In Linux:
|
In Solaris 10
In Solaris 11
In AIX:
In Linux:
|
- #1: Indicates the name of the compressed file and uncompressed file after a data collection tool is used (with the compressed file described first, followed by the uncompressed file).
-
The compressed file is created in .tar.Z format for Windows, Solaris, and AIX, and created in .tar.gz format for Linux.
For details about the internal directory configuration of the compressed file, see jim_log.sh (UNIX only) (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
#2: Can be collected when data in a logical host (cluster) environment is being collected.
(2) JP1 information
You need to collect the JP1-related information listed in the table below. These types of information can be collected using a data collection tool. If a network connection problem has occurred, you must also collect files from the machine at the connection destination.
Information type |
Collected data |
File name#1 |
|
---|---|---|---|
Common to JP1/IM and JP1/Base |
Integrated trace log |
All files under /var/opt/hitachi/HNTRLib2/spool/ |
|
JP1/IM - Manager (common to components) |
Patch application history |
/opt/jp1imm/patch_history |
|
Patch log information |
/opt/jp1imm/update.log |
|
|
JP1/IM - Manager (JP1/IM - Central Console) |
Automatic startup and automatic termination script |
Files under /etc/opt/jp1cons/ |
|
Settings and defintion file |
Files under /etc/opt/jp1cons/conf/ |
|
|
Files under shared-directory/jp1cons/conf/#2 |
|
||
Common definition information |
Files under /etc/opt/jp1cons/default/ |
|
|
Log file |
Files under /var/opt/jp1cons/log/ |
|
|
Files under shared-directory/jp1cons/log/#2 |
|
||
File for accumulated response-waiting events#3 |
Files under /var/opt/jp1cons/log/response/ |
|
|
Files under shared-directory/jp1cons/log/response/ |
|
||
Core analysis information (CAR file) output by the jcogencore command |
car command result /var/opt/jp1cons/log (core output by jcogencore) |
|
|
car command result shared-directory/jp1cons/log (core output by jcogencore)#2 |
|
||
Core analysis information (CAR file) |
car command result /var/opt/jp1cons/log |
|
|
car command result shared-directory/jp1cons/log#2 |
|
||
Correlation event generation history file |
Files under /var/opt/jp1cons/operation/evgen/ |
|
|
shared-directory/jp1cons/operation/evgen#2 |
|
||
JP1/IM - Manager (JP1/IM - Central Scope) |
Settings and definition file |
Files under /etc/opt/jp1scope/conf/ |
|
Files under shared-directory/jp1scope/conf/#2 |
|
||
Common definition information |
Files under /etc/opt/jp1scope/default/ |
|
|
Log file |
Files under /var/opt/jp1scope/log/ |
|
|
Files under shared-directory/jp1scope/log/#2 |
|
||
Core analysis information (CAR file) |
car command result /var/opt/jp1scope/log |
|
|
car command result shared-directory/jp1scope/log#2 |
|
||
Database information |
Files under /var/opt/jp1scope/database/ |
|
|
Files under shared-directory/jp1scope/database/#2 |
|
||
JP1/IM - Manager (IM Configuration Management) |
Settings and defintion files |
Files under /etc/opt/jp1imm/conf/imcf/ |
|
Files under shared-directory/jp1imm/conf/imcf/#2 |
|
||
Common definition information |
Files under /etc/opt/jp1imm/default/imcf/ |
|
|
Log file |
Files under /var/opt/jp1imm/log/imcf/ |
|
|
Files under shared-directory/jp1imm/log/imcf/#2 |
|
||
Core analysis information (CAR file) |
car command result /var/opt/jp1imm/log |
|
|
car command result shared-directory/jp1imm/log#2 |
|
||
JP1/Base |
Automatic startup and automatic termination script |
Files under /etc/opt/jp1base/ |
|
Settings and definition file |
Files under /etc/opt/jp1base/conf/ |
|
|
Files under shared-directory/jp1base/conf/#2 |
|
||
Common definition information |
Files under /etc/opt/jp1base/default/ |
|
|
Plug-in service settings file |
Files under /opt/jp1base/conf/plugin/ |
|
|
Patch application history |
/opt/jp1base/PatchInfo |
|
|
Patch log information |
/opt/jp1base/PatchLog |
|
|
Log file |
/var/opt/jp1base/log |
|
|
shared-directory/jp1base/log#2 |
|
||
Log and temporary file |
Files under /var/opt/jp1base/sys/tmp/ |
|
|
shared-directory/event#2 |
|
||
SES settings file |
|
|
|
Command execution history file |
Files under /var/opt/jp1base/log/COMMAND/ |
|
|
Files under shared-directory/jp1base /log/COMMAND/#2 |
|
||
Event database |
Files under /var/opt/jp1base/sys/event/servers/default/ |
|
|
shared-directory/event#2 |
|
- #1: Indicates the name of the compressed file and uncompressed file after a data collection tool is executed (with the compressed file described first, followed by the uncompressed file).
-
The compressed file is created in .tar.Z format for Solaris and AIX, and created in .tar.gz format for Linux.
For details about the internal directory configuration of the compressed file, see jim_log.sh (UNIX only) (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
#2: Can be collected when data in a logical host (cluster) environment is being collected.
#3: The file for accumulated response-waiting events is created when you enable the response-waiting event management function. You can prevent the jim_log.sh command from collecting this file by specifying a command option. For details, see 9.5.3 jim_log.sh (UNIX only).
(3) Operation content
You need the following types of information related to the operation that was being performed when the problem occurred:
-
Operation content details
-
Time of problem occurrence
-
Machine configuration (version of each OS, host name, and Central Console configuration)
-
Reproducibility
-
Login user name that was used to log in from JP1/IM - View
(4) Error information on the screen
Collect a hard copy of the following:
-
Error dialog box
(5) Information related to the Web version of JP1/IM - View
If a problem occurs while you are using the Web version of JP1/IM - View, you need to collect the following data.
View side
-
Java stack trace log
Before you can collect a Java stack trace log, you must set up the system such that the Java Console window can be opened. For details, see 4.16.4 Specifying display settings for the Java Console window in the Job Management Partner 1/Integrated Management - Manager Configuration Guide.
-
Java trace file of JavaTM Plug-in
- The Java trace file is located in the following directory:
-
system-drive:\Documents and Settings\login-user-name\Application Data\Sun\Java\Deployment\log\
Manager side
-
HTTP server error log
-
HTTP server access log