On 25 May 2010, at 12:16, Andrew Hall wrote:
On 2010-05-25 08:23, Ton Voon wrote:
As your Nagios doesn't have this extra logic, you can just disable
the
max_concurrent_checks by setting it to 0.
Thanks for the tip but I'd rather test increasing it in steps right
now as it's a slight concern we're hitting 50 concurrent checks as it
is. Setting it to zero could be a recipe for disaster :-)
I think most instances of Nagios use 0 (as it is the default), so I
don't think it will necessarily be that bad.
From my previous investigations, it looks like the value is increment
when a new check is set to run, but not decremented until the result
has been reaped. This means that the plugin to do the check could have
finished, but because Nagios has not read the result yet, it still
counts towards the total.
We triggered the situation by doing a mass recheck of lots of things
at once - Nagios schedules all those at the same time.
Ton
_______________________________________________
Opsview-users mailing list
Opsview-users@lists.opsview.org
http://lists.opsview.org/lists/listinfo/opsview-users
