Connection refused/socket time out

[keshav murthy]

Can somebody help please.
Cheers
Kesava

On Mon, Nov 9, 2009 at 8:04 PM, keshav murthy <nkeshav12 at gmail.com> wrote:

> Hey guys,
>
> My environment
>
>
>    - 2 nagios servers
>    - 1 nagios server monitoring more than 920 clients and another more
>    than 700 clients
>    - Clients are both Windows and Unix servers
>    - *No firewalls*.
>    - Added both the nagios server's IP address on all the client's config
>    file.
>
> Issue
>
>    - Occasionally we get connection refused sometimes and Socket timeout
>    sometimes.
>    - During such times, it generates CRITICAL alert and our ticketing
>    system generates lots of tickets
>
> Assumptions
>
>    - Network slowness between nagios server and client.
>    - Client takes more time to respond to the check and nrpe timeouts.
>    - NRPE dies on the nagios server.
>
>
> Clarification needed
>
>    - What are the various causes for these alerts? (are the assumptions
>    correct, if wrong please clarify.)
>    - Is it possible to change them as "Warning"?
>    - If yes for above, how?
>
> Regards
> Kesava
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20091110/b52a5d38/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
-------------- next part --------------
_______________________________________________
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