Event Monitoring Service problem

[Michael Leis]

Have a K420 with HPUX 11.0 on it. I've not yet set up Event Monitoring Service but I want to... when I run it from SAM I get the message: "Client connect failed. An error occurred while trying to connect to a remote system: Invalid argument." Any thoughts what this seemingly nondescript message is telling me?

[Helen French]

Hi Michael:

Try these options:

1.) Check /etc/inetd.conf file and verify the following line is there and it is uncommented:

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

2.) Check /etc/services file and verify that port 1712 is setup for registrar.

registrar 1712/tcp
registrar 1712/udp

3.) Run inetd -c

4.) Run netstat -a |grep registrar and this should come back with:

tcp 0 0 *.registrar *.* LISTEN

5.) If it is still failing, stop and start inetd. (instead of inetd -c)

/sbin/init.d/inetd stop
/sbin/init.d/inetd start

HTH,
Shiju

[S.K. Chan]

3 possibilties ..
1) /etc/inetd.conf must have this line ..

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

2) The inetd is not running. Restart it.

# ps -ef|grep inetd
==> if none then ..
# /sbin/init.d/inetd start

3) A /var/adm/inetd.sec setting clogged your port. In this case verify that /var/adm/inetd.sec allows access to port 1712

# netstat -an|grep 1712

[S.K. Chan]

Can you also verify if you can run this ..

# cd /etc/opt/resmon/lbin
# ./monconfig

If not what's the error.

[Michael Leis]

Here's the results of all your suggestions:

Shiju Wilson:
1) there and uncommented
2) they are setup in /etc/services and in /var/yp/src/services (which have been updated and pushed to this server)
3) returns no info / messages
4) returns no info / messages
5) stopped/started inetd and did 3 & 4 -- still return no info / messages.

S.K. Chan:
1) line is in place and uncommented
2) it is running
3) There is nothing in inetd.sec that should cause a problem... this file & permission is the same as it is on another system that this does work on.
4) returns no info / messages

S.K. Chan:
1) monconfig runs and says "Event Monitor is currently enabled" and indicates no errors.

Thanks for the suggestions... let me know where to go next.

[Jeff Schussele]

Hi Michael,

Run
netstat -a | more
verify that you're getting a listen or bind on the 1712 port. It should be on the localhost 127.0.0.1
If netstat -a returns no listens or binds you've got a net problem & may need to bounce the network services
/sbin/init.d/net stop
/sbin/init.d/net start

Rgds,
Jeff

[S.K. Chan]

Can you describe what you did in SAM ? Also take a look at /var/sam/log/samlog for related error message that describe more (hopefully)..

[Michael Leis]

Jeff Schussele:
The netstat -a | more did not return anything related to registrar, 1712, or localhost. I did the stop / start and it didnt help. I rebooted the server and that didnt change anything either.

S.K. Chan:
In SAM all I did was double-click on "Resource Management" and then double-click on "Event Monitoring Service". The result was the earlier mentioned error related to "Client connect failed"

As far as samlog is concerned, here is the output from it related to the double-click on "Event Monitoring Service" icon:

@!@129@1021312370@0
Mon May 13 13:52:50 2002 Entering area "Event Monitoring Service".
@!@2@1021312370@0
Executing the following command:\CLANG=C LC_ALL=C /opt/resmon/bin/emsui /opt/resmon/bin/EMSconfig.ui\C
@!@2@1021312373@0
Command completed with exit status 0.
@!@129@1021312373@0
Mon May 13 13:52:53 2002 Exiting area "Event Monitoring Service".
@!@8@1021312373@0
Entering Task Manager with task FAL_CHECK_FOR_INSTALL.
@!@4@1021312373@0
Checking SAM installation state.
@!@4@1021312373@0
No change in install state was found.
@!@8@1021312373@0
Exiting Task Manager with task FAL_CHECK_FOR_INSTALL.

[S.K. Chan]

Sorry Michael .. should have asked you to run this in my previous post. Can you run this and post the output ..

# cd /etc/opt/resmon/lbin
# ./moncheck

What it'll do is report the status of each "components" that EMS monitors. You'll see some of it being at "NOT MONITORING" status which is normal and some will say "OK".

[Michael Leis]

S.K. Chan:

When I run the moncheck command I get the message:

Client Connect Failed

And that's all it says.

I ran it on another server I have that is running Event Monitoring Service and I see what you are describing, but this stubborn server wont fly.