- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - HP-UX
- >
- General
- >
- Re: vmunix alerts in syslog.log
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
12-17-2013 06:52 AM
12-17-2013 06:52 AM
vmunix alerts in syslog.log
Hello Experts,
I am getting continues vmunix alerts in syslog.log file of server which looks like as below.
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.
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility is no longer receiving excessive
errors from the I/O subsystem. 1 I/O error entries were lost.
Any idea how to overcome this repeat error?
Thanks & Regards,
Chirag Parikh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-17-2013 01:47 PM
12-17-2013 01:47 PM
Re: vmunix alerts in syslog.log
You are getting I/O errors from a problematic device. Look for other entries in syslog.log prior to these messages or run the command 'dmesg'.
You dont give details such as OS version or model of the server, but perhaps there are also entries being logged in the EMS event log. View the file /var/opt/resmon/log/event.log for any recent entries.
Also, you could search this forum for many other examples of others receiving the same message.
-Bob
Was this helpful? Like this post by giving me a thumbs up below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-18-2013 06:23 AM - edited 12-18-2013 06:24 AM
12-18-2013 06:23 AM - edited 12-18-2013 06:24 AM
Re: vmunix alerts in syslog.log
Here are the missing information from my last post.
Ioscan output --
XXXXXX:root> ioscan -fn |grep -i "FCP" |more
fcp 2 0/2/1/0/4/0.201 fcd_fcp CLAIMED INTERFACE FCP Domain
ext_bus 20 0/2/1/0/4/0.201.0.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
ext_bus 21 0/2/1/0/4/0.201.0.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ext_bus 22 0/2/1/0/4/0.201.1.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
ext_bus 23 0/2/1/0/4/0.201.1.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ext_bus 24 0/2/1/0/4/0.201.4.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
ext_bus 25 0/2/1/0/4/0.201.4.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ext_bus 26 0/2/1/0/4/0.201.5.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
ext_bus 27 0/2/1/0/4/0.201.5.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ext_bus 41 0/2/1/0/4/0.201.14.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ext_bus 37 0/2/1/0/4/0.201.15.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
fcp 3 0/6/1/0/4/0.101 fcd_fcp CLAIMED INTERFACE FCP Domain
ext_bus 28 0/6/1/0/4/0.101.0.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
ext_bus 29 0/6/1/0/4/0.101.0.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ext_bus 30 0/6/1/0/4/0.101.1.0.0 fcd_vbus NO_HW INTERFACE FCP Array Interface
ext_bus 31 0/6/1/0/4/0.101.1.255.0 fcd_vbus NO_HW INTERFACE FCP Device Interface
ext_bus 32 0/6/1/0/4/0.101.4.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
ext_bus 33 0/6/1/0/4/0.101.4.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ext_bus 34 0/6/1/0/4/0.101.5.0.0 fcd_vbus CLAIMED INTERFACE FCP Array Interface
ext_bus 35 0/6/1/0/4/0.101.5.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ext_bus 40 0/6/1/0/4/0.101.14.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
ext_bus 36 0/6/1/0/4/0.101.15.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
two hardware path is captured in event.log file which cause this repeat alerts, check the no_hw status hardware path from above.
OS version -- B.11.11
Hardware model -- 9000/800/rp4440
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-18-2013 08:36 AM
12-18-2013 08:36 AM
Re: vmunix alerts in syslog.log
You should check the connection (e.g. fcmsutil ... from host or switchshow from switch). Maybe bad cable, bad port, etc...?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP