Nagios scheduling issues - resolved.

[Edy Gasparini]

OK - thanks for the feedback.

I've actually solved my problem - it wasn't related at all to the interval
settings. What I found was that the submit_check_result script I had was
hanging due to an incorrect IP address (I've setup redundant nagios
servers). As a result, the service checks were taking a _long_ time to
complete.

Would've been nice if the master nagios considered the service check
complete before it submits the result to any slaves ....

Anyway, back to smart settings and max_concurrent_checks=0 and all is good
with the world.

Edy

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net 
> [mailto:nagios-users-admin at lists.sourceforge.net] On Behalf 
> Of Andreas Ericsson
> Sent: Thursday, 28 October 2004 6:22 PM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Nagios scheduling issues
> 
> 
> Edy Gasparini wrote:
> > Guys,
> > 
> > Have got Nagios 1.2 running on RedHat Enterprise Linux 3 
> (RHEL3), with MySQL
> > support/backend. With a small number of hosts/services (say 
> <10), scheduling
> > works as expected, based on check_interval values.
> > 
> > However, now I have 34 hosts and 760 service checks and the 
> scheduling is
> > screwed badly. Checks are being scheduled 60 mins or so apart (with
> > check_interval = 2)
> > 
> > I originally had: 
> > 
> > inter_check_delay_method=s
> > service_interleave_factor=s
> > max_concurrent_checks=0
> > 
> > I've since changed from smart to set figures, as described 
> in the Nagios
> > doco, with no change.
> > 
> > Check latency is currently displaying 
> > 
> > 3206 / 3935 / 3635.479 sec
> > 
> 
> Change the max_concurrent_checks value to 0. If your system load 
> skyrockets, try setting it to 80 or so, or increase the 
> check_interval 
> for your services.
> 
> > Performance info says:
> > <= 1 minute: 0 (0.0%) 
> > <= 5 minutes: 28 (3.6%) 
> > <= 15 minutes: 127 (16.5%) 
> > <= 1 hour: 628 (81.5%) 
> > 
> > Does anyone have a guide on correctly tuning Nagios for 
> large deployments?
> > 
> 
> 34 hosts and 760 service isn't exactly a very large 
> deployment (although 
> a pretty odd one, with +22 services on each monitored node). 
> Go with the 
> 's' setting and let it figure out its own checking delays.
> 
> -- 
> Andreas Ericsson                   andreas.ericsson at op5.se
> OP5 AB                             www.op5.se
> Lead Developer
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> 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
> 



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
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