check_external_commands option

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Sxan
> Sent: Friday, July 08, 2005 9:36 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] check_external_commands option
> 
> 
> Hey all,
> 
> I have a question regarding the check_external_commands option in the
> nagios.cfg
> file. Basically, I tried to schedule some downtime, saw that I needed
to
> have that
> option enabled, so I went into the nagios.cfg file and changed the 0
to a
> 1 for that line
> like it is below:
> 
> check_external_commands=1
> 
> I saved the .cfg and now when I try and restart nagios, it won't
start. I
> just get:
> 
> honda:/usr/local/nagios/etc # sh /etc/init.d/nagios restart
> Running configuration check...done
> Stopping network monitor: nagios
> Starting network monitor: nagios
>   PID TTY          TIME CMD
> honda:/usr/local/nagios/etc #
> 
> If I run the following
> ..../nagios/etc/../bin/nagios -v nagios.cfg Everything checks out ok
with
> just a couple warnings
> that have been there before. Am I missing something else I should be
> doing? Like perhaps
> specifying somewhere in the configs who has the right to run external
> commands? Thanks.

Did you check nagios.log? Chances are that nagios isn't able to actually
create the command pipe (nagios.cmd) in the path specified by
command_file in nagios.cfg.

--
Marc


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
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