EMS fails

[A. Daniel King_1]

Hi, folks.

I've got an EMS issue on a new configuration. I see that diagmond is running as well as emsagent.

I can't seem to find event.log! Also, e-mails which I would expect to get are not appearing.

I have created a catastrophic event (i.e., removed a fiber cable between the machine and some disk), which I would expect to see from EMS.

In the same location as the log should be (/var/opt/resmon/log), I see client.log which contains:

Event 2505 occurred at Wed Apr 2 13:08:08.101491 2003
Process ID: 2967 (/etc/opt/resmon/lbin/p_client) Log Level: Error
update_monitors: socket open failed

And other similar messages. Any ideas?

A note as background, I did copy over the configuration files (/var/stm/config/tools/monitor) from another machine (after backup). I suspect I've got some cleanup to do there, but I was wondering if anyone had specific thoughts. This is the process of upgrading from 11.0 to 11i, so there may be something there, too.

Thanks.

[erics_1 · Accepted solution]

Daniel,

I would advise taking a look through TKB document # KBRC00003773 for possible troubleshooting steps and let us know your results.

Regards,
Eric

[Steven E. Protter]

Here is a shot in the dark.

http://search.hp.com/redirect.html?url=http%3A//forums.itrc.hp.com/cm/QuestionAnswer/1,,0x6dc053921f1ad5118fef0090279cd0f9,00.html&qt=update_monitors%3A+%2Bsocket+%2Bopen+%2Bfailed&hit=1

That thread has the same error text but I don't understand it.

SEP

[castro_2]

Probe set_fixed -l.
To have created a catastrophic event you can use /etc/opt/resmon/lbin/send_test_event
For example /etc/opt/resmon/lbin/send_test_event dm_stape.
You can re-start EMS with /etc/opt/resmon/lbin/monconfig
Good Lock

[A. Daniel King_1]

Eric,

You got me close enough to realize that I had registrar commented out in /etc/inetd.conf. This seems to have been the problem. Thank you!

Steven,

I can't tell how this relates, but thanks anyway.

Castro,

Good information. I'll be digging into set_fixed for more information soon.

I am happily receiving alerts now.

[Ranjeet A.]

Daniel,
I am in need of the DOC:KBRC00003773. But not able to access the TKB document # KBRC00003773. Will you pls attatch the same here.

Thanks
Ranjeet