Operating System - HP-UX
1846088 Members
4287 Online
110253 Solutions
New Discussion

Re: Support Tool Issue - Cannot connect

 
OldSchool
Honored Contributor

Support Tool Issue - Cannot connect

recently I've experienced an issue on one server where mstm refuses to run. The other two server, same sub-net and switch, function properly. since the last time I used it successfully, the system's IP address has change, however other things are connecting properly to the server experiencing issues. This includes X-windows, rlogin, telnet, ping, etc..

message is: the request to connect to the unit under test (UUT) was not successfully sent to the UUT

This occurs not matter how I try to start it, local, remote, X, cstm, or mstm.

I've obviously missed something, but what?
5 REPLIES 5
Torsten.
Acclaimed Contributor

Re: Support Tool Issue - Cannot connect

You should check if the system can resolve its own hostname (fedcat) by using "nslookup "

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
OldSchool
Honored Contributor

Re: Support Tool Issue - Cannot connect

nslookup works fine...
OldSchool
Honored Contributor

Re: Support Tool Issue - Cannot connect

First off: Torsten, thanks for the suggestion. I'd already tried that, and went back and verified that it did work.

Turns out that the solution was to stop and restart diagmond. It did this by:

cd /sbin/init.d
./diagnostic stop ; ./diagnostic start

don't know what caused the issue, but that cleared it.
Andrew Merritt_2
Honored Contributor

Re: Support Tool Issue - Cannot connect

If you start diagmond (well, it's started automatically at boot time), and then change the IP address of the system, you will need to restart diagmond for STM to work as it doesn't check for changes while it's running.

Andrew
OldSchool
Honored Contributor

Re: Support Tool Issue - Cannot connect

AFAIK, that doesn't apply in this case, as the box was / has been rebooted a couple of times since the IP change, but thanks for the tip.