> Thanks for the response. Below are entries that are made in > ssl_access_log: > > When I click on "Re-schedule the next check of this service", it creates > the following entry: > > 139.222.121.213 - [email protected] [12/Jul/2011:11:03:10 +0100] "GET > /nagios/cgi-bin/cmd.cgi?cmd_typ=7&host=cn001&service=cpu HTTP/1.1" 200 > 3143 > > When I click on the "commit" button after clicking the "force check" tick > box, it then creates the following two entries: > > 139.222.121.213 - - [12/Jul/2011:11:03:14 +0100] "POST > /nagios/cgi-bin/cmd.cgi HTTP/1.1" 401 490 > 139.222.121.213 - [email protected] [12/Jul/2011:11:03:14 +0100] "POST > /nagios/cgi-bin/cmd.cgi HTTP/1.1" 200 1314 > > It's not clear what the URL is.
OK, so, it's not a GET, it's a POST. I'll let someone more familiar with that comment... Doing this via the web interface seems cumbersome, but it might be possible to do it via the command file somehow. Not like that's much better... http://old.nagios.org/developerinfo/externalcommands/commandlist.php http://nagios.sourceforge.net/docs/nagioscore/3/en/extcommands.html Good luck! Benny -- "You were doing well until everyone died." -- "God", Futurama ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Nagios-users mailing list [email protected] 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
