Event Monitoring Service Version A.03.10 Release Notes

16 Chapter1

Known Problems and Workarounds

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 ﬁle:

registrar 1712/tcp # resource monitor service

Then enter inetd -c to reconﬁgure inetd.

2. Retry running the client that failed.

JAGab69421: /cluster/package/package/package_

status displays an error when systems have multiple

network host aliases

Whatis the problem? /cluster/package/package_status resources are

not available, even though cmviewcl shows that the package state is

up or down.

What is the workaround? In order to monitor package_status resources,

the system hostname must match the “ofﬁcial” network host name. Also,

if you are not using DNS, the ServiceGuard node cannot have any other

aliases in /etc/hosts or in the NIS hosts map ﬁle.

The system hostname is speciﬁed by the HOSTNAME variable in

/etc/rc.config.d/netconf. The network host name is determined by

the name resolver: DNS host table, NIS hosts map ﬁle, or /etc/hosts.

You can verify that this requirement is satisﬁed by using the nslookup

command. The command nslookup $(

hostname

) must show only one

Name and no Aliases. For example: