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

installation-folder-for-the-Device-Manager-server\Server\config\log-

ger.properties

• In Linux:

installation-directory-for-the-Device-Manager-server/Server/config/

logger.properties

This property file contains a set of directives that configure the Device Manager server's logging

module, including the names, locations and verbosity level of the various operation and error log

files. You can also use this file to configure trace logging for debugging and diagnostic purposes.

The properties logger.loglevel, logger.MaxBackupIndex, and logger.MaxFileSize are

applied to the following files: access.log, cim_access.log, error.log, service.log,

stdout.log, stderr.log, statuscheck.log, trace.log, CIMOMTrace.log, and

SMISClientTrace.log.

The properties logger.hbase.loglevel, logger.hbase.MaxBackupIndex, and

logger.hbase.MaxFileSize are applied to the following files: HDvMtracen.log,

HDvMGuiTracen.log, and HDvMGuiMessagen.log.

The n in the file name indicates the backup generation number of the file.

The Windows event log is viewable in the Event Viewer. The default syslog is specified in /etc/

syslog.conf

logger.loglevel

Specify the verbosity level for the trace.log, error.log, CIMOMTrace.log, and

SMISClientTrace.log.

The values accepted in this field are (in decreasing order of detail): DEBUG, INFO, WARN, ERROR,

and FATAL. If this property is set to the default, entries whose verbosity level is either INFO, WARN,

ERROR, or FATAL are written into the trace.log. In this case, entries whose verbosity level is DEBUG

are not written into the logs.

Default: INFO

logger.MaxBackupIndex

Specify the maximum number of backups for the access.log, cim_access.log, error.log,

service.log, stdout.log, stderr.log, statuscheck.log, trace.log, CIMOMTrace.log,

and SMISClientTrace.log.

When a log file reaches its maximum size (as specified in the logger.MaxFileSize property), the

file is renamed and a counter is added into the file name (for example, access.log.1). As more

backup log files are created, their counters or version suffixes are incremented (for example,

access.log.1 becomes access.log.2), 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.

Specifiable values are from 1 to 20.

Default: 10