Problem scheduling downtime externally

[Aaron M. Segura]

Please be more specific.  How, exactly, are you trying to write to the
pipe?  Please include some examples.

Do you look in the nagios log after that to see if it picked up any
commands?  Are there any relevant log entries that might help?

On Wed, 2008-06-25 at 11:09 -0400, Tony Rice (trice) wrote:
> I'm trying to interface a database of upcoming downtimes to Nagios via
> the SCHEDULE_AND_PROPAGATE_TRIGGERED_HOST_DOWNTIME external command.
> However, writing to the nagios.cmd file just sits there and never
> returns.  I'm wondering if it's a problem with the way the named pipe is
> setup.  My nagios.cmd file looks like this:
> 
> % ls -la var/rw/nagios.cmd
> prw-rw-rw-   1 nagios      nagios         0 Jun 25 08:03
> var/rw/nagios.cmd
> 
> I've tried writing to this file from perl and a borne shell script with
> similar results.  An advice?
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.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

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.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