HP XP7 Command View Advanced Edition Administrator Guide (Web Version) (TK981-96004, May 2014)

Default: 10
Related topics
• logger.MaxFileSize, page 328
logger.MaxFileSize
Specify the maximum size for the access.log, cim_access.log, error.log, service.log,
stdout.log, stderr.log, statuscheck.log, trace.log, CIMOMTrace.log, and
SMISClientTrace.log.
If the maximum size is exceeded, a new log file is created. Unless KB is specified for kilobytes or MB
for megabytes, the specified size is interpreted to mean bytes.
Specifiable range: from 512 KB to 32 MB
Default: 1 MB
logger.hbase.loglevel
Specify the verbosity level for each operation (trace) log file and error log file written by Common
Component. The log files are HDvMtracen.log, HDvMGuiTracen.log, and
HDvMGuiMessagen.log, where n is an integer that represents the backup number for the file.
Each logging event has its own importance level independent from its type (error, warning, and
information). The levels, in increasing order of importance, are: 30, 20, 10, and 0. The default logging
level for production systems is 20, which means that messages for logging event levels 20, 10, and
0 are written to HDvMtrace1.log, but messages for logging event level 30 are not.
Default: 20
logger.hbase.sysloglevel
Specify the verbosity level for the operation (trace) log data and error log data written to the event
log (in Windows) or to syslog (in Linux) by Common Component.
Each logged event has its own importance level independent from its type (error, warning, and
information). The levels, in increasing order of importance, are: 30, 20, 10 and 0. The default logging
level for production systems is 0, which means that only messages for the logging event level 0 are
written to the event log (in Windows) or to syslog (in Linux), but messages for the logging event level
30, 20, and 10 are not. The default value is recommended.
Default: 0
logger.hbase.MaxBackupIndex
Specify the maximum number of backups for each trace and error log file that is written by Common
Component. The log files are HDvMtracen.log, HDvMGuiTracen.log, and
HDvMGuiMessagen.log (the n in the file name indicates the backup generation number of the file).
When a log file reaches the size specified in the logger.hbase.MaxFileSize property, a new
log file is created with a counter added to the file name, for example HDvMtrace2.log. If the
number of log files reaches the value specified in this property, log files are overwritten starting from
the oldest file.
Valid values are from 1 to 16.
Device Manager server properties328