HP P9000 Command View Advanced Edition Suite Software 7.4.1-00 Administrator Guide (TB581-96334, April 2013)

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 its maximum size (as specified in the logger.hbase.MaxFileSize
property), the file is renamed and a counter is added into the file name (for example,
HDvMtrace2.log). As more backup log files are created, their counters or version suffixes are
incremented (for example, HDvMtrace2.log becomes HDvMtrace3.log), until the specified
number of backups have been created. After that, the oldest backup log file is deleted each time a
new backup is created.
Valid values are from 1 to 16.
Default: 10
Administrator Guide (Web Version) 361