Insight Remote Support
cancel
Showing results for 
Search instead for 
Did you mean: 

ISEE Report

Prashant Zanwar_4
Respected Contributor

ISEE Report

I have a ISEE report which says :

There have been no errors logged in the I/O error logfile for more than 30 days. Suspect that the diagnostics are either corrupted or the logging facility has been disabled.

Please advise what shall do to resolve it. Let me know if any more inputs are required?

STM has following processes running :

root 1096 1 0 Sep 5 ? 0:17 /usr/sbin/stm/uut/bin/sys/diagmond
root 15947 15453 1 14:27:55 pts/ta 0:00 grep -i stm
root 2295 1 0 Sep 5 ? 1:14 /usr/sbin/stm/uut/bin/tools/monitor/lpmc_em
maestro 12173 1135 0 06:03:28 ? 0:01 /opt/maestro/bin/writer -- 2001 NCSTMR1 MAILMAN HPUX 7.0 8
root 2047 1 0 Sep 5 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_TL_adapter
root 1967 1 0 Sep 5 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/disk_em
root 1915 1 0 Sep 5 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/armmon
root 2101 1 0 Sep 5 ? 0:20 /usr/sbin/stm/uut/bin/tools/monitor/dm_core_hw
root 2207 1 0 Sep 5 ? 0:05 /usr/sbin/stm/uut/bin/tools/monitor/dm_stape
root 2165 1 0 Sep 5 ? 0:00 /usr/sbin/stm/uut/bin/tools/monitor/dm_memory
maestro 12180 1135 0 06:03:43 ? 0:16 /opt/maestro/bin/mailman -- 2002 NCSTMR1 MAILMAN HPUX 7.0 SO
root 2340 1 0 Sep 5 ? 0:01 /usr/sbin/stm/uut/bin/tools/monitor/sysstat_em

Thanks in advance
Prashant
"Intellect distinguishes between the possible and the impossible; reason distinguishes between the sensible and the senseless. Even the possible can be senseless."
7 REPLIES
Sundar_7
Honored Contributor

Re: ISEE Report

hmm..interesting..do they imply there SHOULD be some I/O errors ? :-). Is there any reference to the log file ?

STM maintains its log files in /var/stm/logs/os directory.

Try to read the log file and confirm

# cstm

cstm> runutil logtool

Logtool> fr
Logtool> fl

-- Sundar
Learn What to do ,How to do and more importantly When to do ?
Prashant Zanwar_4
Respected Contributor

Re: ISEE Report

It says runutil is currently disabled? what shall be done to enable it?
Thanks
Prashant
"Intellect distinguishes between the possible and the impossible; reason distinguishes between the sensible and the senseless. Even the possible can be senseless."
Andrew Merritt_2
Honored Contributor

Re: ISEE Report

Is 'diaglogd' also running? If not, then there is definitely a problem.

Places to look for clues:

Have a look at the log files in /var/opt/resmon/log, and see if anything is being reported.

Check /var/adm/syslog/syslog.log for any errors related to diaglogd.

Run STM and look at the System Activity Log ('sal' in cstm).

Run /etc/opt/resmon/lbin/moncheck. It should list the monitors that are active.
Prashant Zanwar_4
Respected Contributor

Re: ISEE Report

These are really good hints. What I am seeing is version for STM in my server is 42.00. And when i am trying cstm for everything it is saying disabled. or
NO CURRENT SYSTEM.
Does some one have idea how to turn on the features.
There are no errors on diaglogd in syslog. and also I can see it has reported errors on drive on Aug 30, I mean resmon.
Please advise
Thanks
Prashant
"Intellect distinguishes between the possible and the impossible; reason distinguishes between the sensible and the senseless. Even the possible can be senseless."
Andrew Merritt_2
Honored Contributor

Re: ISEE Report

Sounds like diaglogd has failed for some reason.

I'd suggest opening a support call with HP to get it properly diagnosed.

You can try stopping and starting OnlineDiags daemons, which might fix it.

# /sbin/init.d/diagnostic stop

(check diagmond, memlogd, cclogd have stopped)

# /sbin/init.d/diagnostic start

Andrew Merritt_2
Honored Contributor

Re: ISEE Report

Sorry, pressed 'send' too soon.

After the 'diagnostic start', diaglogd should now be running.

(After the 'diagnostic stop' you will still see the monitors running (/usr/sbin/stm/uut/bin/tools/monitor/*).

Andrew
Andrew Merritt_2
Honored Contributor

Re: ISEE Report

Is this the same server as mentioned in http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=694763 ?

What type of server is it? I'd recommend upgrading to A.44.00 or later, that may well cure the problem. You may have a bad installation, or the hardware is too new to be supported by A.42.00.

Were there any errors logged in /var/adm/sw/swagent.log when A.42.00 was installed? Was this version of OnlineDiags ever running successfully on this system?