Re: [Nagios-users] Scheduling Downtime Not Authorized?

2006-07-22 Thread Marc Powell


> -Original Message-
> From: [EMAIL PROTECTED] [mailto:nagios-users-
> [EMAIL PROTECTED] On Behalf Of Hari Sekhon
> Sent: Thursday, July 20, 2006 12:21 PM
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] Scheduling Downtime Not Authorized?
> 
> I'm really pleased with my nagios 1.4.1 installation so far, I have it
> monitoring loads of servers, but now I feel like expanding beyond the
> basics and am trying to schedule downtime for a couple of hosts since
> they are down and will be for some time.
> 
> However I get the following 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.
> 
> I'm logged in as nagiosadmin and have the following lines in
nagios.cfg
> 
> check_external_commands=1
> command_check_interval=-1
> command_file=/var/nagios/rw/nagios.cmd
> 
> ll /var/nagios/rw/nagios.cmd
> prw-rw 1 nagios apache 0 Jul 20 18:12 /var/nagios/rw/nagios.cmd|
> 
> 
> In cgi.cfg I have:
> 
> use_authentication=1
> authorized_for_system_information=nagiosadmin
> authorized_for_configuration_information=nagiosadmin
> authorized_for_system_commands=nagiosadmin
> authorized_for_all_services=nagiosadmin
> authorized_for_all_hosts=nagiosadmin
> authorized_for_all_service_commands=nagiosadmin
> authorized_for_all_host_commands=nagiosadmin
> 
> I restarted nagios with those settings but it still won't let me
> schedule downtime. Does anybody know why?

In the upper left status box on every page does it show you 'Logged in
as nagiosadmin'? If not, verify your .htaccess configuration in your
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@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


[Nagios-users] Scheduling Downtime Not Authorized?

2006-07-20 Thread Hari Sekhon
I'm really pleased with my nagios 1.4.1 installation so far, I have it 
monitoring loads of servers, but now I feel like expanding beyond the 
basics and am trying to schedule downtime for a couple of hosts since 
they are down and will be for some time.

However I get the following 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.

I'm logged in as nagiosadmin and have the following lines in nagios.cfg

check_external_commands=1
command_check_interval=-1
command_file=/var/nagios/rw/nagios.cmd

ll /var/nagios/rw/nagios.cmd
prw-rw 1 nagios apache 0 Jul 20 18:12 /var/nagios/rw/nagios.cmd|


In cgi.cfg I have:

use_authentication=1
authorized_for_system_information=nagiosadmin
authorized_for_configuration_information=nagiosadmin
authorized_for_system_commands=nagiosadmin
authorized_for_all_services=nagiosadmin
authorized_for_all_hosts=nagiosadmin
authorized_for_all_service_commands=nagiosadmin
authorized_for_all_host_commands=nagiosadmin

I restarted nagios with those settings but it still won't let me 
schedule downtime. Does anybody know why?

-
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@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