A log file is created in the BASEDIR/smarts/local/logs directory for each Domain Manager application that is started with the -- output option. (Any Domain Manager application that is installed as a service automatically has --output in its invocation.) The log file is the primary tool for tracking the startup and progression of a Domain Manager application, and for resolving application and discovery errors.
Below figure shows through example the formatting structure of error (exception) messages that are written to a Domain Manager log file.
The first line of an error message identifies the following information:
-
Domain Manager software subsystem that reported the error
-
Severity level of the error:
-
F for Fatal
-
E for Error
-
W for Warning
-
N for Notice
-
I for Informational
-
D for Debug
-
-
Name of the error table from which the Domain Manager subsystem took the error
-
Name of the error
In the example error message, the reporting subsystem is ASL, for Adapter Scripting Language, the message severity level is Warning, the error table name is ERROR_RULE_SOURCE, and the error name is “While executing rule set.” The combination of an error table name and an error name uniquely identifies a particular error.
The remaining lines in a message, referred to as chained exceptions, provide more detail about the exception appearing in the top line. The last chained exception identifies the root cause of the error. In the example message, the root cause of the error is that the code was instructed to open a file that it could not find.
Below table identifies and briefly defines some of the Domain Manager subsystems.
Domain Manager subsystem |
Description |
---|---|
ASL |
Adapter scripting language subsystem. (Most Domain Manager Adapters are implemented in ASL code.) Throws errors that are detected by ASL code. |
DNS |
Network name translation subsystem |
DVST |
Device status polling subsystem |
DX |
Correlator subsystem |
ICF |
Domain Manager framework subsystem |
ICS |
Domain Manager service assurance subsystem |
MR |
Repository manager. Throws generic Repository errors; the Repository is the database that stores the discovered topology (inventory). |
OSA |
Operating system accessor |
RTLD |
Module loading. Throws errors due to configuration problems that cause the code to be unable to locate parts of itself. |
TOPO |
Topology |
<SYS> |
Not a Domain Manager subsystem; represents an operating system component that threw an error. |