duplicate service alerts

[Jason Lancaster]

I should probably let everyone know that two processes of nsca are not
running.

Additionally, if I disable the external commands file and have nsca dump to
a dump log, entries are only being written once.

Jason
----- Original Message ----- 
From: "Jason Lancaster" <jlancaster at affinity.com>
To: <nagios-users at lists.sourceforge.net>
Sent: Wednesday, June 18, 2003 10:23
Subject: duplicate service alerts


> I've been experiencing some strange behavior in the nagios.log and was
> hoping I could have everyone's thoughts on this situation. My nagios.log
> contains duplicate service alerts for most external commands. For example:
> [1055945454] EXTERNAL COMMAND:
> PROCESS_SERVICE_CHECK_RESULT;host.com;Memory;0;Memory OK - 434 MB free
> [1055945231] SERVICE ALERT: host.com;Memory;OK;HARD;2;Memory OK - 434 MB
> free
> [1055945231] SERVICE ALERT: host.com;Memory;OK;HARD;2;Memory OK - 434 MB
> free
>
> Not all services do this and this is only with regards to external
commands
> (passive service checks) sent through nsca. There is only one nagios core
> process running. I cannot duplicate this unless I send results through
> nsca -- writing to the external commands file by hand registers only one
> service alert.
>
> Does anyone have any ideas on why nagios might be processing service
alerts
> sent through nsca twice? I figure this is probably eating resources on my
> system and would like to resolve it.
>
> Thanks!
> Jason Lancaster
>



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null