Event Monitoring Service Version A.03.00 Release Notes

Chapter 1 7
Required Patches and Problems
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 one 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:
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:
ems1::bootwait:touch
/etc/opt/resmon/persistence/reboot_flag
ems2::bootwait:/usr/bin/rm -f
/etc/opt/resmon/persistence/runlevel4_flag
ems5::boot:/etc/opt/resmon/lbin/p_client -r
ems3:3:once:touch
/etc/opt/resmon/persistence/runlevel4_flag
ems4:3456:respawn:/etc/opt/resmon/lbin/p_client