Externals Commands

[Marc Powell]

> -----Original Message-----
> From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> bounces at lists.sourceforge.net] On Behalf Of Hari Sekhon
> Sent: Tuesday, August 01, 2006 7:48 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Externals Commands
> 
> I am having real difficulty getting external commands to work and
don't
> full understand what's going wrong, despite having RTFMing several
times.
> 
> As an example, I log in to the web interface as nagiosadmin via basic
> apache auth successfully as usual. I go to "comments" in the left hand
> pane and enter one for a host but when I click submit, I get the
error:
> 
> 
> "Sorry, but you are not authorized to commit the specified command.
> Read the section of the documentation that deals with authentication
and
> authorization in the CGIs for more information.
> 
> Return from whence you came" <javascript:window.history.go(-2)>


> The apache process is run by the apache user, a member of the apache
> group, so has full perms to the directory and the pipe file
nagios.cmd.
> Nagios is run by nagios who is also a member of the apache group.
> 
> This all looks as it should be according to the docs as far as I can
see.
> 
> 
> What am I missing?

Who does nagios see you logged in as? It will be displayed in the upper
left of every page. If it's '?', verify your htaccess configuration for
the nagios/sbin directory.

--
marc

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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