Event Monitoring Service Version A.03.20 Release Notes

12 Chapter1
Event Monitoring Service Version A.03.20 Release Notes
Known Problems and Workarounds
Known Problems and Workarounds
The following are known problems and suggested workarounds with the
EMS:
JAGab77527: EMS client may fail to connect to the
registrar
What is the problem? An EMS client may fail to connect to the EMS
registrar. If this occurs, you may see a message in
/etc/opt/resmon/log/client.log like this one:
-------------------Start Event--------------------
Event 11 occurred at Tue Oct 19 15:53:24.025936 1999
Process ID: 1062 (/etc/opt/resmon/lbin/startmon_client)
Log Level: Error
rm_client_connect: Failed to connect to hprdstts.rose.hp.com,
IP address 15.8.135.200, Port 1712: Invalid argument
-------------------End Event----------------------
-------------------Start Event--------------------
User event occurred at Tue Oct 19 15:53:24.036390 1999
Process ID: 1062 (/etc/opt/resmon/lbin/startmon_client)
Log Level: Error
client connect failed: An error occurred while trying to connect to a remote
system: Invalid argument
-------------------End Event----------------------
What is the workaround? Perform the following:
1. Ensure the inetd is listening on port 1712. To do this, you can
execute the following command. The desired output line is listed here:
netstat -an | grep 1712
tcp 0 0 *.1712 *.* LISTEN
If inetd is not listening on port 1712, be sure the following entry is in
/etc/inetd.conf:
registrar stream tcp nowait root \
/etc/opt/resmon/lbin/registrar \
/etc/opt/resmon/lbin/registrar
Be sure the following line is in the /etc/services file: