I think I found the issue. If I happen to send a reload (HUP) to nagios
while a service check is in progress (fairly easy since my service check is
rather long lived), the reloaded nagios doesn't seem to know about that
service check and so I'll end up with another being scheduled as well as
the o
There isn't a second nagios instance. While I was watching the pollers
spawn, they all led back to the same master nagios instance.
On Thu, Dec 13, 2012 at 2:37 PM, Mike Guthrie wrote:
>
> On 12/13/2012 12:38 PM, Mark Keisler wrote:
>
> I understand that nagios dynamically adjusts service chec
On 12/13/2012 12:38 PM, Mark Keisler wrote:
I understand that nagios dynamically adjusts service check times, but
the puzzling thing is that there is a check that runs every 5 minutes
but then an extra or two in between. And yes, the web interface shows
the next service check as 5 mins out an
I understand that nagios dynamically adjusts service check times, but the
puzzling thing is that there is a check that runs every 5 minutes but then
an extra or two in between. And yes, the web interface shows the next
service check as 5 mins out and yet another runs before that time hits.
On Th
Although some of those start times do seem close together, it's
important to know that the check_interval in Nagios is not necessarily a
hard number. Nagios is continually adjusting and recalculating the check
schedule, so if you need a check to run on a hard 5mn schedule, you
might be better o
I will be out of the office starting 13/12/2012 and will not return until
17/12/2012.
Please contact Tom Barnes if the request is urgent:
Tom Barnes
tom.bar...@ricoh-rpl.com
01952 205362
Regards.
Peter Shankland
TECHNICAL SPECIALIST
IT DEPARTMENT
Rico
I'm running Nagios 3.4.1 on RHEL6. I have an issue where I have a poller
(service check) that is running too often and I am not sure why. I have
"service_check_timeout=180" because I had trouble with the poller running
long. Relevant settings for the service check:
check_period
