Nagios 1.2 and OpenBSD. CGI issues

[Juris Grinbergs]

Hi!

On Wed, 15 Sep 2004 07:38:18 -0700,  
<nagios-users-request at lists.sourceforge.net> wrote:
> [Nagios-users] Nagios 1.2 and OpenBSD.  CGI issues

May, when configuring nagios, you see warning about GD lib-s...
Download it's from http://www.boutell.com/gd/http/gd-2.0.28.tar.gz
Extract, compile, install, and then ...
Try configure, compile and install nagios!!!

Good luck!


-----Original Message-----
From: nagios-users-admin at lists.sourceforge.net
[mailto:nagios-users-admin at lists.sourceforge.net] On Behalf Of nemir  
nemiria
Sent: Wednesday, September 15, 2004 1:50 AM
To: nagios-users at lists.sourceforge.net
Subject: [Nagios-users] Nagios 1.2 and OpenBSD. CGI issues

Hi there!

I have just configured nagios under OpenBSD and it was all great until I  
got
up to the bit where the CGI's try to run.

OpenBSD by default sets up a chrooted environment for httpd under /var/www,
and rather than turn this off I am attempting to make everything happy
within this restriction.

I installed nagios under teh default /usr/local/nagios directory.    I
created the rw directory as directed in the documentation.  I started up
nagios just fine.   I edited my apache config as follows:

<VirtualHost 172.32.30.5>
ScriptAlias /nagios/cgi-bin/ /htdocs/usr/local/nagios/sbin/
<Directory "/htdocs/usr/local/nagios/sbin/">
     AllowOverride AuthConfig
     Options ExecCGI
     Order allow,deny
     Allow from all
</Directory>


Alias /nagios /htdocs/usr/local/nagios/share
<Directory "/htdocs/usr/local/nagios/share">
     Options None
     AllowOverride AuthConfig
     Order allow,deny
     Allow from all
</Directory>
</VirtualHost>



I copied /usr/local/nagios/share and /usr/local/nagios/sbin into
/var/www/htdocs/usr/local/nagios/sbin and
/var/www/htdocs/usr/local/nagios/share.


I pointed my browser to 172.32.30.5/nagios/ and Lo!!   I got myself a  
nagios
page.   Shocked that it all worked so easily,  I tried to check on stuff.

Sadly,  any cgi I click gives me the following output:

"The server encountered an internal error or misconfiguration and was  
unable
to complete your request...."


Tha nagios log just says it started okay.  the messages file jsut has
nothing relevent in it,  just stuff about the checks it is doing.

The apache error_log says:

"[Thu Sep 16 05:53:06 2004] [error] [client 172.32.30.166] Premature end of
script headers: /htdocs/usr/local/nagios/sbin/status.cgi"

a search of the faq revealed something that seemed not relevent about  
suexec
not liking group writable permiossions.  I followed its advice anyway.

Is there an issue with these CGI's not working in a path other than the one
they were compiled for?

regards,

Nemir

-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm



-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
Nagios-users mailing list
Nagios-users at 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

-- 
Juris


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Nagios-users mailing list
Nagios-users at 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