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 off using cron, and then pushing the result to Nagios
passively.
With that said, access the service details for this service. When new
results come in does the scheduler set the Next Check 5mn out as expected?
On 12/13/2012 9:43 AM, Mark Keisler wrote:
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 24x7
max_check_attempts 1
normal_check_interval 5
retry_check_interval 5
I also set up a tracking logger in the poller to record "timestamp PID
started by PPID : Poll [Start|End] of poller"
2012-12-12_12:26:38 19448 started by 19442 : Poll Start of poller
2012-12-12_12:27:13 19448 started by 19442 : Poll End of poller
2012-12-12_12:28:14 19931 started by 19930 : Poll Start of poller
2012-12-12_12:30:14 19931 started by 19930 : Poll End of poller
2012-12-12_12:31:37 20467 started by 20460 : Poll Start of poller
2012-12-12_12:33:15 20949 started by 20946 : Poll Start of poller
2012-12-12_12:33:15 20467 started by 20460 : Poll End of poller
2012-12-12_12:33:41 20949 started by 20946 : Poll End of poller
2012-12-12_12:36:38 21483 started by 21478 : Poll Start of poller
2012-12-12_12:38:14 21971 started by 21964 : Poll Start of poller
2012-12-12_12:39:17 21483 started by 21478 : Poll End of poller
2012-12-12_12:39:18 21971 started by 21964 : Poll End of poller
2012-12-12_12:41:38 22500 started by 22492 : Poll Start of poller
2012-12-12_12:42:19 22500 started by 22492 : Poll End of poller
2012-12-12_12:43:14 23003 started by 22999 : Poll Start of poller
2012-12-12_12:45:20 23003 started by 22999 : Poll End of poller
2012-12-12_12:46:37 23540 started by 23535 : Poll Start of poller
2012-12-12_12:48:14 24025 started by 24024 : Poll Start of poller
2012-12-12_12:48:20 23540 started by 23535 : Poll End of poller
2012-12-12_12:48:41 24025 started by 24024 : Poll End of poller
2012-12-12_12:51:38 24558 started by 24554 : Poll Start of poller
2012-12-12_12:53:14 25044 started by 25041 : Poll Start of poller
2012-12-12_12:54:35 25044 started by 25041 : Poll End of poller
As you can see, I start to get overlapping pollers. I don't understand
why this would happen. Any hints or clues?
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
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
--
Mike Guthrie
Technical Team
___
Nagios Enterprises, LLC
Email: mguth...@nagios.com
Web: www.nagios.com
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
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
