N1 Provisioning Server 3.1, Blades Edition, System Administration Guide

Message Log File Format

All messages logged into the /var/adm/messages and the /var/adm/tspr.debug files are in a standard format. The following example is a typical message:

Nov 12 17:22:57 sp3 java[23033]: [ID 398540 user.info] TSPR [sev=crit] [fmid=1211] [MSG6718] FM Activate: Ready timeout expired.

Table 7–1 Message Log File Format


Message Element	Description
`Nov 12 17:22:57`	The date and timestamp of the message.
`sp3`	The name of the control plane server.
`java[23033]`	The unique ID of the Solaris process.
`[ID 398540`	The unique ID of the system log.
`user.info]`	The type of system log entry.
`TSPR`	The type of message. In the example, the message is an N1 Provisioning Server message.
`[sev=crit]`	Indicates the severity of the message. In the example, `crit` means this error message is critical. Other severity types are `warn`, `okay`, and `dbug`.
`[fmid=1211]`	Indicates the application ID that generated the message. In the example, the application is the farm manager for farm `1211`. The segment manager application ID is in the format `[smid=27003]`. The command-line tools application ID is in the format `[apps=26765]`.
`[MSG6718`]	The message ID assigned by the N1 Provisioning Server.
`FM Activate: Ready timeout expired`	The message itself.

When an error or exception occurs during execution, the name of the exception is logged as part of the message along with a description of the exception.