N1 Provisioning Server 3.1, Blades Edition, System Administration Guide

Error Message Overview

During the course of administering an Infrastructure Fabric (I-Fabric), you will encounter error messages. This chapter provides messages, descriptions, and actions required to solve a problem or to gather additional information before reporting a problem. You can locate messages in the log files.

The severity of error messages ranges from merely a minor debug message to a critical alert. All messages from N1 Provisioning Server software are logged in the /var/adm/tspr.debug log file. All messages from third-party components (for example, drivers) are logged in the /var/adm/messages log file.

As the message is written to the log file, the message is categorized as okay, debug, warning, or critical. The following example shows how it appears in the log:

Oct 30 00:16:47 sp4 java[ 506]: [ID 289794 user.info] TSPR [sev=okay] [apps=770034] TCPEventHandler:dispatch.

Note –

[sev=okay] denotes the message's severity.

N1 Provisioning Server software logs messages in two separate log files:

okay, warning, and critical messages with an error ID are logged in the /var/adm/messages log file.
Along with the okay, warning, and critical messages, the /var/adm/tspr.debug log file also includes the debug messages, which are used for debugging system failures.