12.2.1 JP1/IM - Manager log information
- Organization of this subsection
(1) Common message log
The common message log contains log information for the system administrator and reports system problems. The common message log reports a minimal amount of necessary problem information.
The common message log is output to the syslog file in UNIX, and to the Windows Event Log in Windows.
In SUSE Linux 15 or later, the common message log is not output to syslog by default. Instead, the common message log is output to a log file called a journal. In this manual, read syslog as journal.
In UNIX, the common message log is output to the following files:
-
/var/log/messages (in Linux)
- Important
-
In UNIX, a message whose output destination is the syslog file might not actually be output, depending on the behavior of the syslog file.
(2) Integrated trace log
The integrated trace log contains log information that is obtained by using the Hitachi Network Objectplaza Trace Library (HNTRLib2) to integrate the trace information that is output by individual programs into a single output file. The integrated trace log outputs more detailed messages than the common message log.
Product plugin log for JP1/IM - Agent is written to JP1/IM - Manager integrated trace log.
The default output destination of the integrated trace log is as follows:
- In Windows (32 bit):
-
system-drive\Program Files\Hitachi\HNTRLib2\spool\hntr2{1|2|3|4}.log
- In Windows (64 bit):
-
system-drive\Program Files\Hitachi\HNTRLib2\spool\hntr2{1|2|3|4}.log
or
system-drive\Program Files(x86)\Hitachi\HNTRLib2\spool\hntr2{1|2|3|4}.log
- In UNIX:
-
/var/opt/hitachi/HNTRLib2/spool/hntr2{1|2|3|4}.log
You can view the integrated trace log file from a text editor of your choice. The figure below shows an output example of the integrated trace log.
|
|
![[Figure]](GRAPHICS/CS240150.GIF)
The header information that is output to the integrated trace log file and the output items are explained below.
|
Header information |
Explanation |
|---|---|
|
OS information |
Information on the OS under which the Hitachi Network Objectplaza Trace Library (HNTRLib2) started. |
|
Host name |
The name of the host on which the Hitachi Network Objectplaza Trace Library (HNTRLib2) started. |
|
Time zone |
|
|
Integrated trace log function start time |
Time at which the Hitachi Network Objectplaza Trace Library (HNTRLib2) started. |
|
Output items |
Explanation |
|---|---|
|
Number (4 digits) |
Trace code serial number A number is assigned to each process that outputs a log. |
|
Date (10 bytes) |
Trace collection date: yyyy/mm/dd (year/month/day) |
|
Time (12 bytes) |
Trace collection time (local time): hh:mm:ss.sss (hour:minutes:seconds.milliseconds) |
|
AP name (16 bytes or shorter) |
Name that identifies an application (application identifier) The following AP names are output by JP1/IM - Manager:
The following AP names are output by JP1/IM - View:
|
|
pid |
Process ID assigned by the OS |
|
tid |
Thread ID for identifying a thread |
|
Message ID |
Message ID explained in the message output format. Message ID used by this product. |
|
Message text |
Message text that is output to the integrated trace log. Message text that is output from this product. |
The log time that is output to the integrated trace log is formatted according to the time zone of the process that output the log.
Consequently, if a user who has changed the environment variable TZ starts a service or executes a command, a time that is different from the time zone that is set in the OS may be output.
(3) Operation log
The operation log of JP1/IM - Manager contains log information about the login and logout history, including who attempted login or logout when and where, and whether the attempt was successful or failed. The operation log is used to find the cause of security problems such as unauthorized access, and to collect information necessary to ensure secure system operation. For details about the operation log, see Appendix K. Operation Log Output in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.
(4) Individual log
For authentication results using the secrets listed in initial secret and client secret, print the success or failure of authentication and its time in the secret authentication log file in the following format: Regarding initial secret and IM client secret, refer to 3.7 Initial secret and client secret in the JP1/Integrated Management 3 - Manager Overview and System Design Guide. The file has UTF-8 (no BOMs) character encoding, and the maximum file size is 60MB.
Time Message type Message
|
Output Item |
Description |
|---|---|
|
Time |
Print the time in "yyyy/MM/dd/hh:mm:ss.SSS" format. |
|
Message type |
Outputs one of the following message types:
|
|
Message |
Outputs one of the following messages:
For details about messages, see Chapter 2. List of Messages in the JP1/Integrated Management 3 - Manager Messages. |
The maximum number of characters that can be output in a single line is 4096 bytes. If it exceeds 4096 bytes, it will be wrapped and output. If the 4096th byte is in the middle of a multibyte character, the character is wrapped.
Also, the destination for the secret authentication log file is as follows:
- For Windows
-
For physical host: Manager-path\log\secretAuth\jddSecretAuth.log{.1|2|3}
For logical host: Shared-folder\jp1imm\log\secretAuth\jddSecretAuth.log{.1|2|3}
- For UNIX
-
For physical host:/var/opt/jp1imm/log/secretAuth/jddSecretAuth.log{.1|2|3}
For logical host: Shared-Directory/jp1imm/log/secretAuth/jddSecretAuth.log{.1|2|3}
(5) Log files and directory list
This subsection explains the types of log information that are output by JP1/IM, default file names, and directory names.
Note that the files explained here are output for product maintenance purposes. Therefore, there is no need for the user to view or modify these files. If a problem such as a system error occurs, the user may be asked to temporarily retain these files on site for the purpose of collecting data.
(a) In Windows
The tables below show the default log files and folders that are output by the Windows version of JP1/IM.
The Log type column lists the log types that are output by JP1/IM.
The Default file name and folder name column describes log file names as absolute paths when JP1/IM - Manager, JP1/IM - View, or JP1/Base is installed in the default mode. Default file name and folder name in a cluster operation system describes the log file names of shared folders as absolute paths.
The Maximum disk usage column shows the maximum disk space used by each log file. When there are multiple log files, the combined total is given.
The File-switching timing column shows how JP1/IM times output destination log file switching. When the file reaches the size shown in this column or when the event shown in this column occurs, the output destination is switched. If there are multiple log files and if the maximum disk usage is reached, files are overwritten, beginning with the ones that have the oldest update dates.
|
Log type |
Default file name and folder name |
Maximum disk usage |
File-switching timing |
|---|---|---|---|
|
Operation log |
Manager-path\log\operationlog\imm_operation{none|1|2...|16}.log#1 |
55 MB#1 |
5 MB#1#2 |
|
jimnodecount command log#3 |
Manager-path\log\nodecount\jimnodecount_cmd{1|2}.log |
20 MB |
10 MB |
#1: You can change the output destination, the number of files that can be saved, and the file size. For details, see Operation log definition file (imm_operationlog.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference. The number of bytes shown in the Maximum disk usage and File-switching timing columns are the values used when the number of files that can be saved and the file size are set to initial values.
#2: For details about the operation when switching the operation log file, see Appendix K.2 Storage format of operation log output in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.
#3: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.
#1: The file size may be dozens of kilobytes larger than this value.
#2: You can set this value to be from 65,536 bytes (64 kilobytes) to 104,857,600 bytes (100 megabytes), as described in Automated action environment definition file (action.conf.update) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
#3: You can set this value to be from 1 to 4,096 kilobytes, as described in Automated action environment definition file (action.conf.update) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
#4: This is the value when the size of the action information file is the default value (626 kilobytes). You can use the following estimation formula to estimate the maximum disk usage by this file. Each time an action is performed, the size increases by 5 kilobytes.
((action information file size ÷ 64 bytes) - 1) × 5 kilobytes
#5: The files are output to the jcochstat and jcoevtreport command trace logs on the physical host in a cluster operation system as well.
#6: You can change the file count and file size as described in the Correlation event generation environment definition file in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
#7: This file is used to output the memory information for inheriting data during correlation event generation, and therefore its size varies depending on the correlation event generation condition and the correlation-source event. For details about estimating the size of this file, see the JP1/IM - Manager release notes.
#8: This file is created when you start JP1/IM - Manager after enabling the response-waiting event management function.
#9: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.
Note: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.
Note: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.
|
Log type |
Default file name and folder name |
Maximum disk usage |
File-switching timing |
|---|---|---|---|
|
Intelligent Integrated Management Base service individual log |
Manager-path\log\imdd\jddmain\jddmain.log{.1-7} |
1 GB |
128 MB |
|
shared-folder\jp1imm\log\imdd\jddmain\jddmain.log{.1-7} |
|||
|
Definition file#1, node file history log |
Manager-path\log\imdd\jddmain\jimddDef.log{.1-10} |
80 MB |
8 MB |
|
shared-folder\jp1imm\log\imdd\jddmain\jimddDef.log{.1-10} |
|||
|
Manager-path\log\imdd\jddmain\jimddMaster.log{.1-30} |
240 MB |
8 MB |
|
|
shared-folder\jp1imm\log\imdd\jddmain\jimddMaster.log{.1-30} |
|||
|
jddsetaccessuser command trace log |
Manager-path\log\imdd\jddsetaccessuser\jddsetaccessuser.log{.1-6} |
70 MB |
10 MB |
|
shared-folder\jp1imm\log\imdd\jddsetaccessuser\jddsetaccessuser.log{.1-6} |
|||
|
Manager-path\log\imdd\jddsetaccessuser\jddsetaccessuser_exe{1|2|3}.log |
768 KB |
256 KB |
|
|
shared-folder\jp1imm\log\imdd\jddsetaccessuser\jddsetaccessuser_exe{1|2|3}.log |
|||
|
Manager-path\log\imdd\jddsetaccessuser\javalog0{1|2|3|4}.log |
1,024 KB |
At startup or 256 KB |
|
|
shared-folder\jp1imm\log\imdd\jddsetaccessuser\javalog0{1|2|3|4}.log |
|||
|
jddcreatetree command trace log |
Manager-path\log\imdd\jddcreatetree\jddcreatetree.log{.1-6} |
70 MB |
10 MB |
|
shared-folder\jp1imm\log\imdd\jddcreatetree\jddcreatetree.log{.1-6} |
|||
|
Manager-path\log\imdd\jddcreatetree\jddcreatetree_exe{1|2|3}.log |
768 KB |
256 KB |
|
|
shared-folder\jp1imm\log\imdd\jddcreatetree\jddcreatetree_exe{1|2|3}.log |
|||
|
Manager-path\imdd\jddcreatetree\javalog0{1|2|3|4}.log |
1,024 KB |
At startup or 256 KB |
|
|
shared-folder\jp1imm\log\imdd\jddcreatetree\javalog0{1|2|3|4}.log |
|||
|
jddupdatetree command trace log |
Manager-path\log\imdd\jddupdatetree\jddupdatetree.log{.1-6} |
70 MB |
10 MB |
|
shared-folder\jp1imm\log\imdd\jddupdatetree\jddupdatetree.log{.1-6} |
|||
|
Manager-path\log\imdd\jddupdatetree\jddupdatetree_exe{1|2|3}.log |
768 KB |
256 KB |
|
|
shared-folder\jp1imm\log\imdd\jddupdatetree\jddupdatetree_exe{1|2|3}.log |
|||
|
Manager-path\log\imdd\jddupdatetree\javalog0{1|2|3|4}.log |
1,024 KB |
256 KB |
|
|
shared-folder\jp1imm\log\imdd\jddupdatetree\javalog0{1|2|3|4}.log |
|||
|
jddsetproxyuser command trace log |
Manager-path\log\imdd\jddsetproxyuser\jddsetproxyuser.log{.1-6} |
70 MB |
10 MB |
|
shared-folder\jp1imm\log\imdd\jddsetproxyuser\jddsetproxyuser.log{.1-6} |
|||
|
Manager-path\log\imdd\jddsetproxyuser\jddsetproxyuser_exe{1|2|3}.log |
768 KB |
256 KB |
|
|
shared-folder\log\imdd\jddsetproxyuser\jddsetproxyuser_exe{1|2|3}.log |
|||
|
Manager-path\log\imdd\jddsetproxyuser\javalog0{1|2|3|4}.log |
1,024 KB |
256 KB |
|
|
shared-folder\log\imdd\jddsetproxyuser\javalog0{1|2|3|4}.log |
|||
|
jddupdatesuggestion command trace log |
Manager-path\log\imdd\jddupdatesuggestion\jddupdatesuggestion.log{.1-6} |
70MB |
10MB |
|
shared-folder\jp1imm\log\jddupdatesuggestion\jddupdatesuggestion.log{.1-6} |
|||
|
Manager-path\log\imdd\jddupdatesuggestion\jddupdatesuggestion_exe{1|2|3}.log |
768KB |
256KB |
|
|
shared-folder\log\imdd\jddupdatesuggestion\jddupdatesuggestion_exe{1|2|3}.log |
|||
|
Manager-path\log\imdd\jddupdatesuggestion\javalog0{1|2|3|4}.log |
1,024KB |
256KB |
|
|
shared-folder\log\imdd\jddupdatesuggestion\javalog0{1|2|3|4}.log |
|||
|
jddsetopinfo command trace log |
Manager-path\log\imdd\jddsetopinfo\jddsetopinfo.log{.1-6} |
70MB |
10MB |
|
shared-folder\jp1imm\log\jddsetopinfo\jddsetopinfo.log{.1-6} |
|||
|
Manager-path\log\imdd\jddsetopinfo\jddsetopinfo_exe{1|2|3}.log |
768KB |
256KB |
|
|
shared-folder\log\imdd\jddsetopinfo\jddsetopinfo_exe{1|2|3}.log |
|||
|
Manager-path\log\imdd\jddsetopinfo\javalog0{1|2|3|4}.log |
1,024KB |
256KB |
|
|
shared-folder\log\imdd\jddsetopinfo\javalog0{1|2|3|4}.log |
|||
|
jddupdatessomap command trace log |
Manager-path\log\imdd\jddupdatessomap\jddupdatessomap.log{.1-6} |
70MB |
10MB |
|
shared-folder\jp1imm\log\jddupdatessomap\jddupdatessomap.log{.1-6} |
|||
|
Manager-path\log\imdd\jddupdatessomap\jddupdatessomap_exe{1|2|3}.log |
768KB |
256KB |
|
|
shared-folder\log\imdd\jddupdatessomap\jddupdatessomap_exe{1|2|3}.log |
|||
|
Manager-path\log\imdd\jddupdatessomap\javalog0{1|2|3|4}.log |
1,024KB |
256KB |
|
|
shared-folder\log\imdd\jddupdatessomap\javalog0{1|2|3|4}.log |
|||
|
jimgndbsetup command trace log |
Manager-path\log\imgndb\jimgndbsetup{1|2}.log |
512KB |
256KB |
|
jimgndbunsetup command trace log |
Manager-path\log\imgndb\jimgndbunsetup{1|2}.log |
512KB |
256KB |
|
jimgndbstop command trace log |
Manager-path\log\imgndb\jimgndbstop{1-10}.log |
51,200KB |
5,120KB |
|
shared-folder\jp1imm\log\imgndb\jimgndbstop{1-10}.log |
|||
|
jimgndbstatus command trace log |
Manager-path\log\imgndb\jimgndbstatus{1-10}.log |
51,200KB |
5,120KB |
|
shared-folder\jp1imm\log\imgndb\jimgndbstatus{1-10}.log |
|||
|
Logs of the response action execution history file #4 |
Manager-path\log\suggestion\jddSuggestionHistory.log{.1-3} |
240MB |
60MB |
|
shared-folder\jp1imm\log\suggestion\jddSuggestionHistory.log{.1-3} |
|||
|
Secret authentication logfile |
Manager-path\log\secretAuth\jddSecretAuth.log{.1-3} |
240MB |
60MB |
|
shared-folder\jp1imm\log\secretAuth\jddSecretAuth.log{.1-3} |
|||
|
User-created plug-ins |
Manager-path\log\imdd\user-created-plug-in-name\user-created-plug-in.log{1-21}#3 |
220MB |
10MB |
|
shared-folder\JP1IMM\log\imdd\user-created-plug-in-name\user-created-plug-in.log{1-21}#3 |
|||
|
Other logs |
Manager-path\log\imdd\jddmain\jddmain_exe{1|2|3}.log |
768 KB |
256 KB |
|
shared-folder\jp1imm\log\imdd\jddmain\jddmain_exe{1|2|3}.log |
|||
|
Manager-path\log\imdd\jddmain\javalog0{1|2|3|4}.log |
1,024 KB |
At startup or 256 KB |
|
|
shared-folder\jp1imm\log\imdd\jddmain\javalog0{1|2|3|4}.log |
|||
|
Manager-path\log\imdd\jcoapi{1-50}.log |
500 MB |
10 MB |
|
|
shared-folder\jp1imm\log\imdd\jddmain\jcoapi{1-50}.log |
|||
|
Manager-path\log\imdd\jcoapiM{1-50}.log |
500 MB |
10 MB |
|
|
shared-folder\jp1imm\log\imdd\jddmain\jcoapiM{1-50}.log |
|||
|
Manager-path\log\imdd\component-name#2\component-name#2{1-21}.log |
220 MB |
10 MB |
|
|
shared-folder\log\imdd\component-name#2\component-name#2{1-21}.log |
Note: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.
- #1
-
The logs for the following definition files are output to the definition file log for the Intelligent Integrated Management Base:
System node definition file, category name definition file for IM management nodes, host name definition file, target host definition file for configuration collection, IM management node link definition file, IM management node link file, IM management node tree file, IM management node file
- #2
-
One of the following is displayed as the component name:
- jp1ajs
- jp1pfm
- jp1im
- #3
-
{1-21} indicates the file count. You can view the log files in a text editor of your choice.
- #4
-
The log is created when a response action is taken. Users can check the logs of response actions by themselves in order to examine the causes of failures, for example.
Note: When you use Windows, replace View-path\log\ with system-drive:\ProgramData\Hitachi\jp1\jp1_default\JP1CoView\log\.
#1: This log is a process-by-process trace log. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.
#2: The file size may be dozens of kilobytes larger than this value.
|
Log type |
Default file name and folder name |
Maximum disk usage |
File-switching timing |
|---|---|---|---|
|
IM Configuration Management trace log# |
View-path\log\jcfview\VIEW{1|2|3}.log |
30 MB |
10 MB |
|
Stack trace log# |
View-path\log\jcfjavalog{1|2}.log |
512 KB |
At startup or 256 KB |
|
Integrated trace log |
system-drive:\Program Files\Hitachi\HNTRLib2\spool\hntr2{1|2|3|4}.log |
1,024 KB |
256 KB |
Note: When you use Windows, replace View-path\log\ with system-drive:\ProgramData\Hitachi\jp1\jp1_default\JP1CoView\log\.
For Windows, the location represented by system-drive:\Program Files is determined at installation by an OS environment variable and might differ depending on the environment.
#: This log is a process-by-process trace log. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.
(b) In UNIX
The tables below show the default log files and folders that are output by the UNIX version of JP1/IM.
The Log type column lists the log types that are output by JP1/IM.
The Default file name and folder name column describes log file names as absolute paths when JP1/IM - Manager or JP1/Base is installed in the default mode. Default file name and folder name in a cluster operation system describes the log file names of shared folders as absolute paths.
The Maximum disk usage column shows the maximum disk space used by each log file. When there are multiple log files, the combined total is given.
The File-switching timing column shows how JP1/IM times output destination log file switching. When the file reaches the size shown in this column or when the event shown in this column occurs, the output destination is switched. If there are multiple log files and if the maximum disk usage is reached, files are overwritten, beginning with the ones that have the oldest update dates.
|
Log type |
Default file name and folder name |
Maximum disk usage |
File-switching timing |
|---|---|---|---|
|
Operation log |
/var/opt/jp1imm/log/operationlog/imm_operation{none|1|2...|16}.log#1 |
55 MB#1 |
5 MB#1#2 |
|
jimnodecount command log#3 |
/var/opt/jp1imm/log/nodecount/jimnodecount_cmd{1|2}.log |
20 MB |
10 MB |
#1: You can change the output destination, the number of files that can be saved, and the file size. For details, see Operation log definition file (imm_operationlog.conf) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference. The number of bytes shown in the Maximum disk usage and File-switching timing columns are the values used when the number of files that can be saved and the file size are set to initial values
#2: For details about the operation when switching the operation log file, see Appendix K.2 Storage format of operation log output in the JP1/Integrated Management 3 - Manager Overview and System Design Guide.
#3: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.
#1: This log is a process-by-process trace log. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.
#2: This log is created only in a cluster environment.
#3: The file size may be dozens of kilobytes larger than this value.
#4: You can set this value to be from 64 kilobytes to 100 megabytes, as described in Automated action environment definition file (action.conf.update) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
#5: You can set this value to be from 1 to 4,096 kilobytes as described in Automated action environment definition file (action.conf.update) in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
#6: This is the value when the size of the action information file is the default value (626 kilobytes). You can use the following estimation formula to estimate the maximum disk usage by this file. Each time an action is performed, the size increases by 5 kilobytes.
((action information file size ÷ 64 bytes) - 1) × 5 kilobytes
#7: The files are output to the jcochstat and jcochafmode command trace logs on the physical host in a cluster operation system as well.
#8: You can change the file count and file size as described in Correlation event generation environment definition file in Chapter 2. Definition Files in the JP1/Integrated Management 3 - Manager Command, Definition File and API Reference.
#9: This file is used to output the memory information for inheriting data during correlation event generation, and therefore its size varies depending on the correlation event generation condition and the correlation-source event. For details about estimating the size of this file, see the JP1/IM - Manager release notes.
#10: This file is created when you start JP1/IM - Manager after enabling the response-waiting event management function.
Note: This log is a process-by-process trace log. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.
Note: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.
|
Log type |
Default file name and directory name |
Maximum disk usage |
File-switching timing |
|---|---|---|---|
|
Intelligent Integrated Management Base service individual log |
/var/opt/jp1imm/log/imdd/jddmain/jddmain.log{.1-7} |
1 GB |
128 MB |
|
shared-directory/jp1imm/log/imdd/jddmain/jddmain.log{.1-7} |
|||
|
Definition file#1, node file history log |
/var/opt/jp1imm/log/imdd/jddmain/jimddDef.log{.1-10} |
80 MB |
8 MB |
|
shared-directory/jp1imm/log/imdd/jddmain/jimddDef.log{.1-10} |
|||
|
/var/opt/jp1imm/log/imdd/jddmain/jimddMaster.log{.1-30} |
240 MB |
8 MB |
|
|
shared-directory/jp1imm/log/imdd/jddmain/jimddMaster.log{.1-30} |
|||
|
jddsetaccessuser command trace log |
/var/opt/jp1imm/log/imdd/jddsetaccessuser/jddsetaccessuser.log{.1-6} |
70 MB |
10 MB |
|
shared-directory/jp1imm/log/imdd/jddsetaccessuser/jddsetaccessuser.log{.1-6} |
|||
|
/var/opt/jp1imm/log/imdd/jddsetaccessuser/jddsetaccessuser_exe{1|2|3}.log |
768 KB |
256 KB |
|
|
shared-directory/jp1imm/log/imdd/jddsetaccessuser/jddsetaccessuser_exe{1|2|3}.log |
|||
|
/var/opt/jp1imm/log/imdd/jddsetaccessuser/javalog0{1|2|3|4}.log |
1,024 KB |
At startup or 256 KB |
|
|
shared-directory/jp1imm/log/imdd/jddsetaccessuser/javalog0{1|2|3|4}.log |
|||
|
jddcreatetree command trace log |
/var/opt/jp1imm/log/imdd/jddcreatetree/jddcreatetree.log{.1-6} |
70 MB |
10 MB |
|
shared-directory/jp1imm/log/imdd/jddcreatetree/jddcreatetree.log{.1-6} |
|||
|
/var/opt/jp1imm/log/imdd/jddcreatetree/jddcreatetree_exe{1|2|3}.log |
768 KB |
256 KB |
|
|
shared-directory/jp1imm/log/imdd/jddcreatetree/jddcreatetree_exe{1|2|3}.log |
|||
|
/var/opt/jp1imm/log/imdd/jddcreatetree/javalog0{1|2|3|4}.log |
1,024 KB |
At startup or 256 KB |
|
|
shared-directory/jp1imm/log/imdd/jddcreatetree/javalog0{1|2|3|4}.log |
|||
|
jddupdatetree command trace log |
/var/opt/jp1imm/log/imdd/jddupdatetree/jddupdatetree.log{.1-6} |
70 MB |
10 MB |
|
shared-directory/jp1imm/log/imdd/jddupdatetree/jddupdatetree.log{.1-6} |
|||
|
/var/opt/jp1imm/log/imdd/jddupdatetree/jddupdatetree_exe{1|2|3}.log |
768 KB |
256 KB |
|
|
shared-directory/jp1imm/log/imdd/jddupdatetree/jddupdatetree_exe{1|2|3}.log |
|||
|
/var/opt/jp1imm/log/imdd/jddupdatetree/javalog0{1|2|3|4}.log |
1,024 KB |
256 KB |
|
|
shared-directory/jp1imm/log/imdd/jddupdatetree/javalog0{1|2|3|4}.log |
|||
|
jddproxyuser command trace log |
/var/opt/jp1imm/log/imdd/jddproxyuser/jddproxyuser.log{.1-6} |
70MB |
10MB |
|
shared-directory/jp1imm/log/imdd/jddproxyuser/jddproxyuser.log{.1-6} |
|||
|
/var/opt/jp1imm/log/imdd/jddproxyuser/jddproxyuser_exe{1|2|3}.log |
768KB |
256KB |
|
|
shared-directory/jp1imm/log/imdd/jddproxyuser/jddproxyuser_exe{1|2|3}.log |
|||
|
/var/opt/jp1imm/log/imdd/jddproxyuser/javalog0{1|2|3|4}.log |
1,024KB |
256KB |
|
|
shared-directory/jp1imm/log/imdd/jddproxyuser/javalog0{1|2|3|4}.log |
|||
|
jimgndbsetup command trace log |
/var/opt/jp1imm/log/imgndb/jimgndbsetup{1|2}.log |
512KB |
256KB |
|
jimgndbunsetup command trace log |
/var/opt/jp1imm/log/imgndb/jimgndbunsetup{1|2}.log |
512KB |
256KB |
|
jimgndbstop command trace log |
/var/opt/jp1imm/log/imgndb/jimgndbstop{1-10}.log |
51,200KB |
5,120KB |
|
shared- directory /jp1imm/log/imgndb/jimgndbstop{1-10}.log |
|||
|
jimgndbstatus command trace log |
/var/opt/jp1imm/log/imgndb/jimgndbstatus{1-10}.log |
51,200KB |
5,120KB |
|
shared- directory /jp1imm/log/imgndb/jimgndbstatus{1-10}.log |
|||
|
Logs of the response action execution history file#4 |
/var/opt/jp1imm/log/suggestion/jddSuggestionHistory.log{.1-3} |
240MB |
60MB |
|
shared-directory/jp1imm/log/suggestion/jddSuggestionHistory.log{.1-3} |
|||
|
Secret authentication logfile |
var/opt/jp1imm/log/secretAuth/jddSecretAuth.log{.1-3} |
240MB |
60MB |
|
shared-directory/jp1imm/log/secretAuth/jddSecretAuth.log{.1-3} |
|||
|
User-created plug-ins |
/var/opt/jp1imm/log/imdd/user-created-plug-in-name/user-created-plug-in.log{1-21}#3 |
220MB |
10MB |
|
shared-directory/jp1imm/log/imdd/user-created-plug-in-name/user-created-plug-in.log{1-21}#3 |
|||
|
Other logs |
/var/opt/jp1imm/log/imdd/jddmain/jddmain_exe{1|2|3}.log |
768 KB |
256 KB |
|
shared-directory/jp1imm/log/imdd/jddmain/jddmain_exe{1|2|3}.log |
|||
|
/var/opt/jp1imm/log/imdd/jddmain/javalog0{1|2|3|4}.log |
1,024 KB |
At startup or 256 KB |
|
|
shared-directory/jp1imm/log/imdd/jddmain/javalog0{1|2|3|4}.log |
|||
|
/var/opt/jp1imm/log/imdd/jcoapi{1-50}.log |
500 MB |
10 MB |
|
|
shared-directory/jp1imm/log/imdd/jddmain/jcoapi{1-50}.log |
|||
|
/var/opt/jp1imm/log/imdd/jcoapiM{1-50}.log |
500 MB |
10 MB |
|
|
shared-directory/jp1imm/log/imdd/jddmain/jcoapiM{1-50}.log |
|||
|
/var/opt/jp1imm/log/imdd/component-name#2/component-name#2{1-21}.log |
220MB |
10MB |
|
|
shared-directory/jp1imm/log/imdd/component-name#2/component-name#2{1-21}.log |
Note: The logs above are process-by-process trace logs. The process-by-process trace log is the log information that is output by each function of JP1/IM. It is output to a different log file depending on the function that is being used. Since the process-by-process trace log contains product information, its content is not made public.
#1: The logs for the following definition files are output to the definition file log for the Intelligent Integrated Management Base:
System node definition file, category name definition file for IM management nodes, host name definition file, target host definition file for configuration collection, IM management node link definition file, IM management node link file, IM management node tree file, IM management node file
#2: One of the following is displayed as the component name:
-
jp1ajs
-
jp1pfm
-
jp1im
#3: {1-21} indicates the file count. You can view the log files in a text editor of your choice.
#4: The log is created when a response action is taken. Users can check the logs of response actions by themselves in order to examine the causes of failures, for example.
(6) Log of JP1/IM - Agent (JP1/IM - Agent management base)
(a) Public log
JP1/IM - Agent management base log for publishing is output.
- Upper limit of log size and number of planes
-
It is specified in JP1/IM - Agent management base definition file.
- Output destination
-
-
For Windows
Manager-path#\log\imdd\imagent\imbase\
Manager-path#\log\imdd\imagent\imbaseproxy\
#: For a cluster, replace it with "shared-folder\jp1imm"
-
For Linux
/var/opt#/jp1imm/log/imdd/imagent/imbase/
/var/opt#/jp1imm/log/imdd/imagent/imbaseproxy/
#: For a cluster, replace it with "shared-directory".
-
- File name
-
jima_message.log#1
jima_message-YYYY-MM-DDThh-mm-ss.sss.log#2
- #1
-
When the log reaches the specified size, "-YYYY-MM-DDThh-mm-ss.sss.log" is added to the log filename and the log is rotated.
- #2
-
Rename the output destination log file name to a new date and delete the oldest log file.
- Output format
-
Datetime PID Job-Identifier Message-ID Message
- Note
-
When the command is executed in response action, the contents of the standard output and standard error output of executed command is output to the public log of imagent. Therefore, when execution of command that outputs message is expected in response action, expand logging sectors and max. file size of public log as needed. Logging sectors and max. file size of public log can be specified in log.message.num and log.message.size in imagent configuration file.
(b) Configuration Log at Startup
The settings read by JP1/IM - Agent management base at startup are printed out.
- Upper limit of log size and number of planes
-
The log size and number of planes are fixed in the system. It cannot be changed by a user.
- Output destination
-
-
For Windows
Manager-path#\log\imdd\imagent\imbase\
Manager-path#\log\imdd\imagent\imbaseproxy\
#: For a cluster, replace it with "shared-folder\jp1imm"
-
For Linux
/var/opt#/jp1imm/log/imdd/imagent/imbase/
/var/opt#/jp1imm/log/imdd/imagent/imbaseproxy/
#: For a cluster, replace it with "shared-directory".
-
- File name
-
jima_setting.log#1
jima_setting-YYYY-MM-DDThh-mm-ss.sss.log#2
- #1
-
When the log reaches the specified size, "-YYYY-MM-DDThh-mm-ss.sss.log" is added to the log filename and the log is rotated.
- #2
-
Rename the output destination log file name to a new date and delete the oldest log file.
- Output format
-
Outputs a log that shows the date and time and the set value.