Event Monitoring Service Version A.03.10 Release Notes

Chapter 1 13

Patches and Fixes in this Version

JAGab19144

JAGab69972

Problem: When monitors were restarted due to system

reboot, a restart notiﬁcation was sent instead of a

reboot notiﬁcation

Resolution: Reboot notiﬁcations are sent only when a

monitor is restarted during system start-up

immediatelyaftersystemreboot.Restartnotiﬁcations

are sent when a monitor is restarted at any other

time.

JAGab16576

JAGab25503

JAGab24903

Problem: The on-line diagnostic clients

startmon_client and psmctd logged repeated

time-outs for monitor requests in the client.log

EMS log ﬁle during system start-up. Also, log

messages with the error Bad file number would

appear intermittently in the registrar.log EMS log

ﬁle.

Resolution: Reliability has been improved by ensuring

that the framework does not wait indeﬁnitely under

some unusual conditions and that the framework

continues to service monitorrequests while waiting to

contact other monitors, which may be non-responsive

during system start-up.

JAGab21159 Problem: Error messages such as Error renaming

p.1.86234607@ would appear intermittently in the

client.log EMS log ﬁle. Other problems might also

occur, including the abnormal termination of the

persistence client (p_client).

Resolution: The persistence client (p_client) was

allocating one less byte than necessary when

renaming persistence ﬁles. This caused memory

corruption. This has been corrected.

Table 1-5 Corrected Defects

SR Number Problem and Resolution