5.2.2 Precautions to Be Taken When Referencing the Hitachi Trace Common Library Format Log
This section describes the precautions to be taken when using the Hitachi Trace Common Library format log.
- Organization of this subsection
-
(1) Common precautions for multi and single processes
The common precautions for multi and single processes are as follows:
-
Do not edit the log file that has been output.
-
Do not lock files by using a function such as the text editor.
-
When setting the access rights for the output log file manually, assign the appropriate access rights.
-
Do not change the update time of the log file that has been output.
-
During trace output, do not delete log files or change file names. Delete the log files or change file names after stopping
all the trace output processes.
-
The management file xxxxxx.conf is output with the log file. Do not edit or delete this file while the trace output process is running.
-
Stop the trace output process before changing the log file size, number of log files, or other settings. When doing so, back
up or delete all log files and management files (xxxxxx.conf) under the log output directory (including subdirectories).
-
If you change the owner or owner group of the log files, also change the owner or owner group of the management file (xxxxxx.conf) to the same owner or owner group.
To Page Top
(2) Precautions when referencing multi processes Hitachi Trace Common Library
The precautions to be taken when referencing multi processes compliant Hitachi Trace Common Library format log file are as
follows:
-
The line feed code at the end of the message is CRLF, regardless of the OS being used.
-
In some cases you may need to delete the log files to enable changes in the log file size, number of files and mode options.
Before deleting the log files, stop all the processes that output trace.
-
Even if trace is output, there are cases when the update time of the log file is not updated. Therefore, you cannot judge
whether the trace is output based on the updated time of the file.
To Page Top
(3) Changes in the multi-process trace common library from the earlier versions
The log files of the multi-process trace common library have been changed from the earlier versions. The following table describes
the changes.
Table 5‒14: Differences with the earlier versions of the multi-process trace common library
|
Item
|
Application Server V9
|
Earlier than Application Server V9
|
|
File size
|
Variable (specified size might be exceeded)
|
Fixed (specified size)
|
|
File switching time
|
The files are switched at the following times:
-
When the file size exceeds the specified size
-
For time specified rotation
-
When the specified time is reached while the process is runing
|
When the file size + the size you want to output exceeds the specified size
|
|
Size when the files are switched
|
0 (All lines will be deleted)
|
Fixed (overwrite and store)
|
|
File switching operation (Wraparound method)
|
The trace data is overwritten and output from the beginning of the file (the information before wraparound remains as is)
|
The trace data is overwritten and output from the beginning of the file (the information before wraparound remains as it is)
|
|
File switching operation (Shift method)
|
All the lines are deleted and the trace data is output from the beginning of the file
|
--
|
|
Log file name numbering rules (Wraparound method)
|
xxxxxx1.log,
xxxxxx2.log,
xxxxxx3.log,
...
|
xxxxxx1.log,
xxxxxx2.log,
xxxxxx3.log,
...
|
|
Log file name numbering rules (Shift method)
|
xxxxxx.log,
xxxxxx1.log,
xxxxxx2.log,
...
|
--
|
|
End identifier
|
No (end of file)
|
Yes#
|
|
Management file
|
Created
|
Created
|
|
Determining the output file used when the process restarts
|
Time stamp
|
Management file, or time stamp
|
- Legend:
-
--: Not applicable.
- #
-
The end identifier used in the multi-process trace common library of the earlier versions is as follows:
EOF CRLF CRLF CRLF CRLF----------< End of Data >----------CRLF CRLF
EOF is the character (0x1A) that indicates the end of the trace data. CRLF indicates the linefeed (0x0D, 0x0A).
Table 5‒15: List of change files for the multi-process trace common library format
|
Classification of log
|
Log type
|
Log file and default file output destination
|
|
Common log
|
Audit log
|
Product-installation-directory/auditlog/audit?.log
|
|
Product-installation-directory/auditlog/rasexception?.log
|
|
Product-installation-directory/auditlog/rasmessage?.log
|
|
Functionality-specific public log
|
Performance, error analysis trace
|
Product-work-directory/ejb/J2EE-server-name/logs/RM/maintenance/mtd_RM-display-name_??.log
|
|
Product-work-directory/ejb/J2EE-server-name/logs/RM/maintenance/shq_RM-display-name_??.log
|
|
Product-work-directory/ejb/J2EE-server-name/logs/RM/maintenance/lin_RM-display-name_??.log
|
|
Product-installation-directory/CC/server/public/ejb/J2EE-server-namecsmxsec_trace?.log
|
|
Message log
|
Product-work-directory/ejb/J2EE-server-name/logs/CJW/cjwmessage?.log
|
|
Product-work-directory/ejb/J2EE-server-name/logs/CJR/cjrmessage?.log
|
|
Product-work-directory/ejb/J2EE-server-name/logs/WS/ <log_file_prefix>-j2ee-J2EE-server-name-<log_file_num>.log
|
|
Product-work-directory/ejb/J2EE-server-name/logs/WS/ c4webcl-default-?.log
|
|
Manager log
|
Integrated message log
|
Product-installation-directory/manager/log/message/mngmessage?.log
|
|
Integrated trace log
|
Product-installation-directory/manager/log/trace/mngtrace?.log
|
|
Console log
|
Product-installation-directory/manager/log/processConsole?.log
|
|
Internal setup tool log of the virtual functionality
|
Product-installation-directory/manager/setup/log/rasetup?.log
|
|
Server communication agent log
|
Product-installation-directory/sinagent/log/sinaviagent?.log
|
|
Server communication agent console log
|
Product-installation-directory/sinagent/log /processConsole?.log
|
To Page Top
