Comments on: Using nagxmlstatus.cgi http://nagstatus.com/pages/using-nagxmlstatuscgi Windows Sidebar/Desktop Gadget Fri, 22 Mar 2013 21:26:45 +0000 hourly 1 http://wordpress.org/?v=3.0.4 By: Jouko Markkanen http://nagstatus.com/pages/using-nagxmlstatuscgi/comment-page-1#comment-9812 Jouko Markkanen Fri, 22 Mar 2013 21:26:45 +0000 http://www.markkanen.net/wptest/articles/using-nagxmlstatuscgi#comment-9812 The HTTP status code 500 indicates that your server could not run the nagxmlstatus.cgi script for some reason. Things that can cause this include missing Perl modules (see the instructions for a list of requirements), http server misconfiguration, incorrect file permissions etc. I'd start by checking your http server's error logs for more information on what causes this error. The HTTP status code 500 indicates that your server could not run the nagxmlstatus.cgi script for some reason. Things that can cause this include missing Perl modules (see the instructions for a list of requirements), http server misconfiguration, incorrect file permissions etc. I’d start by checking your http server’s error logs for more information on what causes this error.

]]> By: Brodey Dover http://nagstatus.com/pages/using-nagxmlstatuscgi/comment-page-1#comment-9494 Brodey Dover Thu, 07 Mar 2013 23:25:48 +0000 http://www.markkanen.net/wptest/articles/using-nagxmlstatuscgi#comment-9494 I get a 500 Internal Server error when using this: http://nagios.oscar-emr.net/nagios3/cgi-bin/nagxmlstatus.cgi?node=all&elem=all I get a 500 Internal Server error when using this:

http://nagios.oscar-emr.net/nagios3/cgi-bin/nagxmlstatus.cgi?node=all&elem=all

]]>