3.5.1 Matrix Server Administration Guide

Chapter 19: Other Matrix Maintenance 317

files are named matrix.log.1, matrix.log.2, and so on. You can also rotate the

matrix log file from the Management Console. Select the appropriate

server on the Servers window, right-click, and select Rotate Log. The

Management Console will display an error message if the rotate option

fails.

Add Your Own Messages to the Matrix Log File

You can use the mxlogger command to add your own messages to the

matrix.log file. For example, you may want to add messages about the

state of your applications. The mxlogger command has this syntax:

mxlogger -e entity -l level [-G|-L] log-text

The -e entity option specifies the type of message that you are adding.

entity can be

USER1, USER2, USER3, USER4, USER5, USER6, USER7, or USER8.

You will need to determine how you want to use these entities.

The -l level option specifies the severity of the message. level can be

ERROR, WARN, INFO, EVENT, FATAL, STATE, TRACE, or DEBUG.

The -G option specifies that the message is global; the -L option specifies

that it is local. The default is local.

If the log-text contains special characters or spaces, it must be enclosed in

quotation marks.

The following command adds a local message to the matrix.log file:

mxlogger -l info -e User2 “hello, world.”

The message appears like this in the log file:

Server Level Date/time Facility Entity Message

192.168.0.1 [Info] [2001-10-07 14:16:27] User USER2 hello, world

Audit Administrative Commands

Matrix Server provides an audit feature that can be used to log

administrative commands in the matrix log. The following types of

commands are audited:

• Login authentication for the PolyServe Management Console and mx

commands