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

EMS - Client connect failed when moncheck

Godfrey Zhang — Wed, 31 Mar 2004 19:59:44 GMT

Using monconfig:
1. (C)heck detailed monitoring status, results "Client connect failed"
2. (K)ill (disable) monitoring, results:
Are you sure you wish to disable event monitoring?
{(Y)es,(N)o,(H)elp} [n] Y

This may take a while...

EVENT MONITORING IS CURRENTLY ENABLED.

when I check the processes: ps -ef | grep monitor, I got nothing.

3. (E)nable Monitoring, results:
This may take a while...

EVENT MONITORING IS CURRENTLY ENABLED.

when I check the processes: ps -ef | grep monitor, I got nothing (expecting some processes).

How can I get it working properly?

monconfig:
EVENT MONITORING IS CURRENTLY ENABLED.
EMS Version : A.03.20.01
STM Version : A.43.00
Platform: 11i (11.11) 9000/800/L2000-44

Re: EMS - Client connect failed when moncheck

Michael Tully — Wed, 31 Mar 2004 20:31:53 GMT

The actual process for the EMS is called 'emsagent'. (/etc/opt/resmon/lbin/emsagent)
You could try to run /etc/opt/resmon/lbin/moncheck first. Failing that you could try to stop/start it, before attmepting connection.
(/sbin/init.d/emsa)

Re: EMS - Client connect failed when moncheck

Godfrey Zhang — Wed, 31 Mar 2004 20:51:46 GMT

Hi Michael;

No luck:
HLZ1HXO7 (hxo7)# ./emsa stop
emsagent stopped
HLZ1HXO7 (hxo7)# ./emsa start
HLZ1HXO7 (hxo7)# /etc/opt/resmon/lbin/moncheck
Client connect failedHLZ1HXO7 (hxo7)# ps -ef | grep monitor
root 27772 27728 0 13:38:28 pts/ta 0:00 grep monitor
HLZ1HXO7 (hxo7)#

Re: EMS - Client connect failed when moncheck

Godfrey Zhang — Wed, 31 Mar 2004 21:10:47 GMT

I found the problem, it was /var/adm/inetd.sec disabled the registrar

registrar deny

commented out, all good now.

Thanks
Godfrey