EES, the Error/Event Subsystem, improves the fault management, serviceability, and usability of systems by providing a single set of interfaces to report, log, and retrieve system errors and events.
This release of EES provides support for the logging of VCS messages in the EES log.
EES is compatible with the following software products running on Symmetry® and NUMA-Q® systems:
EES is installed using ptx/ADMIN® and ptx/INSTALL. The kernel portion of the product is now installed as part of the DYNIX/ptx base. The consumer portion of the product needs to be installed via ptx/INSTALL.
ATTENTION We recommend that you install /var/ees on its own filesystem, otherwise the root filesystem may fill up quickly due to the size of the EES logfile. If you choose to make a new filesystem for /var/ees, we recommend that you create the new filesystem prior to installing the EES software.
The EES User's Guide contains more information about managing the size of the EES logfile.
Refer to the DYNIX/ptx and Layered Products Software Installation Release Notes for installation procedures.
The number that appears in parentheses in problem report titles is the Problem Tracking System number assigned to the report. These problems will be corrected in a future release unless otherwise noted.
The ees_notifyd daemon cannot take an action on the first event registered by the ees_notify tool if this event is the first event that occurs after the ees_notifyd daemon started. This event, however, is logged into the eeslog file.
Workaround. None.
The system will not boot when /var/ees is a volume filesystem. This problem is a general SVM boot problem due to /var/ees not being an early-access volume.
Workaround. If /var/ees is created as a separate filesystem, it must not be under SVM control.
The following list shows fixed problems in EES V1.2.0:
(249723) EES should prepend SAK printf's with the "SAK"string
(249855) SYS: eeslog header corrupted, no automated way to fix
(248917) eed_logmgr -size with eesd not running crashes system
(249903) Remove bloated code in EES due to multiple instances
(240233) EES must cleanup before a panic
(237940) Filters using ees_time cannot be properly registered because of colon
(245227) ees_logmgr dumped core doing a log compaction
(250804) Logs fill up with libees_filter messages
(250986) Functional testing on EES v1.2.0 revealed version mismatch