Understanding notification_interval and state changes on free space monitors

[Andrew Moran]

I setup Nagios to watch a service.  I thought I had told it to notify  
me every 16 hours.  Over the weekend, a problem occurred and I was  
notified every 40 minutes or so.    I can't help but think I must be  
missing a configuration somewhere.

The service in question is monitoring free space on a filesystem.   I  
want it to go into warning when there is less than 10% free and  
become critical when there is 0% free.   From the event log, it seems  
like the state is going from CRITICAL to WARNING to CRITICAL, and  
every time it goes to CRITICAL, it sends me email.. but I can't  
figure out why it's going back into warning mode when the space free  
remained at 0%.

Part of the event log:

[02-17-2007 23:45:43] SERVICE ALERT: menc001;mc_vol001  
Space;WARNING;HARD;4;DISK WARNING - free space: /Volumes/mc_vol001 0  
MB (0%):
[02-17-2007 23:20:43] SERVICE NOTIFICATION: andy;menc001;mc_vol001  
Space;CRITICAL;notify-by-email;DISK CRITICAL - free space: /Volumes/ 
mc_vol001 0 MB (0%):
[02-17-2007 23:20:43] SERVICE ALERT: menc001;mc_vol001  
Space;CRITICAL;HARD;4;DISK CRITICAL - free space: /Volumes/mc_vol001  
0 MB (0%):
[02-17-2007 23:15:43] SERVICE ALERT: menc001;mc_vol001  
Space;WARNING;HARD;4;DISK WARNING - free space: /Volumes/mc_vol001 0  
MB (0%):
[02-17-2007 23:05:49] Auto-save of retention data completed  
successfully.
[02-17-2007 22:40:43] SERVICE NOTIFICATION: andy;menc001;mc_vol001  
Space;CRITICAL;notify-by-email;DISK CRITICAL - free space: /Volumes/ 
mc_vol001 0 MB (0%):
[02-17-2007 22:40:43] SERVICE ALERT: menc001;mc_vol001  
Space;CRITICAL;HARD;4;DISK CRITICAL - free space: /Volumes/mc_vol001  
0 MB (0%):
[02-17-2007 22:05:49] Auto-save of retention data completed  
successfully.
[02-17-2007 21:55:43] SERVICE ALERT: menc001;mc_vol001  
Space;WARNING;HARD;4;DISK WARNING - free space: /Volumes/mc_vol001 0  
MB (0%):
[02-17-2007 21:30:43] SERVICE NOTIFICATION: andy;menc001;mc_vol001  
Space;CRITICAL;notify-by-email;DISK CRITICAL - free space: /Volumes/ 
mc_vol001 0 MB (0%):


Relevant part of service definition:

         notification_options            u,c,r
         notification_interval           960
         notification_period             24x7
         check_command                   check_nrpe!check_disk!10%! 
0%!/Volumes/mc_vol001
         }


Ultimately I only want it to notify me when it's critical, not in  
warning, and I want the notification to only be sent every 16 hours  
(960 units, my unit is defined elsewhere as 60 seconds).        Any  
help as to what I'm doing wrong would be appreciated.  Thanks.

--Andy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070219/0b363f3e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2415 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/users/attachments/20070219/0b363f3e/attachment.bin>
-------------- next part --------------
-------------------------------------------------------------------------
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
-------------- next part --------------
_______________________________________________
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