Page 1 of 1

Nagios Core 4.2.1, Debian 8.4 install problem

Posted: Fri Oct 21, 2016 1:13 pm
by nickgeo
Trying to get Nagios 4.2.1 working on Debian 8.4 "Jessie". Nagios is built from source.
The doc advises using the Fedora quickstart as a guide for installation on "other" linuxes, modified appropriately, which I've tried to do. The make-generated httpd.conf does not get installed in the appropriate directory so I moved it to /etc/apache2/sites-enabled as nagios.conf, and I can display the Nagios home page. But there are 2 problems. Despite that nagios is indeed running, the web page reports that it is not running. And the various Nagios CGIs get downloaded instead of executed. I'm not good enough with Apache2 to fix these problems easily, so I wonder if someone could give me a couple of pointers on what apache2 config needs fixing.

Re: Nagios Core 4.2.1, Debian 8.4 install problem

Posted: Fri Oct 21, 2016 1:27 pm
by rkennedy
Which guide were you following for installation? It may be worth trying our official guide, which has instructions specifically for Debian. It can be found here - https://support.nagios.com/kb/article.php?id=96

Re: Nagios Core 4.2.1, Debian 8.4 install problem

Posted: Fri Oct 21, 2016 2:25 pm
by nickgeo
Thanks! The "a2enmod cgi" fixed almost everything. But the "Services" entry on the left-side pane under "Current Status" still downloads status.cgi instead of executing it. All of the other entries now appear to work fine. So what's different about status.cgi?

Re: Nagios Core 4.2.1, Debian 8.4 install problem

Posted: Fri Oct 21, 2016 2:47 pm
by nickgeo
A little more info. The "downloads status.cgi instead of running it" problem appears to only occur using chromium. Other browsers (chrome, firefox) do just fine. Again, this is only a problem with the "Services" entry under "Current Status", all of the other screens seem to work well.

Re: Nagios Core 4.2.1, Debian 8.4 install problem

Posted: Mon Oct 24, 2016 12:01 pm
by rkennedy
This is strange, a few things for you to run through -

Could you run a tail -f /var/log/httpd/*_log, and then try to access the status.cgi once again?

Also, what are the permissions on it? ls -la /usr/local/nagios/sbin/status.cgi

It sounds like chromium may not know how to handle CGI files, or the server isn't serving them properly. Could you attach the CGI file it downloads for us to review?