System Event Log

Top  Previous  Next

This software logs nearly all actions and polling results in an O/S-specific event log.  It passes the messages to the standard UNIX/LINUX syslog function or the Windows ReportEvent API, depending on what operating system you are using. Alternately you can add the -L function is added to the command-line and have your messages recorded into a file specified by the table below.

 

All log entries are made by opening, appending, and closing the file.  If the log file is busy, the software will sleep for 100 ms then retry up to 100 times before giving up and moving on. This insures that multiple instances of the software will not corrupt the log file.

 

O/S-Defined Event Log File Name

Operating System

-L Log file

LINUX

/var/log/smartmon-ux

SPARC Solaris

/var/log/smartmon-ux

X86 Solaris

/var/log/smartmon-ux

Apple OS X

/var/log/smartmon-ux

UNIXWare

/var/adm/smartmon-ux

IBM AIX

/var/adm/smartmon-ux

HP HP/UX

/var/adm/smartmon-ux

SGI IRIX

/var/adm/smartmon-ux

HP (DEC) Tru64

/var/adm/smartmon-ux

HP (DEC) OpenVMS

SMARTMON.LOG (in current directory)

Windows

smartmon-ux.log in the "current" directory when the program was invoked.

 

Note: If you invoke software from a batch (.BAT) file, you should CD to the  desired log file directory before you invoke the software.

 

If the program is running as a service, then the log file will be saved in the same directory where the program is installed.

 

Event Log Priority

Depending on the type of event, the software will classify log messages as Success, Information, Error, Critical, and Warning. These correspond to standard priorities supported by the UNIX/LINUX syslog.  (The Windows event logger does not differentiate between a critical error and a non-critical error).

 

Event Log Localization

If the -i flag is added to the command-line, all events will be prefaced by the date and time in the local language, provided your operating system also has localization enabled. Localization is supported on all operating systems, including Windows, if it is enabled. If you do not use the -i option, all messages will be prefaced by the date an time in US English format.

 

Sample event log entries (data sent with the -L flag)

Fri Mar 25 23:13:57 2005: ./smartmon-ux started

Fri Mar 25 23:13:57 2005: Discovered SEAGATE ST336706LC S/N "3FD010DD" on /dev/sdb (SMART enabled)(35003 MB)

Fri Mar 25 23:13:57 2005: /dev/sdb polled at Fri Mar 25 23:13:57 2005 Status:Passed

Fri Mar 25 23:14:07 2005: /dev/sdb polled at Fri Mar 25 23:14:07 2005 Status:Passed

 

Windows-Specific Event Log Information

SANTOOLs software utilizes the standard ReportEvent API for reporting events. They appear as uncategorized Application Log entries. The event source will always be "smartmon-ux".  Event IDs will be 8000 - 8003 which correspond, in order, to Success, Information, Warning, and Error.  The full text of the message will appear in the log, but there will be no redundant leading date/time information. This is because the operating system will assign the date/time as the event is posted.

 

One of the enhancements introduced in release 1.29 was that you can add hostname in order to specify logging events on a remote host.  You must, of course, have proper permissions. Hostname must be entered  in the Universal Naming Convention (UCE) format. This is also known as the Uniform Naming Convention, or just NETBIOS name. This should not be confused with the IP based-hostname.  Example: -LRemote \\MAILSERVER3.  You may also use the IP number, as in -LRemote 192.168.1.245

 

Firewall Restrictions

If you use the -LRemote function to send messages to a remote host, you must make sure that you open up UDP port #514 between the remote host that will receive the events, and the local system that is generating them via this software.  This port is closed by default with the native firewall in Windows XP SP1.