Event Monitoring Service Version A.03.00 Release Notes Second Edition

Chapter 1 9
Event Monitoring Service Version A.03.00 Release Notes
Known Problems and Workarounds
Known Problems and Workarounds
The following are known problems with the EMS:
Name services requirement
• What is the problem? EMS may not function if you are running name
services that do not use /etc/services, such as NIS, DNS, or X.500.
The port number for the EMS registrar is listed in /etc/services.If
you are running a different name lookup service, for example NIS,
and it is not configured to use /etc/services as part of the name
lookup process, then EMS monitors will not be able to find the
registrar program and will not function.
• What is the workaround? You can do either of the following:
— On the name server, add the registrar services line to the
appropriate services file for the name lookup service you are
running. The line should have the same port number as the line in
/etc/services, for example:
registrar 1712/ tcp # resource monitor service
— Add the /etc/services file to the lookup path your name lookup
service uses. For example, modify the nsswitch.conf file to refer
to /etc/services if you are running NIS.
Restart notifications after system reboot
• What is the problem? There is no differentiation between monitor
restart notifications due to system reboot and those due to a monitor
being restarted.
Currently the persistence client (p_client) logs all monitor restarts
as RM_RESTART. If you would like to be able to distinguish between
restarts due to monitor failure (which are logged as RM_RESTART) and
restarts during system reboot (which should be logged as RM_REBOOT),
you need to modify the inittab file.
• What is the workaround? Edit the /etc/inittab file to make sure it
looks like this:
init:3:initdefault: