Restart event notification without restarting system

[Carles Viaplana]

Hello,

We shutdown our system 1 week ago and after reboot it we received a mail restart event notification as usual.

But one week after reboot we're still receiving mails about restart event.

Why does system sent restart event notification mails without restarting or a week after reboot?

Note that we can't ignore message as we already did with some other messages or systems.

Thanks in advance for your help.
Regards,

Carles

[RAC_1]

what is the exact message?? What does mail.log file say??

[Devender Khatana · Accepted solution]

Hi Charles,

#/sbin/init.d/diagnostics stop
&
#/sbin/init.d/diagnostics start

HTH,
Devender

[Steven E. Protter]

Shalom Carles,

Either the system rebooted without your consent or the diagnostics are broken.

See that the patching for Online Diagnostics are patched and up to date.

Check the date of the files in /var/adm/syslog

If they correspond with the message, your system booted itself. A power supply issue can cause this. If not, look into software problems with EMS/Online Diagnostics.

SEP

[Carles Viaplana]

Message we receive is as follow:

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Thu Dec 1 18:07:14 2005

paris sent Event Monitor Restart information:

Title: disk_em
Command: /usr/sbin/stm/uut/bin/tools/monitor/disk_em
Vendor: Hewlett-Packard Company
Version: B.01.01
Monitor PID: 20208

Resources currently monitored:
/storage/events/disks/default/0_0_1_1.2.0
/storage/events/disks/default/0_0_2_0.2.0
/storage/events/disks/default/0_0_2_1.2.0

>---------- End Event Monitoring Service Event Notification ----------<

Not system hasn't been reboot at least for a week.

Regards,

Carles

[Carles Viaplana]

Hello,

Thanks for your help.

I executed uptime command and system is up for more than 10 days:

# uptime
9:47am up 10 days, 1:23, 1 user, load average: 1.50, 1.45, 1.44
#

So I don't believe system was rebooted by itself.

Regards,

Carles

[Andrew Merritt_2]

Hi Carles,
Assuming it is only disk_em that is reporting the messages, that is indicating a problem just with the disk_em monitor; the monitor is dying for some reason and being restarted. What version of OnlineDiags do you have installed? There were some problems with disk_em that would lead to such a symptom that have been fixed in the current versions.

Andrew

[Carles Viaplana]

After stop event notification service messages stop to arrive.

Thanks to all for your help.
Regards,

Carles

[Andrew Merritt_2]

Hi Carles,
Yes, disabling the delivery of notifications will stop them arriving! That's only a temporary work-around; the monitor is there for a reason and if it's dying then you need to find out why and get it going again.

How often are you seeing the messages, and what version of the OnlineDiags do you have?

Do you have ISEE installed? If so, read on.

Check the /etc/opt/resmon/log/api.log. Is there something like the following being logged:

-------------------Start Event--------------------
User event occurred at Mon Jan 24 01:46:52.193736 2005
Process ID: 2733 (/usr/sbin/stm/uut/bin/tools/.../disk_em) Log Level: Error
Tool is exiting due to receipt of an unexpected signal (11).

SIGSEGV (11) signal indicates a segmentation violation.

Possible Causes/Recommended Action:

Internal Application error. Tool attempted to reference an invalid address.
Usually a NULL or bad pointer.
-------------------End Event----------------------

-------------------Start Event--------------------
Event 170 occurred at Mon Jan 24 01:46:52.202622 2005
Process ID: 2733 (/usr/sbin/stm/uut/bin/tools/.../disk_em) Log Level: Panic
lookup_obj_desc: Cannot find description of object 0
-------------------End Event----------------------

-------------------Start Event--------------------
Event 51 occurred at Mon Jan 24 01:46:52.202917 2005
Process ID: 2733 (/usr/sbin/stm/uut/bin/tools/.../disk_em) Log Level: Error
rm_destroy: Invalid object type (0)
-------------------End Event----------------------

If so, modify the /var/stm/config/tools/monitor/rst_disk_em.clcfg file. Current Entry
in rst_disk_em.clcfg:

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

Needs to be modified to:


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

(all one line).

This is fixed in later versions of ISEE, so installing the latest version should fix the problem too.

Andrew