On Fri, Jan 22, 2010 at 14:13, Scott Lambert <lamb...@lambertfam.org> wrote:
> On Fri, Jan 22, 2010 at 11:03:49AM -0800, Kurt Buff wrote:
>> I'm trying to install nagios on freebsd, and can't get to the point of
>> getting lynx on the host to talk to http://192.168.8.20/nagios - I get
>> a 403 "You don't have permission to access /nagios/ on this server."
>>
>> I'm beating my brains out on this one, and don't know what I'm doing
>> wrong. I'm sure it's something really simple I'm overlooking, because
>> just browsing http://192.168.8.20 gets a response. Unfortunately there
>> isn't a quick install guide for freebsd, so I'm having to do some
>> translation of the docs.
>>
>> Any help much appreciated.
>
> Rather than guessing, you might want to take a look at what Apache
> thinks is wrong:
>
> Access the page and then:
>
> sudo tail /var/log/httpd-error.log
>
> It should pretty much tell you what is wrong.
>
> Is lynx asking you for a username and password?
>
> Is there some reason you didn't follow exactly the instructions
> suggested by the pkg-message for the nagios port with regard to the
> Apache configuration?  I don't see anything particularly wrong with your
> config, but it may be needlessly over complex.
>
> I believe in getting things working according how the port maintainer
> suggests. The port maintainers tend to do a good job of handing you a
> good basic configuration which works.
>
> Once that works, I make the changes needed for my site one step at a
> time, testing each change individually.
>
> --
> Scott Lambert                    KC5MLE                       Unix SysAdmin
> lamb...@lambertfam.org

Just so you know, the only things I modifed in the default httpd.conf
were the following  parameters:

     Listen is now 'Listen 192.168.8.20:80'
     ServerAdmin is now 'ServerAdmin ift...@example.com
     ServerName is now 'ServerName loki.example.com:80'

The page does indeed ask for auth when configured with the stanzas I listed.

I've been examining /var/log/httpd-error.log, and found the following,
with the configuration I first listed:

     [client 192.168.8.20] Directory index forbidden by Options
directive: /usr/local/www/nagios/

Following your suggestion, I have removed those stanzas, and replaced
them with the ones I found in
/usr/ports/net-mgmt/nagios/work/pkg-message, and the results are
slightly different. Namely, I get a 404 message saying

     The requested URL /nagios was not found on this server.

and /var/log/httpd-error.log says

     [error] [client 192.168.8.20] File does not exist:
/usr/local/www/apache22/data/nagios

If I then add

     Alias /nagios /usr/local/www/nagios/

to the end of httpd.conf, I again get an auth prompt in lynx, and
again I get the error in httpd-error.log:

     [client 192.168.8.20] Directory index forbidden by Options
directive: /usr/local/www/nagios/


So, I'm led to believe that I'm making a bonehead error in httpd.conf,
but I can't figure it out.

Kurt

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Nagios-users mailing list
Nagios-users@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

Reply via email to