New Alert showing up in monitor daemon log

[Kevin Scantlan]

We had the following log entry show up in a monitor daemon log:

[aler:aler:INFO/0:  hcimonitord:02/28/2012 07:29:44] New alert #51:

{VALUE status} {SOURCE all} {MODE delta} {WITH -1} {COMP diff} {FOR once} {ACTION status}

I understand that if you update the alerts and save them back, it reloads all the alerts and the log shows “New Alert #nn” for each alert.   Also if you bounce the monitor daemon you will get the same thing.  However, in the case, you do get all the alerts.  Also, we only have 14 alerts for this site, not 51.  Plus, if you look at this entry, it alert itself looks like a generic alert.  But it’s not in the alert file at all.

This coincides timewise with us having to refresh our monitor as it showed the processes and threads as all being dead.

Topic

[Bob Richardson]

Greetings,

We are running both the 5.7.2.0 and 5.8.5.0 engines and have observed that you will get an alert action firing for the default.alrt file reload event itself.

This may be what you are seeing here:  the monitord daemon program resets

alerts when it discovers that the alert file itself has changed.

Perhaps your version of the Integrator is older and not as clear in its informational message here as later releases?

My guess.

You can always open a CASE with Lawson online and investigate it to confirm

what is stated in this Forum by individuals like myself.

Good luck, good hunting!

[Author]

Replies