topic Re: EMS: Client connect failed in Operating System - HP-UX

EMS: Client connect failed

Coleman Blake_2 — Thu, 17 Jul 2003 16:50:13 GMT

I tried to bring up EMS through SAM to modify and add some events. When I clicked on the EMS icon, I got a message "Client connect failed...".

I tried monconfig and got the same message when I tried to "Check detailed monitoring status."

It worked the last time I tried it a month or so ago. Any ideas what's wrong and how to fix it?

Re: EMS: Client connect failed

Ken Hubnik_2 — Thu, 17 Jul 2003 16:52:43 GMT

Try stopping and restarting ems

/sbin/init.d/ems stop
/sbin/init.d/ems start

Re: EMS: Client connect failed

Jeff Schussele — Thu, 17 Jul 2003 17:03:59 GMT

Also check the /etc/rc.config.d/ems file to make sure EMS_ENABLED=1 or it won't let you start it.
I would also check the log files in /etc/opt/resmon/log for clues - specifically the client.log file

HTH,
Jeff

Re: EMS: Client connect failed

Jeff Schussele — Thu, 17 Jul 2003 17:13:42 GMT

Also make sure you have the following in /etc/services

registrar 1712/tcp # resource monitoring service
registrar 1712/udp # resource monitoring service

And this in /etc/inetd.conf

registrar stream tcp nowait root /etc/opt/resmon/lbin/registrar /etc/opt/resmon/
lbin/registrar

And make sure there are NO registrar entries in /var/adm/inetd.sec that could be preventing connections.
You may also want to see if there is already a registrar process bound - run

netstat -an | grep 1712

If EMS is not running BUT you do have something bound to port 1712, that may be preventing the client connection.

HTH,
Jeff

Re: EMS: Client connect failed

Elena Leontieva — Thu, 17 Jul 2003 17:35:21 GMT

This is from Document id: A5774548:

----------|------------------------------------------------------------
Cause A: | The /etc/inetd.conf file is not complete.
Answer A: | Ensure that /etc/inetd.conf contains the following
| information:
|
| registrar stream tcp nowait root | /etc/opt/resmon/lbin/registrar /etc/opt/resmon/lbin/registrar
|
----------|------------------------------------------------------------
Cause B: | The inetd process is not running.
Answer B: | Re-start inetd.
|
----------|------------------------------------------------------------
Cause C: | A /var/adm/inetd.sec setting clogged your port.
Answer C: | Verify that /var/adm/inetd.sec allows access to port 1712.
|
----------|------------------------------------------------------------

If none of the above causes and solutions apply to your situation:

1. Re-execute the netstat command:

netstat -an | grep 1712

2. Ensure that your system contains the /var/adm/inetd.sec and
/etc/inetd.conf files.

3. Enable inetd logging:

inetd -k; inetd -l

Regards,
Elena.

Re: EMS: Client connect failed

Coleman Blake_2 — Fri, 18 Jul 2003 10:45:09 GMT

Thanks everyone. The "registrar" line in inetd.conf had been commented out.

Uncommenting it and running inetd -c fixed things.

/sbin/init.d/ems stop produces the message "This script doesn't stop EMS." I think you have to use monconfig to stop it.

Now I nave to figure out who or what modified the inetd.conf file.

Coleman