Hi All
Yes, it's me, talking to myself. I found that cmd.cgi wasn't working any more. I couldn't schedule any more downtimes. After restarting Nagios, things seem to be back on track. I'm thinking that if cmd.cgi wasn't working, perhaps the downtime notification logic wasn't working either. This isn't the solution, but a clue. I have encountered this problem before with cmd.cgi in Nagios v1.2. I'm not sure if it's a browser problem (javascript) or if it's caused by too many downtimes scheduled at one time... Anyway, the restart has solved it till the next time we schedule downtimes. If anyone has any suggestions or ideas, it would be greatly appreciated. - David Schlecht (dschl) ----------------------- This thread is located in the archive at this URL: http://www.nagiosexchange.org/nagios-users.34.0.html?&tx_maillisttofaq_pi 1[showUid]=13895 ------------------------------------------------------- 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://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ 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