EES V1.2.2 Release Notes


Introduction

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.


Changes Since the Previous Release

This release of EES provides bug fixes and the following default behaviour:


Compatibility Information

EES is compatible with the following software products running on NUMA-Q® systems:


Installation

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.


Problem Reports

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.


Open Problem Reports


SVM Problems with /var/ees Being a Volume (249612)

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.


Fixed Problem Reports

The following list shows fixed problems in EES V1.2.2:

253629 /etc/init.d/S52EES ran ees_vcsd on symmetry sb8000 systems.

254065 ees_view -terse -new dumped core.

253789 ees_view wrote usage message to stdout or stderr.

251003 ees_view -terse -new stopped printing messages.

254227 EES logged a critical message about bad packet when dropping messages.

251615 ees_vcs logd filed all events as severity = info.

251522 Base and TCP compatible versions were wrong for EES image.

251412 ees_filter_get leaked memory.

250986 Functional testing on EES v1.2.0 revealed version mismatch.

250962 EES filter added from an invalid file returned 0 status.

250731 Reader daemon took too long to accept notification from the server.

250421 ees_view dumped core when accessing large logs.

250172 EES generated an event when a daemon was started or stopped.

250145 ees_logd was unable to compact log.

249560 ees_send man page contained an error.

249561 ees_view man page contained an error.

249559 ees_logmgr man page contained an error.

249368 chroot commands dumped core during install.

248358 Binary timestamp incorrectly described on man page.

247701 ees_view, ees_filter filter_exp incorrectly described in ees_send(1M).

247488 Compaction using ees_logmgr specified a filter displayed error messages.

247434 ees_logmgr -policy show_stat didn't report stats for all IDs.

247349 ees_view -tail was argument-order sensitive.

246461 Man page for ees_view lacked examples.

245709 ees_compact_log() returned false value of EES_FILE_ACCESS_FAILED.

243510 ees_notifyd stopped at wrong time.

243361 ees_notify -file <directory> succeeded without proper warning.

243206 Transfer of dmesg "events" did not work correctly.

242632 ees_notifyd gave up too soon.

240624 ees_send command did not do enough validation of its commandline arguments.

253662 ees_get_rt_event timeout value was incorrect.