- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- ISEE Report
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2004 06:28 AM
тАО09-08-2004 06:28 AM
ISEE Report
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2004 06:37 AM
тАО09-08-2004 06:37 AM
Re: ISEE Report
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2004 06:50 AM
тАО09-08-2004 06:50 AM
Re: ISEE Report
Thanks
Prashant
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-08-2004 08:40 PM
тАО09-08-2004 08:40 PM
Re: ISEE Report
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2004 01:03 AM
тАО09-09-2004 01:03 AM
Re: ISEE Report
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2004 02:05 AM
тАО09-09-2004 02:05 AM
Re: ISEE Report
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2004 02:08 AM
тАО09-09-2004 02:08 AM
Re: ISEE Report
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2004 02:58 AM
тАО09-14-2004 02:58 AM
Re: ISEE Report
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?