topic Re: Support Tool Issue - Cannot connect in Operating System - HP-UX

Support Tool Issue - Cannot connect

OldSchool — Wed, 11 Oct 2006 09:35:38 GMT

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?

Re: Support Tool Issue - Cannot connect

Torsten. — Wed, 11 Oct 2006 10:00:03 GMT

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

Re: Support Tool Issue - Cannot connect

OldSchool — Wed, 11 Oct 2006 10:09:23 GMT

nslookup works fine...

Re: Support Tool Issue - Cannot connect

OldSchool — Wed, 11 Oct 2006 14:37:57 GMT

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.

Re: Support Tool Issue - Cannot connect

Andrew Merritt_2 — Fri, 13 Oct 2006 09:12:52 GMT

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

Re: Support Tool Issue - Cannot connect

OldSchool — Fri, 13 Oct 2006 09:24:13 GMT

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.