Please always respond on-list so that others may benefit from your experience.
> -----Original Message----- > From: John Jolet [mailto:[EMAIL PROTECTED] > Sent: Monday, January 09, 2006 10:00 AM > To: Marc Powell > Subject: Re: [Nagios-users] downtime not working > > > On Jan 9, 2006, at 9:53 AM, Marc Powell wrote: > > > > > > >> -----Original Message----- > >> From: [EMAIL PROTECTED] [mailto:nagios-users- > >> [EMAIL PROTECTED] On Behalf Of John Jolet > >> Sent: Monday, January 09, 2006 9:27 AM > >> Cc: nagios-users@lists.sourceforge.net > >> Subject: Re: [Nagios-users] downtime not working > >> > > > > [removed OP] > > > >> > >> I'm also unable to do downtime, but I just get "an error occurred > >> processing your command". the rw directory is writeable by apache, > > which > >> is what my server runs as, and the pipe is group writable by apache. > > I > >> can't find an error either in the apache logs, nor the nagios logs. > > > > This indicates that nagios received the external command but was > > unable > > to completely parse it. Typically this is caused by leaving out a > > required field (i.e. one shown as red). Have you supplied all the > > required information in the correct format? > > > went to a problem that currently exists, clicked on the service, then > on "schedule downtime for this service" and let it poplulate the > fields... Are you also supplying the required comment? That's not automatically populated. -- Marc ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ 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
