- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- dmesg diaglogd error.
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
тАО07-20-2002 09:57 AM
тАО07-20-2002 09:57 AM
Would anyone have any info on this error? I see it in dmesg and syslog.log
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
errors from the I/O subsystem. I/O error entries will be lost
until the cause of the excessive I/O logging is corrected.
If the diaglogd daemon is not active, use the Daemon Startup command
in stm to start it.
If the diaglogd daemon is active, use the logtool utility in stm
to determine which I/O subsystem is logging excessive errors.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2002 10:17 AM
тАО07-20-2002 10:17 AM
Solution# /sbin/init.d/diagnostic stop
# /sbin/init.d/diagnostic start
2 - If the above fails to resolve the problems you could have a disk / card failing... try using xstm (X version of stm) or mstm (menu version of stm) to look at all IO type of devices. also "ioscan -f" may be of some help.
Generally I have found one of the above does the trick. If not I'm sure other bright sparks will come forward with more info.
Tim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2002 10:58 AM
тАО07-20-2002 10:58 AM
Re: dmesg diaglogd error.
My first guess is to see if you can relate the I/O errors to a tape backup session. As suggested, you may want to use 'stm' logtools to look for/at errors.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2002 11:39 AM
тАО07-20-2002 11:39 AM
Re: dmesg diaglogd error.
1) In syslog.log is this all the error you see ? Do you see some other message that ask for you to run "resdata" to get more information from the STM log ? If you don't then most likely this is due to the "mismatch" that I mentioned above.
2) Run stm and look at any possible IO errors. If you can't find any, again, possibility of the above is very likely.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-20-2002 04:20 PM
тАО07-20-2002 04:20 PM
Re: dmesg diaglogd error.
I ran cstm to track it down and ioscan -fnC disk.
It ended up being a fiber card on my N class server that was conected via fiber to an XP-256. We tried a differnt fiber cable but that was not it. So we called HP ... they had someone on site replaced the card and we were ready to go. What was happening from this was that our informix engine was getting high checkpoints and timming out because it was trying to access the disk on the XP though the bad fiber card. Once the fiber card was replaced everything was good.
Thanks everyone,
~ richard