Our setup is with Apache2. The binary characters appearing in the right-hand frame of the Nagios web interface must be un-interpreted CGI. This seems to be Apache2 related, or can it be explained by the fact that no plugins are installed?
Gerhard
As for the issue with Apache2 I haven't actually tried setting up on Apache2 at this time; however I would hazzard a guess that Nagios web interface should operate whether you had plugins or not... Nagios merely operates as the framework controlling the execution of plugins and displaying the results... As such it should operate fine prior to the plugins being installed just not really able to check anything... Currently both of my production Nagios machines are runnin Apache 1.x and Nagios 1.1 rebuilt for woody/stable... I'll see about installing Apache2 on my workstation runnin unstable and try to work on the issues regarding the Apache2 setup... Regards, Jeremy
Hi Gerhard, hi Jeremy,
I just came across the same problem using nagios-text 1.1-10 on apache2-mpm-prefork 2.0.48-4
As a quick fix I mapped the cgi-filename extension to the correct handler.
In /etc/apache/apache2.conf:
# To use CGI scripts outside /cgi-bin/: # AddHandler cgi-script .cgi
I don't know how wise/safe it is to do that globally, though.
Then of course the handler needed to be included into the apache2-configuration.
As root:
# > a2enmod cgi
An Apache2-reload brought up some new errors but these were fixed by simply customizing nagios :-)
Regards, Joerg
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
