A.2 List of files and directories (in UNIX)
Contents |
File name/directory name |
---|---|
Command storage directory |
/opt/jp1base/bin/ /opt/jp1base/bin/ext/#1 |
Environment setting directory#2 |
/etc/opt/jp1base/conf/ shared-directory/jp1base/conf/ |
Language type settings file |
/etc/opt/jp1base/conf/jp1bs_param.conf shared-directory/jp1base/conf/jp1bs_param.conf |
Configuration definition file |
/etc/opt/jp1base/conf/route/jbs_route.conf shared-directory/jp1base/conf/route/jbs_route.conf |
Startup process definition file |
|
Character code mapping definition file |
|
Language type mapping definition file |
|
JP1/IM function header file |
/opt/jp1base/include/JevApi.h |
Log directory#3 |
/var/opt/jp1base/log/ shared-directory/jp1base/log/ |
Directory for plug-in |
/opt/jp1base/plugin/ |
Directory for storing operating information |
/var/opt/jp1base/sys/OPI/ shared-directory/jp1base/sys/OPI/ |
Event DB storage directory#4 |
/var/opt/jp1base/sys/event/servers/#5 shared-directory/event/#5 |
jp1hosts2 information |
/var/opt/jp1base/sys/jp1hosts2/hostdb{0|1}.bin shared-directory/jp1base/sys/jp1hosts2/hostdb{0|1}.bin |
Log and temporary directory#3 |
/var/opt/jp1base/sys/tmp/event/servers/#5 |
|
|
|
|
Tool directory |
/opt/jp1base/tools/ |
|
|
|
|
|
|
Integrated trace log directory |
/var/opt/hitachi/HNTRLib2/spool/ |
IT Report Utility (system information collection tool) folder |
|
Forwarding suppression status management directory |
/etc/opt/jp1base/conf/event/servers/default/suppress#5 |
Forwarding suppression information directory for each agent |
/etc/opt/jp1base/conf/event/servers/default/suppress/agent-host-name #5 |
Auto-scaling linkage script directory#2 |
/opt/jp1base/tools/cloud/ |
|
|
|
|
|
|
|
|
Common definition information backup file output directory |
/tmp/JP1_COMDEF/ |
|
|
|
|
|
#1: This is created for Linux.
#2: For details on definition files, see A.2(1) List of definition files (in UNIX).
#3: For details on log files, see A.2(2) List of log files (in UNIX).
#4: For details on event database file name, see 2.3.2 Event database.
#5: If you specify a different path in the event server index file (index), the log will be stored in a different directory.
- Organization of this subsection
(1) List of definition files (in UNIX)
Function |
File name/directory name |
---|---|
Event service |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Event conversion |
|
|
|
|
|
Event service definition information collection and distribution |
|
|
|
|
|
User management |
|
|
|
|
|
Health check function |
|
|
|
|
|
Plugin service |
|
Operation log output function |
|
Process management |
|
|
|
Communication settings |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Local action function |
|
|
|
|
|
Collection of JP1/Base setup information in a single operation |
|
Configuration management functionality |
|
Auto-scaling linkage scripts |
|
|
|
Destination communications port specification function#3 |
|
|
#1: If you specify a different path in the event server index file (index), the log will be stored in a different directory.
#2: This file does not exist unless definition information distribution is used.
#3: This file only exists in Linux.
(2) List of log files (in UNIX)
The table below lists the log files that JP1/Base outputs by default.
- Important
-
JP1/Base also outputs some internal log files required for program maintenance. There is no need for users to reference or modify these internal log files. You might need to keep these files temporarily for data collection purposes if a system error occurs.
Log type indicates the type of log to which JP1/Base outputs data.
File name/directory name indicates the full path of the log file name when JP1/Base is installed using the default settings, and the log file name when JP1/Base is used in a cluster system.
Max. disk space indicates the maximum space the log file uses on a disk. If there are multiple log files, this column indicates the total.
File changing timing indicates when JP1/Base switches the output log files. Output destinations are changed when the indicated file size is reached or when the indicated event occurs. If there is only one log file, file changing causes that log file to be overwritten. If there are multiple log files and the maximum disk space has been reached, the file with the oldest update date is overwritten.
Log type |
File name/directory name |
Max. disk space |
File changing timing |
---|---|---|---|
JP1/Base startup log |
|
128 KB |
When the command is executed |
JP1/Base shutdown log |
|
128 KB |
When the command is executed |
Process management log |
|
384 KB |
128 KB |
|
384 KB |
128 KB |
|
Authentication server log |
|
5 MB |
640 KB |
|
5 MB |
640 KB |
|
|
5 MB |
640 KB |
|
Log of the authentication server setting command |
|
5 MB |
640 KB |
|
1.2 GB#2 |
None |
|
|
2 MB#2 |
None |
|
|
1 KB |
When the command is executed |
|
|
1.2 GB#2 |
None |
|
|
2 MB#2 |
None |
|
|
1 KB |
When the command is executed |
|
Common definition information log |
|
128 KB |
64 KB |
Log of jp1hosts information command |
|
128 KB |
64 KB |
User mapping command log |
|
128 KB |
64 KB |
Remote command log#1 |
|
20 MB |
2.5 MB |
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
|
20 MB |
2.5 MB |
|
Plug-in service log |
|
5 MB |
640 KB |
|
50 MB |
640 KB |
|
|
5 MB |
640 KB |
|
|
5 MB |
640 KB |
|
|
5 MB |
640 KB |
|
|
5 MB |
640 KB |
|
|
5 MB |
640 KB |
|
|
2,048 KB |
256 KB |
|
|
5 MB |
640 KB |
|
|
2,048 KB |
256 KB |
|
Installation log |
|
128 KB |
At installation |
|
10 MB |
2 MB |
|
|
10 MB |
2 MB |
|
|
50 KB |
10 KB |
|
|
50 KB |
10 KB |
|
|
1 MB |
At startup of Hitachi Program Product Installer |
|
|
4 MB |
If 1 MB is exceeded when installation is executed |
|
|
10 MB |
At installation |
|
|
4 MB |
If 1 MB is exceeded when installation is executed |
|
Setup log |
|
-- |
None#15 |
Configuration management log#1 |
|
20 MB |
4 MB |
Log of the health check function (local host monitoring) |
|
50 MB |
6.25 MB |
Log of the health check function (remote host monitoring) |
|
50 MB |
6.25 MB |
Log of the health check commands |
|
50 MB |
6.25 MB |
Log of the health check API |
|
50 MB |
6.25 MB |
Log of the command for deleting shared memory used by the health check function |
|
50 MB |
6.25 MB |
Operation log |
|
68 MB#4 |
1,024 KB#4#5 |
Trace log for the event setting, centralized management, and acquisition command |
|
192 KB |
When the command is executed |
Trace log for event setting, centralized management, and distribution command |
|
192 KB |
When the command is executed |
Trace log of the event service |
|
12.5 MB#7 |
When the event service starts |
|
5 MB#7 |
When the event service starts |
|
Transfer error log of the event service |
|
5 MB#7 |
When the event service starts |
Error log of the event service |
|
2,500 KB#7 |
When the event service starts |
Log of the event service API. |
|
5 MB#8 |
1 MB#8 |
Log of the event service |
|
5 MB |
1 MB |
Error information generated during communication between the event registration/reception process and the event service |
|
1 KB |
1 KB |
Error log of the log file trap |
|
A few hundred bytes#9 |
When the log file trap starts |
Log of the log file trap |
|
5 MB#10 |
1 MB#10 |
Log-file trap startup execution results log |
|
3 MB |
1 MB |
Remote monitoring log (log-file trap) |
|
5 MB |
1 MB |
Trace log of the jbs_killall.cluster command#11 |
|
256 KB |
When the command is executed |
Trace log for inter-process communication |
|
10 MB |
2.5 MB |
|
10 MB |
2.5 MB |
|
|
10 MB |
2.5 MB |
|
|
10 MB |
2.5 MB |
|
|
10 MB |
2.5 MB |
|
Error log of the command for collecting operating information |
|
5 MB |
1 MB |
Log for the operating information API |
|
5 MB |
1 MB |
Log of the service management control |
|
10 MB |
2.5 MB |
Trace log of the service management control |
|
10 MB |
2.5 MB |
Log of the service management control API |
|
10 MB |
2.5 MB |
Local action execution log |
|
1,024 KB#12 |
256 KB#12 |
Local action log |
|
2,048 KB |
256 KB |
|
2,048 KB |
256 KB |
|
|
2,048 KB |
256 KB |
|
JP1/Base administrator settings command log |
|
128 KB |
64 KB |
JP1/Base communications base log |
|
5 MB |
1 MB |
Individual log for the setup information collection command |
|
2 MB |
1 MB |
Log for recording starting and stopping of forwarding suppression |
|
128 KB |
64 KB |
Trace log for the event-forwarding suppression command |
|
5 MB |
1 MB |
Log of the command for the destination communications port settings#16 |
|
6MB |
1MB |
#1: Log file for JP1/IM - Manager
#2: You can use the jcocmddef command of JP1/IM - Manager with the -record option specified to change this to a value within the range below.
-
If the number of the records is 1 (-record 1)
DAT file: 7 KB, K01 file: 4 KB
-
If the number of records is 20,000 (the default setting)
DAT file: 125 MB, K01 file: 200 KB
-
If the number of the records is 196,600 (-record 196600)
DAT file: 1.2 GB, K01 file: 2 MB
#3: Indicates a jbsplugincom process identification number.
#4: You can use the operation log definition file (jp1bs_baselog_setup.conf) to change the number of files and the maximum disk space. For details on the range of specifiable values, see I.5 Settings for outputting operation logs.
#5: You can use the operation log definition file (jp1bs_baselog_setup.conf) to specify whether to automatically change files at JP1/Base startup.
#6: If you specify a different path in the event server index file (index), the log will be stored in a different directory.
#7: You can change the number of files and the maximum disk space using the event server settings file (conf). For details on the range of specifiable values, see Event server settings file in 16. Definition Files.
#8: You can use the API settings (api) file to change the number of files and the maximum disk space. For details on the range of specifiable values, see API settings file in 16. Definition Files.
#9: A file is created when the log file trapping function starts, and is deleted when the function terminates normally. If an error occurs, the file remains when the function terminates. If the log file trapping function generates frequent errors, there will be a large number of error files. Therefore, you need to delete unnecessary error files.
#10: You can change the number of files and the maximum disk space they occupy in the log information definition file (jevlogd.conf). For details on the range of specifiable values, see Log information definition file in 16. Definition Files.
#11: A log file output when the jbs_killall.cluster command executes in a cluster system.
#12: You can use the common definition settings file (local action function) to change the number of files and the maximum disk space. For details on the range of specifiable values, see Common definition settings file (local action function) in 16. Definition Files.
#13: Logs are output in HNTRLib2 format (multi-process trace).
#14: When deleting this log data, also delete the mmap directory at the output destination.
#15: Log data is output only when an environment is configured, for example, at the time of installation.
#16: Log data is only output in Linux.