STM errors

[JOHN TURNER_2]

When we try and run STM on one of our servers, the following happens and STM fails to start. Can anyone shed some light on the situation

1. root#stm

2. running command file (/usr/sbin/stm/ui/config/.stmrc)

3. an unexpected error has been encounted when attempting to connect to the hostname (SN3a)

4. aborting all command files

5. NO CURRENT SYSTEMS

[Sivakumar TS]

Dear John,

STM is a Online Diag Tool which requires the diagnostic daemons to be running to do the DIAGs.

Please make sure that, the "diagmond" daemon is runnig.

#ps -ef | grep diag

Also check if the diagnostic is enabled in,

#vi /etc/rc.config.d/diagnostic

make

DIAGNOSTICS=1

With Regards,

Siva.

[JOHN TURNER_2]

all those pointers are set up correctly, do you have any more thoughts

[DCE]

John,

I found the following on doc.hp.com

Hope it helps

Dave

This message will appear if the system is configured for LOCAL_ONLY, and the user attempts to connect to a remote system:


An unexpected error was encountered while attempting to retrieve the
host info for hostname (XX).
This could be due to either of the following conditions:

1) The support tool daemon "diagmond" may not be running on that system.
Use the STM Startup command (in the administration menu under the
file menu.)

2) The support tool daemon "diagmond" on that system may be configured
to only allow local connections. Check the value of the configuration
parameter LOCAL_ONLY_ENABLE in the /var/stm/config/sys/diagmond.cfg
file or for the existence of the /var/stm/config/sys/local_only file
on that system.

3) The diagnostic system on this system may be configured
to only allow local connections. Check for the existence of the
/var/stm/config/sys/local_only file on this system.

4) The IP address for the system may be invalid or may not be associated
with a valid host. Use a valid IP address.

5) Networking may be incorrectly configured on one of the systems involved.
Verify networking by comparing 'nslookup `hostname`' with the output
of ifconfig of the LANs identified by lanscan.

More details may be available in the System Activity Log and in the
syslog on that system.

It may be necessary to access these using the Local Unit Under Test (UUT).

[Torsten.]

There are 2 things I would do:

restart the diagnostics
re-install the software in a current version

[Sameer_Nirmal]

Hi,

I guess the two probable causes of such error.
1. Either "diagmond" deamon is not running or not properly initilaised.
Check if the "diagmond" is running
# ps -ef | grep diag
If not running , start it using
# /usr/sbin/stm/uut/bin/sys/diagmond

Check for other child deamons of "diagmond" if they are running like diaglogd,memlogd,cclogd(for cell based server) using
# ps -ef | grep

If these deamons are running which confirms "diagmond" initilisation is complete.

2. Local Host network trouble.
Ensure the host name resolution works ( /etc/hosts or DNS ) using ping or nslookup .
# netstat -in
# ll /dev/tty

Ensure the latest STM patch installed on the system.

Which STM version you are dealing with?
# swlist -l fileset | grep Sup-Tool-Mgr
What's HP-UX version?