- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: syslog message
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
Forums
Discussions
Discussions
Discussions
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
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-28-2008 01:13 AM
07-28-2008 01:13 AM
Hi,
This is what my syslog keeps telling daily.
Jul 28 13:12:49 drbkp01 EMS [2350]: ------ EMS Event Notification ------ Value: "SERIOUS (4)" for Resource: "/storage/events/disks/default/0_2_1_0.0.0.0.0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 154009603 -r /storage/events/disks/default/0_2_1_0.0.0.0.0 -n 154009609 -a
When i referred through my event.log file, it tells that the current driver version is not supported.
Kindly suggest!
Attached is the syslog file and outputs which may help you!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2008 01:43 AM
07-28-2008 01:43 AM
Re: syslog message
#/opt/resmon/bin/resdata -R 154009603 -r /storage/events/disks/default/0_2_1_0.0.0.0.0 -n 154009609 -a
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2008 01:50 AM
07-28-2008 01:50 AM
Re: syslog message
Hi Ahsan,
attached is the output
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2008 02:09 AM
07-28-2008 02:09 AM
Re: syslog message
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2008 02:14 AM
07-28-2008 02:14 AM
Re: syslog message
You may have a pathing issue.
You may also just be detecting a disk array on LUN0 because no LUN0 is presented to your machine. This is common and is remedied by either presenting a LUN0 or ignoring the EMS message.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2008 02:22 AM
07-28-2008 02:22 AM
Re: syslog message
This is software configuration error.
we need to restart the diagnostic daemon to stop this events.
#/sbin/init.d/diagnostic stop
#/sbin/init.d/diagnostic start
After restarting this daemon you will not get this messages.
HTH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2008 02:57 AM
07-28-2008 02:57 AM
Re: syslog message
Hi Sudhakar,
I have restarted the daemon and let me wait and see what happens! Points will be surely awarded if it works.
Thanks for the help.
Sridhar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2008 04:27 AM
07-28-2008 04:27 AM
Re: syslog message
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2008 04:31 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2008 04:54 AM
07-28-2008 04:54 AM
Re: syslog message
Event.log shows the following
"Software configuration error" on "IR Volume"
Event #.............: 100776
Version:
OS Version......................: B.11.23
STM Version.....................: C.54.00
EMS Version.....................: A.04.20
CR# JAGag25112
Submitter_Text
Server rx3600 - HPUX 11.23 - STM Version C.54.00 - EMS Version A.04.20
workaround
Use the disabled_instances file to hide events from the IR Volume device
1. run /etc/opt/resmon/lbin/moncheck to determine the names of
instances which should be disabled
2. add/delete/modify instances in the disabled_instances file with an
editor of your choice
3. run /etc/opt/resmon/lbin/monconfig
4. select the "E)nable Monitoring" command
5. wait for monitoring to be re-enabled
6. select "(C)heck detailed monitoring status", or run moncheck again
to verify the changes
Fix Text
fix
The fix will be available in the following patch and Release :
1. PHSS_35807 for 11.23
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2008 05:03 AM
07-28-2008 05:03 AM
Re: syslog message
ftp://us-ffs.external.hp.com/hp-ux_patches/s700_800/11.X/PHSS_35807.txt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2008 05:06 AM
07-28-2008 05:06 AM
Re: syslog message
http://www11.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=ucr_na-KMN8606469959_ssb-1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2008 08:39 PM
07-31-2008 08:39 PM
Re: syslog message
The patch PHSS_35807 did resolve the issue!