This is the appliance alert log, recording key events of interest during appliance operation. The following are example alert log entries as they would appear in the BUI:
An info icon next to the Event ID means that extended information is available. Click the icon and this information will be displayed below the list of alerts.
The appliance can also be configured to send email, raise an SNMP trap, or perform other actions when particular alerts occur. This is configured in the Alerts section. All alerts appear in this log, regardless of whether they have actions configured for them.
The fault log records hardware and software faults. This is a useful reference when troubleshooting hardware failure, as timestamps are available for these hardware fault events.
The following are example fault log entries as they would appear in the BUI:
These faults will generate alert log entries, and so will use the alert reporting settings (such as sending email), if configured. Faults that require administrator attention will appear in Problems.
This is the operating system log, available to read via the appliance interfaces. This may be useful when troubleshooting complex issues, but should only be checked after first examining the alert and fault logs.
The following are example system log entries as they would appear in the BUI:
The audit log records user activity events, including login and logout to the BUI and CLI, and administrative actions. If session annotations are used (see Users), each audit entry should be noted with a reason.
The following are example audit log entries as they would appear in the BUI:
If Phone Home is used, this log will show communication events with Sun support.
The following are example phone home entry as it would appear in the BUI:
Use the Maintenance > Logs screen to navigate logs using list controls, and switch between logs using the local navigation buttons.
Logs can be viewed under the maintenance logs section of the CLI.
Use the show command to list available logs, and the timestamp of the last log entry:
caji:> maintenance logs caji:maintenance logs> show Logs: LOG ENTRIES LAST alert 2 2009-10-16 02:44:04 audit 42 2009-10-16 18:19:53 fltlog 2 2009-10-16 02:44:04 scrk 0 - system 100 2009-10-16 03:51:01
Up to 100 recent entries for each log are visible using the CLI.
Logs may be selected for viewing with the show command:
caji:maintenance logs> select audit show Entries: ENTRY TIME SUMMARY entry-000 2009-10-15 00:59:37 root, <console>, Enabled datalink:nge0 service entry-001 2009-10-15 00:59:39 root, <console>, Enabled interface:nge0 service entry-002 2009-10-15 01:00:39 root, <console>, User logged in entry-003 2009-10-15 01:41:44 root, <console>, Enabled nis service entry-004 2009-10-15 01:42:01 root, <console>, Imported storage pool "pool-0" entry-005 2009-10-15 17:56:30 root, <console>, User logged in entry-006 2009-10-15 17:56:53 root, deimos.sf.fishworks.com, User logged in via CLI entry-007 2009-10-15 18:00:21 root, deimos.sf.fishworks.com, User logged out of CLI entry-008 2009-10-15 18:14:47 root, <console>, Browser session timed out entry-009 2009-10-15 20:46:27 root, deimos.sf.fishworks.com, User logged in via CLI entry-010 2009-10-15 21:51:46 root, <console>, Rebooted appliance entry-011 2009-10-15 21:51:46 root, <console>, User logged out entry-012 2009-10-15 21:56:44 root, deimos.sf.fishworks.com, User logged in via CLI ...
Most recent entries are displayed at the bottom of the list.
All log entry details are available when selecting that entry and running show:
caji:maintenance logs> select audit caji:maintenance logs audit> select entry-000 show Properties: timestamp = 2009-10-15 00:59:37 user = root address = <console> summary = Enabled datalink:nge0 service annotation =
The "annotation" is the session annotation, which can be enabled when configuring users.