EMS stopped notification

[Jan Shu]

Greetings.
I don't have EMS notification in syslog.log, nor in the root emailbox any more. It does log in the /var/opt/resmon/log/event.log. I used to have "EMS Monitor Restart due to system reboot" in syslog.log after each reboot, now there's none. What can be wrong? How to fix it?
Thank you.
Jan

[Steven E. Protter]

Look for an error in /etc/rc.log

Then start it manually.

/sbin/init.d/ems start

and/or

/sbin/init.d/emsa start

I'm not sure of the order so play around if you need to.

SEP

[Jan Shu]

Hi SEP, /etc/opt/resmon/lbin/emsagent is running, but it's not logging. Do I need to start it again?
I guess certain EMS setting was modified because we had some hardware problem last 3 months.
Thanks.
Jan

[Steven E. Protter]

I'm a little stumped.

I can find no configuration file.

Have the permissions on the event.log file changed?

SEP

[Michael Tully]

If the daemon is running but not logging anything, you may wish to look at the options you currently have by running /etc/opt/resmon/monconfig Something may have been changed there.

[Jan Shu]

Hi SEP,
-rw-r--r-- 1 root root 233489 Dec 11 15:22 event.log
Jan

[Jan Shu]

Hi Michael; /etc/opt/resmon/lbin/monconfig showed the following

EVENT MONITORING IS CURRENTLY ENABLED.

The current monitor configuration is:
1) Send events generated by all monitors
with severity >= MAJOR WARNING to SYSLOG
2) Send events generated by monitors
/StorageAreaNetwork/events/SAN_Monitor
/storage/events/disk_arrays/AutoRAID
/storage/events/disks/default
/adapters/events/FC_adapter
/adapters/events/TL_adapter
/system/events/core_hw
/connectivity/events/hubs/FC_hub
/connectivity/events/multiplexors/FC_SCSI_mux
/connectivity/events/switches/FC_switch
/system/events/memory
/storage/events/enclosures/ses_enclosure
/storage/events/tapes/SCSI_tape
/system/events/ups
/storage/events/disk_arrays/FC60
/storage/events/disk_arrays/FW_SCSI
/system/events/cpu/lpmc
/adapters/events/scsi123_em
/system/events/system_status
with severity >= INFORMATION to TEXTLOG /var/opt/resmon/log/event.log
3) Send events generated by all monitors
with severity >= MAJOR WARNING to EMAIL root
4) Send events generated by monitors
/storage/events/disk_arrays/High_Availability
with severity > INFORMATION to TEXTLOG /var/opt/resmon/log/event.log
5) Send events generated by monitors
/storage/events/disk_arrays/High_Availability
with severity >= MAJOR WARNING to CONSOLE

[Scot Bean]

EMS is usually started / stopped not by rc scripts but in /etc/inittab.

Check the your /etc/inittab file. Are there 4 ems entries near the bottom, labeled ems1, ems2, ems3, ems4?

The daemon started there is /etc/opt/resmon/lbin/p_client. Is this process running?

[erics_1]

Jan,

It appears that you may have configured EMS to only notify syslog and email root if >= major warning. monconfig is where you can change notification thresholds such as updating syslog >=information message. Just a thought.

Regards,
Eric

[Kevin Wright]

use the /etc/opt/resmon/lbin/send_test_event script.

send_test_event -va disk_em

[Jan Shu]

Hi Scot, p_client is running. and there are 4 ems entries in inittab too.

njuxdb06 # ps -ef|grep p_client
root 1645 1 0 Dec 6 ? 0:57 /etc/opt/resmon/lbin/p_client
root 25329 28042 0 13:31:05 pts/tc 0:00 grep p_client

ems1::bootwait:/sbin/rm -f /etc/opt/resmon/persistence/runlevel4_flag
ems2::bootwait:/sbin/cat /etc/opt/resmon/persistence/reboot_flag
ems3:3456:wait:/usr/bin/touch /etc/opt/resmon/persistence/runlevel4_flag
ems4:3456:respawn:/etc/opt/resmon/lbin/p_client

[Jan Shu]

Eric, I should have assigned you 9 pts, cause you got it right. I compared my 2 HP servers and found out the difference.
Now my question is how to get the correct monconfig back? Pls see attached txt file.

Thanks.
Jan

[Paula J Frazer-Campbell]

Hi

Check your backup tapes, also your ignite recovery tapes and use a tape from when it was correct.

Check history files and the config file itself for last modify time and date.

HTH

Paula

[Andrew Merritt_2]

Jan,
In fact, that notification was an error, it should only happen if a monitor is restarted by p_client due to it aborting or being killed, not at reboot time.

You won't see the message on 11.11, nor in recent versions of OnlineDiags, so I'm guessing you've recently upgraded either the OS or the OnlineDiags.

http://docs.hp.com/hpux/onlinedocs/diag/ems/ems_faq.htm#mon_restart
covers the previous situation, though as I suggest, I believe you won't now see the messages at normal start up.

Since the messages are logged by the EMS Framework, not by a monitor, I don't think that monconfig has any effect on where those messages are logged.

Andrew