[Nagios-users] socket time out

2009-06-22 Thread Param Srinivas
Hello guys,

We are facing problem with one windows server that has socket time out error
for a long time.
 NC_NET is installed on this server. C drive is showing socket timeout
after 20 sec error.

Can any body tell why is this hapenning ?
-- 
Best Regards
Param S
--
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org___
Nagios-users mailing list
Nagios-users@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

Re: [Nagios-users] socket time out

2009-06-22 Thread Param Srinivas
Connectivity is excellent, check_ping works fine. No firewall and DNS -
using host by ip only.

Also for the socket time out error tried increasing the time by 50 sec but
still the same.

Now NC_NET when installed , it requires few changes in its configuration
right ? Like in active_ip_accept_list  included the ip address of the Nagios
server , and changing the startup.cfg file by commenting out port and
ipaddress.

Note :  When opening the config files for NC_NET i select open as word pad

Is this right ?

There is not proper documentation on how to troubleshoot issues with NC_NET


Thanks
Param
On Mon, Jun 22, 2009 at 11:31 AM, Mathew Walker lmw94...@hotmail.comwrote:

 sounds like a possible connectivity issue between the boxes...

 check connectivity, services, firewall settings, and DNS (if using host
 addresses vs. IPs).  that's my usual run down of issues.

 --
 Mat W. - http://www.techadre.com



 --
 Date: Mon, 22 Jun 2009 11:20:25 -0400
 From: prmsr...@gmail.com
 To: nagios-users@lists.sourceforge.net
 Subject: [Nagios-users] socket time out


 Hello guys,

 We are facing problem with one windows server that has socket time out
 error for a long time.
  NC_NET is installed on this server. C drive is showing socket timeout
 after 20 sec error.

 Can any body tell why is this hapenning ?
 --
 Best Regards
 Param S

 --
 Bing™ brings you maps, menus, and reviews organized in one place. Try it
 now.http://www.bing.com/search?q=restaurantsform=MLOGENpubl=WLHMTAGcrea=TEXT_MLOGEN_Core_tagline_local_1x1




-- 
Best Regards
Param S
--
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org___
Nagios-users mailing list
Nagios-users@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

[Nagios-users] notification

2009-06-19 Thread Param Srinivas
  Host Status:   UP
 (for 0d 19h 19m 15s) Status Information: FPING OK - 65.106.232.209
(loss=0%, rta=41.00 ms) Performance Data: loss=0%;80;100;0;100
rta=0.041000s;2.00;5.00;0.00 Current Attempt: 1/3  (HARD
state) Last
Check Time: 06-19-2009 10:13:39 Check Type: ACTIVE Check Latency /
Duration: 56.436 / 2.537
seconds Next Scheduled Active Check:   06-19-2009 10:14:47 Last State
Change: 06-18-2009 14:58:37 Last Notification: N/A (notification 0) Is This
Host Flapping? N/A In Scheduled Downtime?   NO
 Last Update: 06-19-2009 10:17:38  ( 0d 0h 0m 14s ago)

As per above the host is scheduled to check every 1 min. The parameter in
use is check_interval =1   also retry_interval=1
Then when the host went down the  View alert history for this host  at the
left corner says :


[image: Host Down][06-18-2009 14:38:40] HOST ALERT:
benroutermr;DOWN;HARD;3;FPING CRITICAL - 65.106.232.209 (loss=100% )
[image: Host Down][06-18-2009 14:32:56] HOST ALERT:
benroutermr;DOWN;SOFT;2;FPING CRITICAL - 65.106.232.209 (loss=100% )
[image: Host Down][06-18-2009 14:32:40] HOST ALERT:
benroutermr;DOWN;SOFT;1;FPING CRITICAL - 65.106.232.209 (loss=100% )
Why is it not checking every minutes when retry_interval=1? ?


Because of this notification is getting delayed , i want the notification to
be sent 3 min after the host is down.

-- 
Best Regards
Param S
--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects___
Nagios-users mailing list
Nagios-users@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

Re: [Nagios-users] notification

2009-06-19 Thread Param Srinivas
Yes , there is a lot of checks going on.  There are like 750 hosts with a
minimum of about 6 to 7 services checks.
Could this be because  SERVICE INTER-CHECK DELAY METHOD   HOST INTER-CHECK
DELAY METHOD are set to smart calculation  ?

On Fri, Jun 19, 2009 at 11:23 AM, Mat W lmw94...@hotmail.com wrote:

 are there ALOT of checks going on?  eg, when it went down, was there a
 backlog of checks that were firing off?

 for example if I have a network issue to a site, suddenly i have 100s of
 checks firing off in Xmin intervals.

 Check the logs?  up the debug level?

 --
 Mat W. - http://www.techadre.com



 --
 Date: Fri, 19 Jun 2009 10:31:24 -0400
 From: prmsr...@gmail.com
 To: nagios-users@lists.sourceforge.net
 Subject: [Nagios-users] notification


   Host Status:   UP
  (for 0d 19h 19m 15s) Status Information: FPING OK - 65.106.232.209
 (loss=0%, rta=41.00 ms) Performance Data: loss=0%;80;100;0;100
 rta=0.041000s;2.00;5.00;0.00 Current Attempt: 1/3  (HARD
 state) Last Check Time: 06-19-2009 10:13:39 Check Type: ACTIVE Check
 Latency / Duration: 56.436 / 2.537 seconds Next Scheduled Active Check:   
 06-19-2009
 10:14:47 Last State Change: 06-18-2009 14:58:37 Last Notification: N/A 
 (notification
 0) Is This Host Flapping? N/A In Scheduled Downtime?   NO
  Last Update: 06-19-2009 10:17:38  ( 0d 0h 0m 14s ago)

 As per above the host is scheduled to check every 1 min. The parameter in
 use is check_interval =1   also retry_interval=1
 Then when the host went down the  View alert history for this host  at
 the left corner says :


 [image: Host Down][06-18-2009 14:38:40] HOST ALERT:
 benroutermr;DOWN;HARD;3;FPING CRITICAL - 65.106.232.209 (loss=100% )
 [image: Host Down][06-18-2009 14:32:56] HOST ALERT:
 benroutermr;DOWN;SOFT;2;FPING CRITICAL - 65.106.232.209 (loss=100% )
 [image: Host Down][06-18-2009 14:32:40] HOST ALERT:
 benroutermr;DOWN;SOFT;1;FPING CRITICAL - 65.106.232.209 (loss=100% )
 Why is it not checking every minutes when retry_interval=1? ?


 Because of this notification is getting delayed , i want the notification
 to be sent 3 min after the host is down.

 --
 Best Regards
 Param S

 --
 Microsoft brings you a new way to search the web. Try Bing™ 
 nowhttp://www.bing.com/?form=MFEHPGpubl=WLHMTAGcrea=TEXT_MFEHPG_Core_tagline_try+bing_1x1




-- 
Best Regards
Param S
--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects___
Nagios-users mailing list
Nagios-users@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

Re: [Nagios-users] Time diference in Alert History

2009-06-16 Thread Param Srinivas
Thanks for your reply,

But by the way even though this is thoretically posible , practically this
aint working. The recheck interval is varying . Is this because of huge
number of host being monitored. ?  We have around 700 hosts being monitored.

On Tue, Jun 16, 2009 at 1:26 PM, Mat W lmw94...@hotmail.com wrote:

 that would be the rety interval setting for your check I believe.

 for example...

 check_interval  5   ; Actively check
 the host every 5 minutes
 retry_interval  1   ; Schedule host
 check retries at 1 minute intervals

 --
 Mat W. - http://www.techadre.com



 --
 Date: Tue, 16 Jun 2009 13:08:23 -0400
 From: prmsr...@gmail.com
 To: Nagios-users@lists.sourceforge.net
 Subject: [Nagios-users] Time diference in Alert History


 Hi Nagios Experts,

 Below was the informatios i got from clicking  view alert history for the
 host :

 [05-11-2009 16:46:57] HOST ALERT: benfwca;DOWN;HARD;5;FPING CRITICAL -
 (loss=100% )
 [05-11-2009 16:43:36] HOST ALERT: benfwca;DOWN;SOFT;4;FPING CRITICAL -
 (loss=100% )
 [05-11-2009 16:40:30] HOST ALERT: benfwca;DOWN;SOFT;3;FPING CRITICAL
 -(loss=100% )
 [05-11-2009 16:37:30] HOST ALERT: benfwca;DOWN;SOFT;2;FPING CRITICAL -
 (loss=100% )
 [05-11-2009 16:34:16] HOST ALERT: benfwca;DOWN;SOFT;1;FPING CRITICAL -
 (loss=100% )
 here the max_check_attepts   =  5

 If you see above the time difference between SOFT 1 state and SOFT 2 state
 is approx = 3 min.  Is it possible to make it 1 min.

 Please help me find the parameter that controls that time.

 Thanks in adv

 Param

 --
 Microsoft brings you a new way to search the web. Try Bing™ 
 nowhttp://windowslive.com/explore?ocid=TXT_TAGLM_WL_BR_life_in_synch_062009

--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables unlimited
royalty-free distribution of the report engine for externally facing 
server and web deployment.
http://p.sf.net/sfu/businessobjects___
Nagios-users mailing list
Nagios-users@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