Small problem with forced service checks on 2.0rc2

[Steve Johnson]

Hi,

I currently have a setup running 2.0rc2. When I go through the web 
interface and schedule forced checks, this works fine until I hit the 
max_check_attempts and the service falls into a hard state. After that, 
even if I schedule a new check, I see the check request in the log file, 
but the check is never performed. This means that the only way to get it 
to test again is to wait until its next officially scheduled check.

I had asked in one of the IRC channels and was told that this was not 
supposed to be the case. Is this something related to 2.0rc2 or 
something I should not be experiencing at all, even on this version? If 
so, any ideas on what could be wrong?

Thanks a lot,
Steve Johnson


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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