topic Re: syslog message in Operating System - HP-UX

syslog message

Sridhar R — Mon, 28 Jul 2008 08:13:51 GMT

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!

Re: syslog message

Jeeshan — Mon, 28 Jul 2008 08:43:23 GMT

execute this below command and post its output

#/opt/resmon/bin/resdata -R 154009603 -r /storage/events/disks/default/0_2_1_0.0.0.0.0 -n 154009609 -a

Re: syslog message

Sridhar R — Mon, 28 Jul 2008 08:50:19 GMT

Hi Ahsan,

attached is the output

Thanks!

Re: syslog message

Jeeshan — Mon, 28 Jul 2008 09:09:44 GMT

this is not a big problem. check the multipathing software. better you can log a case to HP.

Re: syslog message

Steven E. Protter — Mon, 28 Jul 2008 09:14:34 GMT

Shalom,

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

Re: syslog message

SUDHAKAR_18 — Mon, 28 Jul 2008 09:22:02 GMT

Hello Shridhar,

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

Re: syslog message

Sridhar R — Mon, 28 Jul 2008 09:57:43 GMT

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

Re: syslog message

TTr — Mon, 28 Jul 2008 11:27:44 GMT

I don't know why you are being asked to check the path error or restart the diags. This error is coming from the IR volume (internal HW raid volume of the BL860). First ensure that the HW raid status for the ir volume is good and that no disks have failed. Then check for the possibility that diags/ems are not aware of the ir volume and treat it as a regular disk, in which case you would need a patch.

Re: syslog message

TTr — Mon, 28 Jul 2008 11:31:51 GMT

In fact I just checked, I assumed that you have 11.23 (BL860 blade server), PHSS_35807 in symptom #4, says "Event 100776 was being reported by disk_em for IR Volume". Look like you need to patch.

Re: syslog message

Avinash20 — Mon, 28 Jul 2008 11:54:56 GMT

Good Day,

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

Re: syslog message

Avinash20 — Mon, 28 Jul 2008 12:03:03 GMT

For your referance

ftp://us-ffs.external.hp.com/hp-ux_patches/s700_800/11.X/PHSS_35807.txt

Re: syslog message

Avinash20 — Mon, 28 Jul 2008 12:06:55 GMT

This technical doc will help you

http://www11.itrc.hp.com/service/cki/docDisplay.do?docLocale=en&docId=ucr_na-KMN8606469959_ssb-1

Re: syslog message

Sridhar R — Fri, 01 Aug 2008 03:39:10 GMT

Thanks for all the help!

The patch PHSS_35807 did resolve the issue!