[Nagios-users] Notifications configuration problem

[Michael Vaknine]

Hi,

 

I hope I am on the right place and if not please accept my apologies and
simply ignore.

 

I am usuing Nagios Core version 3.2.3 with check_mk v1.1.9i7

 

I am monitoring some servers on a different site and usuing ADSL line for
this.

I have problems with the ADSL Each time I get a notification that a server
is down and then after 5seconds I get a notification that the server is up
again.

Is there a way to configure a notification that Nagios will think that it
has a problem only if it is persistent more than 5 minutes or so?

 

Thanks

Michael

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev___
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

Re: [Nagios-users] check_memcached and hits/misses

[Eduardo Silvestre]

For e.g... How can you check if memcache is "full"? 

Sent from my iPad

On 30/05/2011, at 06:17, quanta  wrote:

> In my opinion, you shouldn't check the sudden increase in misses.
> You should check the get_misses value and alert when it is greater than
> a threshold.
> 
> $ echo "stats" | nc -w 1   | awk '/get_misses/ { print $3 }'
> 
> On 12/09/2010 11:55 PM, Pär Åslund wrote:
>> Hi,
>> 
>> I'm searching for a nagios check that looks at hits and misses.
>> 
>> Been using check_memcached for checking memcached status and right now
>> I will continue to do that checking that memcached is answering and
>> got free memory.
>> 
>> However, the issue with check_memcached is that it's looking at the
>> hits/misses ratio since start up of the memcached-process.
>> Whereas I need to know if a sudden increase in misses instead between
>> polls has occured.
>> 
>> Is anyone familiar with a such check for Nagios?
>> 
>> Best regards,
>> -p
>> 
>> --
>> ___
>> 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
> 
> --
> vRanger cuts backup time in half-while increasing security.
> With the market-leading solution for virtual backup and recovery, 
> you get blazing-fast, flexible, and affordable data protection.
> Download your free trial now. 
> http://p.sf.net/sfu/quest-d2dcopy1
> ___
> 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

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
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

Re: [Nagios-users] Non obvious 127 plugin error

[Clint Dilks]

Hi

Just wondering if SE Linux is disabled on your system?  If not check your
audit log and see if access to the plugin is being denied

On Thu, Jun 2, 2011 at 8:15 AM, Justin T Pryzby wrote:

> You can also strace the main nagios process:
> strace -fs999 -e execve -p PID_OF_NAGIOS
> or
> sudo strace -fs999 -e execve -p `ps o pid h -C nagios3 --sort start_time
> |sed q` 2>&1 |grep -Fw execve |grep -Fw check_dig
>
> 127 is the return status of the shell when a command isn't found:
> justinp@justinp:~$ asdf; echo $?
> bash: asdf: command not found
> 127
>
> man sh => /EXIT STATUS/
>
> Justin
>
> On Wed, Jun 01, 2011 at 04:23:05PM -0300, Craig Stewart wrote:
> > Giorgio
> >
> > As apache user:
> >
> > bash-4.2$ /usr/lib/nagios/plugins/check_dig -H 72.45.111.250 -l
> > www.xplornet.com -a 142.166.86.46 -w 0.5 -c 1 -t 5
> > DNS OK - 0.096 seconds response time (www.xplornet.com. 864 IN A
> > 142.166.86.46)|time=0.095553s;0.50;1.00;0.00
> >
> >
> > You understand my confusion.
> >
> > Craig
> >
> > Craig Stewart
> > Systems Integration Analyst
> > craig.stew...@corp.xplornet.com Tel: (506) 328-1245 Cell: (506) 425-0111
> > Xplornet - Broadband, Everywhere
> >
> > On 06/01/2011 04:18 PM, Giorgio Zarrelli wrote:
> > > Hi,
> > >
> > > I'm curious. Please, do a su - as the apache user and execute the check
> > > as that user.
> > >
> > > Ciao,
> > >
> > > Giorgio
> >
> >
> --
> > Simplify data backup and recovery for your virtual environment with
> vRanger.
> > Installation's a snap, and flexible recovery options mean your data is
> safe,
> > secure and there when you need it. Data protection magic?
> > Nope - It's vRanger. Get your free trial download today.
> > http://p.sf.net/sfu/quest-sfdev2dev
> > ___
> > 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
> >
>
>
> --
> Simplify data backup and recovery for your virtual environment with
> vRanger.
> Installation's a snap, and flexible recovery options mean your data is
> safe,
> secure and there when you need it. Data protection magic?
> Nope - It's vRanger. Get your free trial download today.
> http://p.sf.net/sfu/quest-sfdev2dev
> ___
> 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
>
--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev___
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

Re: [Nagios-users] Non obvious 127 plugin error

[Justin T Pryzby]

You can also strace the main nagios process:
strace -fs999 -e execve -p PID_OF_NAGIOS
or
sudo strace -fs999 -e execve -p `ps o pid h -C nagios3 --sort start_time |sed 
q` 2>&1 |grep -Fw execve |grep -Fw check_dig

127 is the return status of the shell when a command isn't found:
justinp@justinp:~$ asdf; echo $?
bash: asdf: command not found
127

man sh => /EXIT STATUS/

Justin

On Wed, Jun 01, 2011 at 04:23:05PM -0300, Craig Stewart wrote:
> Giorgio
> 
> As apache user:
> 
> bash-4.2$ /usr/lib/nagios/plugins/check_dig -H 72.45.111.250 -l
> www.xplornet.com -a 142.166.86.46 -w 0.5 -c 1 -t 5
> DNS OK - 0.096 seconds response time (www.xplornet.com. 864 IN A
> 142.166.86.46)|time=0.095553s;0.50;1.00;0.00
> 
> 
> You understand my confusion.
> 
> Craig
> 
> Craig Stewart
> Systems Integration Analyst
> craig.stew...@corp.xplornet.com Tel: (506) 328-1245 Cell: (506) 425-0111
> Xplornet - Broadband, Everywhere
> 
> On 06/01/2011 04:18 PM, Giorgio Zarrelli wrote:
> > Hi,
> > 
> > I'm curious. Please, do a su - as the apache user and execute the check
> > as that user.
> > 
> > Ciao,
> > 
> > Giorgio
> 
> --
> Simplify data backup and recovery for your virtual environment with vRanger. 
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Data protection magic?
> Nope - It's vRanger. Get your free trial download today. 
> http://p.sf.net/sfu/quest-sfdev2dev
> ___
> 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
> 

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
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

Re: [Nagios-users] Non obvious 127 plugin error

[Giorgio Zarrelli]

I understand your confusion. Undortunately I will be om holiday until monday 
and I won't be able to use a real computer for some tests.

Anyway, I will think about it.

Ciao,

Giorgio

Il giorno 01/giu/2011, alle ore 21:23, Craig Stewart 
 ha scritto:

> Giorgio
> 
> As apache user:
> 
> bash-4.2$ /usr/lib/nagios/plugins/check_dig -H 72.45.111.250 -l
> www.xplornet.com -a 142.166.86.46 -w 0.5 -c 1 -t 5
> DNS OK - 0.096 seconds response time (www.xplornet.com. 864 IN A
> 142.166.86.46)|time=0.095553s;0.50;1.00;0.00
> 
> 
> You understand my confusion.
> 
> Craig
> 
> Craig Stewart
> Systems Integration Analyst
> craig.stew...@corp.xplornet.com Tel: (506) 328-1245 Cell: (506) 425-0111
> Xplornet - Broadband, Everywhere
> 
> On 06/01/2011 04:18 PM, Giorgio Zarrelli wrote:
>> Hi,
>> 
>> I'm curious. Please, do a su - as the apache user and execute the check
>> as that user.
>> 
>> Ciao,
>> 
>> Giorgio

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
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

Re: [Nagios-users] Non obvious 127 plugin error

[Craig Stewart]

Matin,

Not quite sure what you mean.  As far as I know I don't have a password
variable in my command definition.

Craig
--
Craig Stewart
Systems Integration Analyst
craig.stew...@corp.xplornet.com Tel: (506) 328-1245 Cell: (506) 425-0111
Xplornet - Broadband, Everywhere

On 06/01/2011 02:11 PM, Martin Hugo wrote:
> Hi Craig,
> 
> Not sure if it will help you but when I had a check reporting a similar
> plug-in error that ran just fine from the terminal I removed the
> password variable from the comd def and hard-coded the pwd in there
> instead.  Worked for me.
> 
> Martin T. Hugo
> Network Administrator
> Hilliard City Schools
> 614-921-7102 (Ph)
> 614-771-7243 (Fax)
> 
> -Original Message-
> From: Craig Stewart [mailto:craig.stew...@corpxplornet.com
> ]
> Sent: Wednesday, June 01, 2011 10:48 AM
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] Non obvious 127 plugin error
> 
> Good day folks,
> 
> I've spent the better part of a week using Google and combing forums for
> an answer to this question without much luck.  First the specs:
> 
> Nagios version 3.2.3
> Nagios and associated plugins installed on CentOS 5.6 and Fedora 15
> servers via package management (i.e. yum)
> 
> I have a couple plugins that simply won't execute.  One of which is the
> check_dig command.  I'll use this for an example.
> 
>>From the commands.cfg file for Nagios:
> 
> define command{
> command_namecheck_dns
> command_line/usr/lib/nagios/plugins/check_dig -H
> $HOSTADDRESS$ -l
> $ARG1$ -a $ARG2$ -w $ARG3$ -c $ARG4$ -t $ARG5$
> }
> 
>>From the Nagios log file:
> 
> [1306863226] Warning: Return code of 127 for check of service
> 'DNS-Check' on host 'TS-TOR-DNS-1' was out of bounds. Make sure the
> plugin you're trying to run actually exists.
> 
> 
> Okay, first to see if it exists:
> 
> [root@nms ~]# locate check_dig
> /usr/lib/nagios/plugins/check_dig
> [root@nms ~]#
> 
> Ownership and permissions check:
> 
> [root@nms ~]# ls -l /usr/lib/nagios/plugins/check_dig
> -rwxr-xr-x. 1 nagios nagios 43292 Mar 23 15:42
> /usr/lib/nagios/plugins/check_dig
> [root@nms ~]#
> 
> Try running it as root:
> [root@nms ~]# /usr/lib/nagios/plugins/check_dig *BLANKED* -l *BLANKED*
> -a *BLANKED* -c 5 -w 0.25
> DNS OK - 0.005 seconds response time (*BLANKED*. 900 IN A
> *BLANKED*)|time=0.004967s;0.25;5.00;0.00
> 
> So it works as root.  Now to try as Nagios user:
> [root@nms ~]# su - nagios
> -bash-4.2$ /usr/lib/nagios/plugins/check_dig *BLANKED* -l *BLANKED* -a
> *BLANKED* -c 5 -w 0.25
> DNS OK - 0.005 seconds response time (*BLANKED*. 900 IN A
> *BLANKED*)|time=0.004967s;0.25;5.00;0.00
> 
> It works as the Nagios user as well.
> 
> So, I'm sure you can see my confusion.  The plugin exists and is
> executable for a user on the system, but even when called directly as
> opposed to using the $USER1$ macro, the Nagios process can't run it.
> 
> Any thoughts anyone?
> 
> Cheers!
> 
> Craig
> 
> --
> Craig Stewart
> Systems Integration Analyst
> craig.stew...@corp.xplornet.com
> Xplornet - Broadband, Everywhere
> 
> --
> Simplify data backup and recovery for your virtual environment with vRanger.
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Data protection magic?
> Nope - It's vRanger. Get your free trial download today.
> http://p.sf.net/sfu/quest-sfdev2dev
> ___
> 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
> 
> 
> 
> --
> Simplify data backup and recovery for your virtual environment with vRanger.
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Data protection magic?
> Nope - It's vRanger. Get your free trial download today.
> http://p.sf.net/sfu/quest-sfdev2dev
> ___
> 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
> 
> --
> This message has been scanned by MailScanner
> 

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. G

Re: [Nagios-users] Non obvious 127 plugin error

[Craig Stewart]

Giorgio

As apache user:

bash-4.2$ /usr/lib/nagios/plugins/check_dig -H 72.45.111.250 -l
www.xplornet.com -a 142.166.86.46 -w 0.5 -c 1 -t 5
DNS OK - 0.096 seconds response time (www.xplornet.com. 864 IN A
142.166.86.46)|time=0.095553s;0.50;1.00;0.00


You understand my confusion.

Craig

Craig Stewart
Systems Integration Analyst
craig.stew...@corp.xplornet.com Tel: (506) 328-1245 Cell: (506) 425-0111
Xplornet - Broadband, Everywhere

On 06/01/2011 04:18 PM, Giorgio Zarrelli wrote:
> Hi,
> 
> I'm curious. Please, do a su - as the apache user and execute the check
> as that user.
> 
> Ciao,
> 
> Giorgio

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
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

Re: [Nagios-users] Non obvious 127 plugin error

[Giorgio Zarrelli]

Hi,

I'm curious. Please, do a su - as the apache user and execute the check as that 
user.

Ciao,

Giorgio

Il giorno 01/giu/2011, alle ore 20:50, Craig Stewart 
 ha scritto:

> Giorgio,
> 
> Here's the final command:
> 
> [1306952706.565337] [2048.1] [pid=3753]   Done.  Final output:
> '/usr/lib/nagios/plugins/check_dig -H 72.45.111.250 -l www.xplornet.com
> -a 142.166.86.46 -w 0.5 -c 1 -t 5'
> 
> I assume that's what you meant?
> 
> I'm also seeing this in the debug log:
> 
> [1306952721.202757] [016.1] [pid=3753] HOST: TS-WIN-DNS-1, SERVICE:
> DNS-Check, CHECK TYPE: Active, OPTIONS: 0, SCHEDULED: Yes, RESCHEDULE:
> Yes, EXITED OK: Yes, RETURN CODE: 127, OUTPUT: (null)
> 
> 
> 
> Craig Stewart
> Systems Integration Analyst
> craig.stew...@corp.xplornet.com
> Xplornet - Broadband, Everywhere
> 
> On 06/01/2011 02:20 PM, Giorgio Zarrelli wrote:
>> Please,
>> 
>> Switch on debug and paste here the "final command"
>> 
>> Ciao,
>> 
>> Giorgio
>> 
>> Il giorno 01/giu/2011, alle ore 16:47, Craig Stewart
>>  ha scritto:
>> 
>>> Good day folks,
>>> 
>>> I've spent the better part of a week using Google and combing forums for
>>> an answer to this question without much luck.  First the specs:
>>> 
>>> Nagios version 3.2.3
>>> Nagios and associated plugins installed on CentOS 5.6 and Fedora 15
>>> servers via package management (i.e. yum)
>>> 
>>> I have a couple plugins that simply won't execute.  One of which is the
>>> check_dig command.  I'll use this for an example.
>>> 
 From the commands.cfg file for Nagios:
>>> 
>>> define command{
>>>   command_namecheck_dns
>>>   command_line/usr/lib/nagios/plugins/check_dig -H $HOSTADDRESS$ -l
>>> $ARG1$ -a $ARG2$ -w $ARG3$ -c $ARG4$ -t $ARG5$
>>>   }
>>> 
 From the Nagios log file:
>>> 
>>> [1306863226] Warning: Return code of 127 for check of service
>>> 'DNS-Check' on host 'TS-TOR-DNS-1' was out of bounds. Make sure the
>>> plugin you're trying to run actually exists.
>>> 
>>> 
>>> Okay, first to see if it exists:
>>> 
>>> [root@nms ~]# locate check_dig
>>> /usr/lib/nagios/plugins/check_dig
>>> [root@nms ~]#
>>> 
>>> Ownership and permissions check:
>>> 
>>> [root@nms ~]# ls -l /usr/lib/nagios/plugins/check_dig
>>> -rwxr-xr-x. 1 nagios nagios 43292 Mar 23 15:42
>>> /usr/lib/nagios/plugins/check_dig
>>> [root@nms ~]#
>>> 
>>> Try running it as root:
>>> [root@nms ~]# /usr/lib/nagios/plugins/check_dig *BLANKED* -l *BLANKED*
>>> -a *BLANKED* -c 5 -w 0.25
>>> DNS OK - 0.005 seconds response time (*BLANKED*. 900 IN A
>>> *BLANKED*)|time=0.004967s;0.25;5.00;0.00
>>> 
>>> So it works as root.  Now to try as Nagios user:
>>> [root@nms ~]# su - nagios
>>> -bash-4.2$ /usr/lib/nagios/plugins/check_dig *BLANKED* -l *BLANKED* -a
>>> *BLANKED* -c 5 -w 0.25
>>> DNS OK - 0.005 seconds response time (*BLANKED*. 900 IN A
>>> *BLANKED*)|time=0.004967s;0.25;5.00;0.00
>>> 
>>> It works as the Nagios user as well.
>>> 
>>> So, I'm sure you can see my confusion.  The plugin exists and is
>>> executable for a user on the system, but even when called directly as
>>> opposed to using the $USER1$ macro, the Nagios process can't run it.
>>> 
>>> Any thoughts anyone?
>>> 
>>> Cheers!
>>> 
>>> Craig
>>> 
>>> --
>>> Craig Stewart
>>> Systems Integration Analyst
>>> craig.stew...@corp.xplornet.com
>>> Xplornet - Broadband, Everywhere
>>> 
>>> 
>> --
>>> Simplify data backup and recovery for your virtual environment with
>> vRanger.
>>> Installation's a snap, and flexible recovery options mean your data is
>> safe,
>>> secure and there when you need it. Data protection magic?
>>> Nope - It's vRanger. Get your free trial download today.
>>> http://p.sf.net/sfu/quest-sfdev2dev
>>> ___
>>> 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
>> 
>> --
>> Simplify data backup and recovery for your virtual environment with vRanger.
>> Installation's a snap, and flexible recovery options mean your data is safe,
>> secure and there when you need it. Data protection magic?
>> Nope - It's vRanger. Get your free trial download today.
>> http://p.sf.net/sfu/quest-sfdev2dev
>> ___
>> 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
>> 
>> --
>> This message has been scanned by MailScanner
>> 

-

Re: [Nagios-users] Non obvious 127 plugin error

[Craig Stewart]

Giorgio,

Here's the final command:

[1306952706.565337] [2048.1] [pid=3753]   Done.  Final output:
'/usr/lib/nagios/plugins/check_dig -H 72.45.111.250 -l www.xplornet.com
-a 142.166.86.46 -w 0.5 -c 1 -t 5'

I assume that's what you meant?

I'm also seeing this in the debug log:

[1306952721.202757] [016.1] [pid=3753] HOST: TS-WIN-DNS-1, SERVICE:
DNS-Check, CHECK TYPE: Active, OPTIONS: 0, SCHEDULED: Yes, RESCHEDULE:
Yes, EXITED OK: Yes, RETURN CODE: 127, OUTPUT: (null)



Craig Stewart
Systems Integration Analyst
craig.stew...@corp.xplornet.com
Xplornet - Broadband, Everywhere

On 06/01/2011 02:20 PM, Giorgio Zarrelli wrote:
> Please,
> 
> Switch on debug and paste here the "final command"
> 
> Ciao,
> 
> Giorgio
> 
> Il giorno 01/giu/2011, alle ore 16:47, Craig Stewart
>  ha scritto:
> 
>> Good day folks,
>>
>> I've spent the better part of a week using Google and combing forums for
>> an answer to this question without much luck.  First the specs:
>>
>> Nagios version 3.2.3
>> Nagios and associated plugins installed on CentOS 5.6 and Fedora 15
>> servers via package management (i.e. yum)
>>
>> I have a couple plugins that simply won't execute.  One of which is the
>> check_dig command.  I'll use this for an example.
>>
>>> From the commands.cfg file for Nagios:
>>
>> define command{
>>command_namecheck_dns
>>command_line/usr/lib/nagios/plugins/check_dig -H $HOSTADDRESS$ -l
>> $ARG1$ -a $ARG2$ -w $ARG3$ -c $ARG4$ -t $ARG5$
>>}
>>
>>> From the Nagios log file:
>>
>> [1306863226] Warning: Return code of 127 for check of service
>> 'DNS-Check' on host 'TS-TOR-DNS-1' was out of bounds. Make sure the
>> plugin you're trying to run actually exists.
>>
>>
>> Okay, first to see if it exists:
>>
>> [root@nms ~]# locate check_dig
>> /usr/lib/nagios/plugins/check_dig
>> [root@nms ~]#
>>
>> Ownership and permissions check:
>>
>> [root@nms ~]# ls -l /usr/lib/nagios/plugins/check_dig
>> -rwxr-xr-x. 1 nagios nagios 43292 Mar 23 15:42
>> /usr/lib/nagios/plugins/check_dig
>> [root@nms ~]#
>>
>> Try running it as root:
>> [root@nms ~]# /usr/lib/nagios/plugins/check_dig *BLANKED* -l *BLANKED*
>> -a *BLANKED* -c 5 -w 0.25
>> DNS OK - 0.005 seconds response time (*BLANKED*. 900 IN A
>> *BLANKED*)|time=0.004967s;0.25;5.00;0.00
>>
>> So it works as root.  Now to try as Nagios user:
>> [root@nms ~]# su - nagios
>> -bash-4.2$ /usr/lib/nagios/plugins/check_dig *BLANKED* -l *BLANKED* -a
>> *BLANKED* -c 5 -w 0.25
>> DNS OK - 0.005 seconds response time (*BLANKED*. 900 IN A
>> *BLANKED*)|time=0.004967s;0.25;5.00;0.00
>>
>> It works as the Nagios user as well.
>>
>> So, I'm sure you can see my confusion.  The plugin exists and is
>> executable for a user on the system, but even when called directly as
>> opposed to using the $USER1$ macro, the Nagios process can't run it.
>>
>> Any thoughts anyone?
>>
>> Cheers!
>>
>> Craig
>>
>> --
>> Craig Stewart
>> Systems Integration Analyst
>> craig.stew...@corp.xplornet.com
>> Xplornet - Broadband, Everywhere
>>
>>
> --
>> Simplify data backup and recovery for your virtual environment with
> vRanger.
>> Installation's a snap, and flexible recovery options mean your data is
> safe,
>> secure and there when you need it. Data protection magic?
>> Nope - It's vRanger. Get your free trial download today.
>> http://p.sf.net/sfu/quest-sfdev2dev
>> ___
>> 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
> 
> --
> Simplify data backup and recovery for your virtual environment with vRanger.
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Data protection magic?
> Nope - It's vRanger. Get your free trial download today.
> http://p.sf.net/sfu/quest-sfdev2dev
> ___
> 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
> 
> --
> This message has been scanned by MailScanner
> 

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___

Re: [Nagios-users] Non obvious 127 plugin error

[Giorgio Zarrelli]

Please,

Switch on debug and paste here the "final command"

Ciao,

Giorgio

Il giorno 01/giu/2011, alle ore 16:47, Craig Stewart 
 ha scritto:

> Good day folks,
> 
> I've spent the better part of a week using Google and combing forums for
> an answer to this question without much luck.  First the specs:
> 
> Nagios version 3.2.3
> Nagios and associated plugins installed on CentOS 5.6 and Fedora 15
> servers via package management (i.e. yum)
> 
> I have a couple plugins that simply won't execute.  One of which is the
> check_dig command.  I'll use this for an example.
> 
>> From the commands.cfg file for Nagios:
> 
> define command{
>command_namecheck_dns
>command_line/usr/lib/nagios/plugins/check_dig -H $HOSTADDRESS$ -l
> $ARG1$ -a $ARG2$ -w $ARG3$ -c $ARG4$ -t $ARG5$
>}
> 
>> From the Nagios log file:
> 
> [1306863226] Warning: Return code of 127 for check of service
> 'DNS-Check' on host 'TS-TOR-DNS-1' was out of bounds. Make sure the
> plugin you're trying to run actually exists.
> 
> 
> Okay, first to see if it exists:
> 
> [root@nms ~]# locate check_dig
> /usr/lib/nagios/plugins/check_dig
> [root@nms ~]#
> 
> Ownership and permissions check:
> 
> [root@nms ~]# ls -l /usr/lib/nagios/plugins/check_dig
> -rwxr-xr-x. 1 nagios nagios 43292 Mar 23 15:42
> /usr/lib/nagios/plugins/check_dig
> [root@nms ~]#
> 
> Try running it as root:
> [root@nms ~]# /usr/lib/nagios/plugins/check_dig *BLANKED* -l *BLANKED*
> -a *BLANKED* -c 5 -w 0.25
> DNS OK - 0.005 seconds response time (*BLANKED*. 900 IN A
> *BLANKED*)|time=0.004967s;0.25;5.00;0.00
> 
> So it works as root.  Now to try as Nagios user:
> [root@nms ~]# su - nagios
> -bash-4.2$ /usr/lib/nagios/plugins/check_dig *BLANKED* -l *BLANKED* -a
> *BLANKED* -c 5 -w 0.25
> DNS OK - 0.005 seconds response time (*BLANKED*. 900 IN A
> *BLANKED*)|time=0.004967s;0.25;5.00;0.00
> 
> It works as the Nagios user as well.
> 
> So, I'm sure you can see my confusion.  The plugin exists and is
> executable for a user on the system, but even when called directly as
> opposed to using the $USER1$ macro, the Nagios process can't run it.
> 
> Any thoughts anyone?
> 
> Cheers!
> 
> Craig
> 
> -- 
> Craig Stewart
> Systems Integration Analyst
> craig.stew...@corp.xplornet.com
> Xplornet - Broadband, Everywhere
> 
> --
> Simplify data backup and recovery for your virtual environment with vRanger. 
> Installation's a snap, and flexible recovery options mean your data is safe,
> secure and there when you need it. Data protection magic?
> Nope - It's vRanger. Get your free trial download today. 
> http://p.sf.net/sfu/quest-sfdev2dev
> ___
> 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

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
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

Re: [Nagios-users] Non obvious 127 plugin error

[Martin Hugo]

Hi Craig,

Not sure if it will help you but when I had a check reporting a similar plug-in 
error that ran just fine from the terminal I removed the password variable from 
the comd def and hard-coded the pwd in there instead.  Worked for me.

Martin T. Hugo
Network Administrator
Hilliard City Schools
614-921-7102 (Ph)
614-771-7243 (Fax)

-Original Message-
From: Craig Stewart [mailto:craig.stew...@corp.xplornet.com] 
Sent: Wednesday, June 01, 2011 10:48 AM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] Non obvious 127 plugin error

Good day folks,

I've spent the better part of a week using Google and combing forums for
an answer to this question without much luck.  First the specs:

Nagios version 3.2.3
Nagios and associated plugins installed on CentOS 5.6 and Fedora 15
servers via package management (i.e. yum)

I have a couple plugins that simply won't execute.  One of which is the
check_dig command.  I'll use this for an example.

>From the commands.cfg file for Nagios:

define command{
command_namecheck_dns
command_line/usr/lib/nagios/plugins/check_dig -H $HOSTADDRESS$ -l
$ARG1$ -a $ARG2$ -w $ARG3$ -c $ARG4$ -t $ARG5$
}

>From the Nagios log file:

[1306863226] Warning: Return code of 127 for check of service
'DNS-Check' on host 'TS-TOR-DNS-1' was out of bounds. Make sure the
plugin you're trying to run actually exists.


Okay, first to see if it exists:

[root@nms ~]# locate check_dig
/usr/lib/nagios/plugins/check_dig
[root@nms ~]#

Ownership and permissions check:

[root@nms ~]# ls -l /usr/lib/nagios/plugins/check_dig
-rwxr-xr-x. 1 nagios nagios 43292 Mar 23 15:42
/usr/lib/nagios/plugins/check_dig
[root@nms ~]#

Try running it as root:
[root@nms ~]# /usr/lib/nagios/plugins/check_dig *BLANKED* -l *BLANKED*
-a *BLANKED* -c 5 -w 0.25
DNS OK - 0.005 seconds response time (*BLANKED*. 900 IN A
*BLANKED*)|time=0.004967s;0.25;5.00;0.00

So it works as root.  Now to try as Nagios user:
[root@nms ~]# su - nagios
-bash-4.2$ /usr/lib/nagios/plugins/check_dig *BLANKED* -l *BLANKED* -a
*BLANKED* -c 5 -w 0.25
DNS OK - 0.005 seconds response time (*BLANKED*. 900 IN A
*BLANKED*)|time=0.004967s;0.25;5.00;0.00

It works as the Nagios user as well.

So, I'm sure you can see my confusion.  The plugin exists and is
executable for a user on the system, but even when called directly as
opposed to using the $USER1$ macro, the Nagios process can't run it.

Any thoughts anyone?

Cheers!

Craig

-- 
Craig Stewart
Systems Integration Analyst
craig.stew...@corp.xplornet.com
Xplornet - Broadband, Everywhere

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
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



--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
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

Re: [Nagios-users] Scheduled downtime and host checks

[Paul M. Dubuc]

Jeffrey Watts wrote:
> On Wed, Jun 1, 2011 at 1:27 AM, Kumar, Ashish  > wrote:
>
>
> No, scheduled downtime only affects notifications, and the stats you
> see in the availability cgi.  Service and host checks run as normal
> during scheduled downtime.
>
>
> Thanks Jim for the explanation but I do not see any rational reason
> to execute host and service checks while the monitored host is
> scheduled for "fixed" downtime.
>
>
> There are plenty of rational reasons.  Just because you disagree with
> the default behavior doesn't mean it's irrational.  Many, many, many
> times I put systems into scheduled, fixed downtime and still want checks
> to be executed.  For example, if I know the netadmins are going to be
> reconfiguring networking at one of our datacenters I will schedule fixed
> downtime for the period of their maintenance for the
> servers/switches/routers affected.
>
> However, I do want to see what's up and down during that time so I can
> tell when they start and finish their work, and what they're affecting.
>   That's a perfectly rational reason to do checks during maintenance.
>
> This is useful because it allows you to
> check the stats of those hosts and services are ok before the
> scheduled downtime period ends.
>
>
> But if the host/services are offline after the scheduled "fixed"
> downtime period ends it will send the notifications anyway (or would
> it not?)
>
> I wish there was a way to disable active checks while a host has
> scheduled downtime set.
>
>
> If the hosts and services are down after the downtime ends yes it will
> send notifications, as clearly either:
>
> 1) The maintenance window wasn't long enough.
> 2) Someone broke something, or something died for another reason during
> maintenance
>
> Sounds like proper behavior.
>
> As far as your question goes, you can disable active checks manually, or
> you can write a script that sets downtime and disables active checks at
> the same time.  You could then run it (manually or via 'at' or something
> else) to re-enable active checks.  Or hack the Nagios source code and
> add that option yourself.  I believe in the last week or so someone
> posted a sample script for setting downtime via a script, so you might
> search the archives.
>
> Jeffrey.

You give some very good reasons for Nagios current behavior during a downtime. 
  But I agree with the original request that there be an option to disable 
checks during a downtime because there are equally rational reasons to do so.

There are some cases where we really should not be running service checks 
during down times because of the extra load they put on our system when they 
fail.   Many of our checks fail in this case by timing out and they use 
relatively scarce (shared) and resource intensive processes (web browser 
sessions run under SeleniumRC).  Timeouts tend to be long for these checks so 
there is more contention for these processes when all the checks using them 
start failing, and they're run more often until they all go into a 'hard' 
failure state, etc.  Maybe we can live with this, but it would be easier on 
the system to just inhibit checks we know are going to fail during certain 
regularly scheduled down times.  There may be plenty of other examples where 
running lots of failing tests during a downtime end up using significant 
system resources.

We implement our regular downtimes by using by defining the uptime with a 
timeperiod and using that for the check_period and notification_period of our 
services.  The problem with that is that all the services get scheduled to run 
at the exact second that our "downtime" ends.  So we have to define a 
concurrency limit and rely on nagios nudging checks out when the limit is 
reached in order to spread the schedule out again.

It would be very nice to be able to define regular downtimes with timeperiods 
and have the option of inhibiting checks as well as notifications during those 
downtimes without bunching up the scheduling queue when the downtime ends.

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
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] Non obvious 127 plugin error

[Craig Stewart]

Good day folks,

I've spent the better part of a week using Google and combing forums for
an answer to this question without much luck.  First the specs:

Nagios version 3.2.3
Nagios and associated plugins installed on CentOS 5.6 and Fedora 15
servers via package management (i.e. yum)

I have a couple plugins that simply won't execute.  One of which is the
check_dig command.  I'll use this for an example.

>From the commands.cfg file for Nagios:

define command{
command_namecheck_dns
command_line/usr/lib/nagios/plugins/check_dig -H $HOSTADDRESS$ -l
$ARG1$ -a $ARG2$ -w $ARG3$ -c $ARG4$ -t $ARG5$
}

>From the Nagios log file:

[1306863226] Warning: Return code of 127 for check of service
'DNS-Check' on host 'TS-TOR-DNS-1' was out of bounds. Make sure the
plugin you're trying to run actually exists.


Okay, first to see if it exists:

[root@nms ~]# locate check_dig
/usr/lib/nagios/plugins/check_dig
[root@nms ~]#

Ownership and permissions check:

[root@nms ~]# ls -l /usr/lib/nagios/plugins/check_dig
-rwxr-xr-x. 1 nagios nagios 43292 Mar 23 15:42
/usr/lib/nagios/plugins/check_dig
[root@nms ~]#

Try running it as root:
[root@nms ~]# /usr/lib/nagios/plugins/check_dig *BLANKED* -l *BLANKED*
-a *BLANKED* -c 5 -w 0.25
DNS OK - 0.005 seconds response time (*BLANKED*. 900 IN A
*BLANKED*)|time=0.004967s;0.25;5.00;0.00

So it works as root.  Now to try as Nagios user:
[root@nms ~]# su - nagios
-bash-4.2$ /usr/lib/nagios/plugins/check_dig *BLANKED* -l *BLANKED* -a
*BLANKED* -c 5 -w 0.25
DNS OK - 0.005 seconds response time (*BLANKED*. 900 IN A
*BLANKED*)|time=0.004967s;0.25;5.00;0.00

It works as the Nagios user as well.

So, I'm sure you can see my confusion.  The plugin exists and is
executable for a user on the system, but even when called directly as
opposed to using the $USER1$ macro, the Nagios process can't run it.

Any thoughts anyone?

Cheers!

Craig

-- 
Craig Stewart
Systems Integration Analyst
craig.stew...@corp.xplornet.com
Xplornet - Broadband, Everywhere

--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___
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

Re: [Nagios-users] Services are dependent on the host they run on?

[Roberto Nunnari]

Roberto Nunnari wrote:
> Hi Gerald.
> 
> 
> Ortner, Gerald wrote:
>> What host/service check interval/max check attempts do you use?
>> Maybe the host check interval is much longer than the service check interval.
>> If the services become hard state critical before the host check does, the 
>> service notifications will be sent, as Nagios isn't aware of the host 
>> problem.
>> I don't know how Nagios behaves if the host is only in soft state?
> 
> I believe that may be the problem.
> The service and host check interval were all 1 minute.
> Maybe, if the checks on the services happen to fail before the checks on 
> the host, then notification for all failed services will be sent anyways.
> 
> This assumes that nagios doesn't care about service dependency on the 
> host running the service when the host is in soft state critical, but 
> only when the host is in hard state critical.
> 
> I modified host/service check interval as follow:
> define host {
> ...
>  max_check_attempts  3
>  normal_check_interval   1
>  retry_check_interval1
> ...
> }
> define service {
> ...
>  max_check_attempts  3
>  normal_check_interval   3
>  retry_check_interval2
> ...
> }
> 
> The above should always give host checks for the host to reach a hard 
> state critical before the services in case the host goes down.
> 
> I've already run an easy test and the result confirmed what stated 
> above, but I'll run some more tests as soon as possible, maybe already 
> tomorrow, and report the results here.

Hi all.
I can confirm that now I can no longer reproduce that undesired 
behavior. So it seems that it was a misconfiguration of the host/service 
check interval/max check attempts.
I would be very helpful though, if 'nagios -v' would signal that, at 
least as a warning. If I'll ever get round to, I'd be pleased to 
contribute a patch for that.

Thank you very much and best regards.
Roberto Nunnari


> 
> Thank you to all.
> Robi
> 
>> hth
>> gerald
>>
>>> -Ursprüngliche Nachricht-
>>> Von: Roberto Nunnari [mailto:roberto.nunn...@supsi.ch]
>>> Gesendet: Freitag, 27. Mai 2011 09:01
>>> An: Nagios Users List
>>> Betreff: Re: [Nagios-users] Services are dependent on the host they run on?
>>>
>>> Hi Mark.
>>>
>>>
>>> Frost, Mark {PBC} wrote:
 Maybe I'm missing something but I thought that suppressing notifications
>>> for services on the same host when the host goes down is the default
>>> behavior.  It's only when you have to suppress notifications from different
>>> hosts that you need host/service dependencies.
>>>
>>> That's exactly what I was expecting, but it doesn't seem to work that way.. 
>>> at
>>> least not for me.
>>>
>>> Yesterday for instance, a host went down because of a hd controller failure,
>>> and I received 22 sms..
>>>
>>> Robi
>>>
>>>
 Mark

 -Original Message-
 From: Assaf Flatto [mailto:nag...@flatto.net]
 Sent: Thursday, May 26, 2011 1:39 PM
 To: Nagios Users List
 Subject: Re: [Nagios-users] Services are dependent on the host they run
>>> on?
 Martin Hugo wrote:
> Hi Robi,
>
> I have never done it but I know you can make hosts/services children that
>>> will not report if the parent is down.
> Hope this puts you on the right track.
>
> Marty
>
> -Original Message-
> From: Roberto Nunnari [mailto:roberto.nunn...@supsi.ch]
> Sent: Thursday, May 26, 2011 12:47 PM
> To: nagios-users@lists.sourceforge.net
> Subject: [Nagios-users] Services are dependent on the host they run on?
>
> Hi all.
>
> Some time ago, I've installed and configured nagios to monitor our IT
> infrastructure.
>
> It works very well and we're happy with it.
>
> There's still one problem though:
> When a host goes down, nagios sends notifications not only for host
> down, but also for all services running on that host. When a host
> goes down, I would like nagios to only send notifications about the
> host down, and not for all the services running on that host.
>
> How can I achive that?
> May it be a configuration error from my side? I thought that to
> nagios, services would be dependent from the host running them..
>
> Any hint/advice/guidance is very welcome.
>
> Thank you and best regards.
>
> Robi
>
 check out service dependencies

 http://nagios.sourceforge.net/docs/3_0/dependencies.html


--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev
___

Re: [Nagios-users] Scheduled downtime and host checks

[Jeffrey Watts]

On Wed, Jun 1, 2011 at 1:27 AM, Kumar, Ashish  wrote:

>
>> No, scheduled downtime only affects notifications, and the stats you
>> see in the availability cgi.  Service and host checks run as normal
>> during scheduled downtime.
>
>
> Thanks Jim for the explanation but I do not see any rational reason to
> execute host and service checks while the monitored host is scheduled for
> "fixed" downtime.
>

There are plenty of rational reasons.  Just because you disagree with the
default behavior doesn't mean it's irrational.  Many, many, many times I put
systems into scheduled, fixed downtime and still want checks to be executed.
 For example, if I know the netadmins are going to be reconfiguring
networking at one of our datacenters I will schedule fixed downtime for the
period of their maintenance for the servers/switches/routers affected.

However, I do want to see what's up and down during that time so I can tell
when they start and finish their work, and what they're affecting.  That's a
perfectly rational reason to do checks during maintenance.


> This is useful because it allows you to
>> check the stats of those hosts and services are ok before the
>> scheduled downtime period ends.
>>
>
> But if the host/services are offline after the scheduled "fixed" downtime
> period ends it will send the notifications anyway (or would it not?)
>
> I wish there was a way to disable active checks while a host has scheduled
> downtime set.
>

If the hosts and services are down after the downtime ends yes it will send
notifications, as clearly either:

1) The maintenance window wasn't long enough.
2) Someone broke something, or something died for another reason during
maintenance

Sounds like proper behavior.

As far as your question goes, you can disable active checks manually, or you
can write a script that sets downtime and disables active checks at the same
time.  You could then run it (manually or via 'at' or something else) to
re-enable active checks.  Or hack the Nagios source code and add that option
yourself.  I believe in the last week or so someone posted a sample script
for setting downtime via a script, so you might search the archives.

Jeffrey.
--
Simplify data backup and recovery for your virtual environment with vRanger. 
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today. 
http://p.sf.net/sfu/quest-sfdev2dev___
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