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 the following default behaviour:
Purge EES records older than 30 days, everyday at midnight. (The number of days and the time are user-configurable.)
Purge syslog message with severity of WARN/INFO/DEBUG
EES is compatible with the following software products running on 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 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.1:
253662 ees_get_rt_event timeout value incorrect.
250824 Default EES setup does not purge old messages and can fill /
Fix: By default, EES records older than 30 days will be deleted midnight everyday. However, the number of days of EES records to be deleted and the time at which to run this deletion are user-configurable through the EES MANAGEMENT submenu in ptx/Admin.
244992 syslog debug messages flooding the ees log
Fix: A default policy is added during EES installation to purge syslog messages with DEBUG/WARN/INFO/NOTICE severity. However this policy may be modified using ees_logmgr -policy [change|delete] policy_id,...
251615 ees_vcs logd files all events as severity = info
251522 Base and TCP compatible versions are wrong for EES image
251412 ees_filter_get leaks memory like a sieve
250986 Functional testing on EES v1.2.0 revealed version mismatch
250962 EES filter added from invalid file returns 0 status
250731 took 11 minutes for reader daemon to accept notification server
250421 ees_view coredumps when accessing large logs
250172 generate an event when a daemon is started/stopped
250145 ees_logd is unable to compact log on eng2
249560 ees_send man page error
249561 ees_view man page error
249559 typo in ees_logmgr man page
249368 chroot commands during install core dumping
248358 Binary timestamp incorrectly described on man page
247701 FUNC ees_view, ees_filter filter_exp described in ees_send(1M)
247488 compaction using ees_logmgr specifying a filter displays err msg
247434 ees_logmgr -policy show_stat doesn't report stats for all ids
247349 ees_view -tail is argument-order sensitive and should not be
246461 man page for ees_view lacks examples
245709 ees_compact_log() seems to return false EES_FILE_ACCESS_FAILED. 243510 ees_notifyd should be stopped first
243361 ees_notify -file <directory> succeeds without proper warning
243206 transfer of dmesg "events" not working correctly
242632 ees_notifyd gives up too soon
240624 ees_send command should do more validation of its cmdline argmnts