HP-UX SysFaultMgmt (System Fault Management) (SFM) Administrator Guide (762798-001, March 2014)

Tracing is a feature that enables you to log and report errors. You can use tracing to log information
about problems encountered while using Evweb. In this document, this information is referred to
as trace records. The trace records are stored in the /var/opt/sfm/log/sfm.log file. The
logs are written when SysFaultMgmt (System Fault Management) (SFM) is running. These logs
are Warning, informational, Milestone etc based on the kind of severity set by the user. You can
send the sfm.log file to the HP support center whenever you encounter a problem.
Following is a sample of the information logged in sfm.log.
01/04/06 06:50:08 EVMAN_COMMANDS ERROR 1069627450 1 Subscription with
this name already exist, Please choose different name and try again.
Table 19 describes the fields included in the sfm.log file.
Table 19 Entries in sfm.log
DescriptionField
Displays the date when the message was logged in the sfm.log file.Date
Displays the time when the message was logged in the sfm.log file.Time
Displays the name of the module or the providers that logged the message
in the sfm.log file, for example, EVWEB_CLI and FMDProviders.
Module Name
Displays the severity of the message logged in the sfm.log file.Severity
Displays the 10-digit process ID.Process ID
Displays the thread ID.Thread ID
Displays the text message.Message
To change the default location of the sfm.log file, you must configure the
/var/opt/sfm/conf/FMLoggerConfig.xml file.
You can enable, modify, and disable tracing for an Evweb session. A session is the duration
between a login and a logout. At the end of a session, tracing is automatically disabled. In an
active session, the trace level remains valid until you modify it.
Evweb provides the following trace levels in the descending order of severity:
• 1-Critical
• 2-Error
• 3-Warning
• 4-Information
Table 20 (page 78) describes the trace levels in Evweb.
Table 20 Trace Levels
DescriptionTrace Level
The system logs only those situations in Evweb that cause major failures.1-Critical
Example: The database server is not functioning properly or is down.
The system logs those situations that generate an error.2-Error
Example: There is more than one subscription name. Evweb accepts only
one subscription name.
Critical situations are also logged at the Error trace level.
The system logs situations that result in warning messages.3-Warning
Example: A warning is generated when the default setting is modified.
78 Administering indications and instances using HP SMH