10.4.2 In UNIX
- Organization of this subsection
(1) Checking the process status
The process names that are displayed when the ps command is executed are shown below. In UNIX, by using the data collection tool (jim_log.sh), you can collect the execution results of the ps command along with other data.
(a) JP1/IM - Manager
The table below shows the processes of JP1/IM - Manager. The value inside parentheses ( ) indicates the number of processes that execute simultaneously.
|
Parent process name |
Function |
Child process name |
Function |
|---|---|---|---|
|
jco_spmd (1)#1 |
Process management |
jcamain (1) |
Automatic Action Service (Process management display name: jcamain) |
|
evtcon (1)#1 |
Event Console Service (Process management display name: evtcon) |
||
|
evflow (1) |
Event Base Service (Process management display name: evflow) |
||
|
jcsmain (1) |
Central Scope Service#3 (Process management display name: jcsmain) |
||
|
jcfmain (1) |
IM Configuration Management Service#3 (Process management display name: jcfmain) |
||
|
evgen (2)#2, #4 |
Event Generation Service#3 (Process management display name: evgen) |
#1: The number of these processes may temporarily increase.
#2: The maximum number is 2, but the normal number is 1. The details are explained below.
-
Event Generation Service process core
-
This is a process that is temporarily generated when Event Service is connected. It is generated in the following cases:
![[Figure]](GRAPHICS/ZUENG030.GIF)
When Event Generation Service starts
When the event acquisition filter is updated
#3: In the default, this service does not run.
#4: This is the service that is used when the integrated monitoring database is not used.
When JP1/IM - Manager is running in a cluster system, the above processes are executed on each physical host and on each logical host. The number of processes that execute simultaneously can be obtained by multiplying the number of physical hosts and logical hosts that are running by the number of above processes. The processes that are running in a cluster system are displayed as follows when the ps command is executed (note that evtcon and evgen are not followed by a logical host name).
jco_spmd logical-host-name
evflow logical-host-name
jcamain logical-host-name
evtcon
evgen
jcsmain logical-host-name
jcfmain logical-host-name
In the table, a process whose parent process is jco_spmd is controlled by process management, and you can use the jco_spmd_status command to check the process status.
-
A display example during normal operations follows.
# jco_spmd_status
KAVB3690-I Processing to report the status of JP1_CONS has started.
Shows processes that are running.
Process name Process ID
evflow 3672
jcamain 4088
evtcon 4236
jcsmain#1 4846
jcfmain#2 4950
evgen#3 5624
KAVB3691-I All the processes have started.
#1: jcsmain is displayed only when the Central Scope is enabled.
#2: jcfmain is displayed only when the IM Configuration Management is enabled.
#3: evgen is displayed only when the Event Generation Service is enabled.
(2) Outputting a dump file for JP1/IM
(a) JP1/IM - Manager
You only need to output a dump file for JP1/IM - Manager when the health check function detects an abnormality in JP1/IM - Manager. Execute the jcogencore command as follows.
jcogencore
When you execute the jcogencore command, a message appears asking you to select the process from which to output a dump file. Select the process that is included in the message information issued by the health check function. If a dump file already exists, an overwrite confirmation message is displayed. If you choose not to overwrite the dump file, choose n and terminate the command. Next, save the dump file and then re-execute the jcogencore command.
For details about the jcogencore command, see jcogencore (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.
(3) Collecting information related to the Web version of JP1/IM - View
When a problem occurs in the Web version of JP1/IM - View, collect the following data in addition to the data described in this section.
View side
-
Java stack trace log
- The collection procedure follows.
-
1. Choose the Java Console window and enter v.
The Java stack trace log is output to the Java Console window.
2. Copy the log and manually paste it to a text file, for example.
3. Save the text file.
-
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\
- Important note
-
The Java trace file of JavaTM Plug-in is erased when JavaTM Plug-in restarts. Therefore, if a problem occurs, save the content of this file to another file before restarting.
Manager side
-
HTTP server error log
-
HTTP server access log
(4) Executing the data collection tool
This subsection describes execution of the data collection tool (jim_log.sh).
When you execute the jim_log.sh command, which is provided by JP1/IM - Manager, you can collect the data necessary for troubleshooting JP1/IM - Manager and JP1/Base on the same host.
Because the total volume of data collected by a data collection tool is massive, you need to estimate it before you execute the command and make sure the machine you are using has sufficient free space. For the volume of data that will be collected by the jim_log.bat command, see the JP1/IM - Manager release notes.
A tool execution example follows.
# /opt/jp1imm/tools/jim_log.sh -f data-storage-directory
When you execute the tool, the collected data is summarized in the tar format and output as compressed data.
(5) Checking the operation content
Check the content of the operation that was taking place when the problem occurred, and record it. The following types of information must be checked:
-
Operation content details
-
Time of problem occurrence
-
Reproducibility
-
Login user name that was used to log in from JP1/IM - View
-
Machine configuration (version of each OS, host name, and Central Console configuration)