EMS Monitor Restart

[Luis Lino_1]

We have some menssage in our syslog.log:
....................................
Feb 2 11:58:28 peunx09 EMS [4577]: ----- EMS Monitor Restart ----- Title: disk_em Command: /usr/sbin/stm/uut/bin/tools/monitor/disk_em Vendor: Hewlett-Packard Company Version: B.01.01 To obtain a list of currently monitored resources, execute the following: /opt/resmon/bin/resdata -M 1533300606
Feb 2 13:01:03 peunx09 EMS [9974]: ----- EMS Monitor Restart ----- Title: disk_em Command: /usr/sbin/stm/uut/bin/tools/monitor/disk_em Vendor: Hewlett-Packard Company Version: B.01.01 To obtain a list of currently monitored resources, execute the following: /opt/resmon/bin/resdata -M 1533300606
Feb 2 14:53:38 peunx09 su: + ta root-orased
Feb 2 16:01:24 peunx09 EMS [25458]: ----- EMS Monitor Restart ----- Title: disk_em Command: /usr/sbin/stm/uut/bin/tools/monitor/disk_em Vendor: Hewlett-Packard Company Version: B.01.01 To obtain a list of currently monitored resources, execute the following: /opt/resmon/bin/resdata -M 1533300606
Feb 3 02:02:36 peunx09 EMS [16751]: ----- EMS Monitor Restart ----- Title: disk_em Command: /usr/sbin/stm/uut/bin/tools/monitor/disk_em Vendor: Hewlett-Packard Company Version: B.01.01 To obtain a list of currently monitored resources, execute the following: /opt/resmon/bin/resdata -M 1533300606
Feb 3 04:12:37 peunx09 su: + tty?? root-sedadm
Feb 3 06:02:49 peunx09 EMS [515]: ----- EMS Monitor Restart ----- Title: disk_em Command: /usr/sbin/stm/uut/bin/tools/monitor/disk_em Vendor: Hewlett-Packard Company Version: B.01.01 To obtain a list of currently monitored resources, execute the following: /opt/resmon/bin/resdata -M 1533300606
Feb 3 06:44:39 peunx09 su: + tty?? root-sedadm

...............................
And we have already executed this command but
don't happen nothing:
............................
peunx09 # /opt/resmon/bin/resdata -M 1533300606
/storage/events/disks/default/0_1_1_0.0.0
/storage/events/disks/default/0_1_1_0.1.0
/storage/events/disks/default/0_1_1_1.2.0
peunx09 # ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
============================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 36.4GST336753
/dev/dsk/c2t0d0 /dev/dsk/c2t0d0s2 /dev/rdsk/c2t
/dev/dsk/c2t0d0s1 /dev/rdsk/c2t0d0 /dev/rdsk/c2t
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 36.4GST336753
/dev/dsk/c2t1d0 /dev/dsk/c2t1d0s2 /dev/rdsk/c2t
/dev/dsk/c2t1d0s1 /dev/dsk/c2t1d0s3 /dev/rdsk/c2t
disk 3 0/1/1/1.2.0 sdisk CLAIMED DEVICE HP 146 GMAP3147N
/dev/dsk/c3t2d0 /dev/rdsk/c3t2d0

Could you help me, please?

Thanks

Luis L.

[melvyn burnard]

>And we have already executed this command but
don't happen nothing:
............................
peunx09 # /opt/resmon/bin/resdata -M 1533300606
/storage/events/disks/default/0_1_1_0.0.0
/storage/events/disks/default/0_1_1_0.1.0
/storage/events/disks/default/0_1_1_1.2.0

Well something did happen, as you got the above output.
What this is telling you is that EMS is using the disk_em monitor, and the devices listed in the output are being monitored, namely the disk drives at hardware paths:
0_1_1_0.0.0
0_1_1_0.1.0
0_1_1_1.2.0

[Henk Geurts]

Luis

is your problem the restart of the EMS monitor and thhat you can't find the reason?
check your crontab for commands that execute around the timesstamps in your syslog

regards.
Henk

[Luis Lino_1]

Hi,
Thanks, but in my crontab can't find anything about EMS Monitor,I don't Know if this service is automatically installed or you execute some command to enable the service.

How can I check this service?

Thanks
Luis

[Jeff Schussele]

Hi Luis,

I believe there's a known issue in EMS that causes spurious restarts - I *think* it's a memory leak.
Try updating EMS with the following 11.11 patch - PHSS_28844 - here:

http://www2.itrc.hp.com/service/patch/patchDetail.do?patchid=PHSS_28844

Or the 11.0 version - PHSS_28843 - here:

http://www2.itrc.hp.com/service/patch/patchDetail.do?patchid=PHSS_28843

HTH,
Jeff

[Henk Geurts]

Jeff is right. check your patchlevel...
also see thread :
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=625777


you can check , stop and start the service :
cd /etc/opt/resmon/lbin
./monconfig
in the menu choose E

and /sbin/init.d/diagnostics stop/start

regards
Henk.

[Luis Lino_1]

Hi,
Sorry, but I have HP-UX 11.23 and i can't found the equivalent parch for this version.

Thanks
Luis Lino

[Jeff Schussele · Accepted solution]

Here's the 11.23 patch - PHSS_30236

http://www2.itrc.hp.com/service/patch/patchDetail.do?patchid=PHSS_30236

HTH,
Jeff

[Andrew Merritt_2]

Hi Luis,
You need to check which version of OnlineDiags you have installed. Then I'd recommend upgrading to the latest version, if you don't already have it, and installing the latest patch for that version.

You can see the version id either with 'swlist' or by running cstm. See http://www.docs.hp.com/en/diag/stm/stm_upd.htm#table . C.46.05/HWE0409 is the latest release for 11.23, and PHSS_32210 is the current patch for that.

There is one known problem with ISEE, if you have that installed, that causes these symptoms. Check for the existance of the file /var/stm/config/tools/monitor/rst_disk_em.clcfg

If it exists, change the lines:
DEV_ID:dev_pdev:dev_devclass:dev_inq_vendor:dev_inq_prod:dev_fw_version
DEV_ID:dev_serial_num

to:
DEV_ID:dev_pdev:dev_devclass:dev_inq_vendor:dev_inq_prod:dev_fw_version:dev_serial_num

(all one line).

If that does not fix the problem, you should also look in the /var/opt/resmon/log/api.log file to see if there is anything being logged at the time of failure. Either report back here or contact HP support.

Andrew