Re: [Nagios-users] notification_interval < normal_check_interval
if the service remains in a non-ok state and notification_interval have passed since the last notification, another notification will be sent. please post your definition of the service. On Tue, Apr 19, 2011 at 1:44 AM, Mike Chesnut wrote: > I have a check that I only want to occur once a day, so I do this in the > service definition: > > normal_check_interval 1440 > > However, when it fails, I want it to retry every 10 minutes, so I do this: > > retry_check_interval 10 > > My default notification_interval is set to 15. When I run a pre-flight > check, I get this: > > Warning: Service '' on host '' has a notification > interval less than its check interval! Notifications are only re-sent > after checks are made, so the effective notification interval will be > that of the check interval. > > Is that warning telling me that notifications are only sent when a > normal check occurs? What I want is for in the event of a failure, > notifications to continue to be sent (every 15 minutes) until the > service recovers. Will that be the case? > > Thanks, > Mike > > -- > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-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 > -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-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] notification_interval < normal_check_interval
On 04/19/2011 03:35 AM, Paul M Dubuc wrote: > Mike Chesnut wrote: >> On 04/18/2011 12:08 PM, Paul M. Dubuc wrote: >>> >>> Mike Chesnut wrote: I have a check that I only want to occur once a day, so I do this in the service definition: normal_check_interval 1440 However, when it fails, I want it to retry every 10 minutes, so I do this: retry_check_interval10 My default notification_interval is set to 15. When I run a pre-flight check, I get this: Warning: Service '' on host'' has a notification interval less than its check interval! Notifications are only re-sent after checks are made, so the effective notification interval will be that of the check interval. Is that warning telling me that notifications are only sent when a normal check occurs? What I want is for in the event of a failure, notifications to continue to be sent (every 15 minutes) until the service recovers. Will that be the case? Thanks, Mike >>> >>> What is the value of max_check_attempts? It's at the end of that number of >>> checks that the service enters a hard state and a notification is sent. If >>> the value is 1, then the warning makes perfect sense because no retry checks >>> will be done. >> >> max_check_attempts is 2. Is that a sensible number here? >> >> Thanks, >> Mike >> > > OK, I think it will work this way: You will get a notification if there > is still a problem after the retry check. After that, the check > interval reverts to the normal interval and, if the problem persists > after the retry, you will not get another notification until after the > next normal interval check. You will not get a recovery notification > until then either if the problem clears up unless you rerun the check > manually. This doesn't sound like what you want. I don't think you can > do what you want without shortening the normal check interval. > That's wrong, unfortunately. It will work exactly like the warning states. First the max check attempts have to be reached and then the notifications will start being sent out. This means you'll get one notification per time the check is run (once every 1440 * interval_length seconds) so long as the service remains in a non-ok state. That's a conclusion of these rules: 1. No notifications are sent until the max check attempts are reached. 2. No notifications are sent unless the service just recently got checked. 3. The service gets re-checked using the default check-interval once the max check attempts have been reached. -- Andreas Ericsson andreas.erics...@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-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] notification_interval < normal_check_interval
Mike Chesnut wrote: > On 04/18/2011 12:08 PM, Paul M. Dubuc wrote: >> >> Mike Chesnut wrote: >>> I have a check that I only want to occur once a day, so I do this in the >>> service definition: >>> >>> normal_check_interval 1440 >>> >>> However, when it fails, I want it to retry every 10 minutes, so I do this: >>> >>> retry_check_interval10 >>> >>> My default notification_interval is set to 15. When I run a pre-flight >>> check, I get this: >>> >>> Warning: Service '' on host'' has a notification >>> interval less than its check interval! Notifications are only re-sent >>> after checks are made, so the effective notification interval will be >>> that of the check interval. >>> >>> Is that warning telling me that notifications are only sent when a >>> normal check occurs? What I want is for in the event of a failure, >>> notifications to continue to be sent (every 15 minutes) until the >>> service recovers. Will that be the case? >>> >>> Thanks, >>> Mike >>> >> >> What is the value of max_check_attempts? It's at the end of that number of >> checks that the service enters a hard state and a notification is sent. If >> the value is 1, then the warning makes perfect sense because no retry checks >> will be done. > > max_check_attempts is 2. Is that a sensible number here? > > Thanks, > Mike > OK, I think it will work this way: You will get a notification if there is still a problem after the retry check. After that, the check interval reverts to the normal interval and, if the problem persists after the retry, you will not get another notification until after the next normal interval check. You will not get a recovery notification until then either if the problem clears up unless you rerun the check manually. This doesn't sound like what you want. I don't think you can do what you want without shortening the normal check interval. Paul Dubuc -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-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] notification_interval < normal_check_interval
On 04/18/2011 12:08 PM, Paul M. Dubuc wrote: > > Mike Chesnut wrote: >> I have a check that I only want to occur once a day, so I do this in the >> service definition: >> >>normal_check_interval 1440 >> >> However, when it fails, I want it to retry every 10 minutes, so I do this: >> >>retry_check_interval10 >> >> My default notification_interval is set to 15. When I run a pre-flight >> check, I get this: >> >> Warning: Service '' on host'' has a notification >> interval less than its check interval! Notifications are only re-sent >> after checks are made, so the effective notification interval will be >> that of the check interval. >> >> Is that warning telling me that notifications are only sent when a >> normal check occurs? What I want is for in the event of a failure, >> notifications to continue to be sent (every 15 minutes) until the >> service recovers. Will that be the case? >> >> Thanks, >> Mike >> > > What is the value of max_check_attempts? It's at the end of that number of > checks that the service enters a hard state and a notification is sent. If > the value is 1, then the warning makes perfect sense because no retry checks > will be done. max_check_attempts is 2. Is that a sensible number here? Thanks, Mike -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-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] notification_interval < normal_check_interval
Mike Chesnut wrote: > I have a check that I only want to occur once a day, so I do this in the > service definition: > > normal_check_interval 1440 > > However, when it fails, I want it to retry every 10 minutes, so I do this: > > retry_check_interval10 > > My default notification_interval is set to 15. When I run a pre-flight > check, I get this: > > Warning: Service '' on host'' has a notification > interval less than its check interval! Notifications are only re-sent > after checks are made, so the effective notification interval will be > that of the check interval. > > Is that warning telling me that notifications are only sent when a > normal check occurs? What I want is for in the event of a failure, > notifications to continue to be sent (every 15 minutes) until the > service recovers. Will that be the case? > > Thanks, > Mike > What is the value of max_check_attempts? It's at the end of that number of checks that the service enters a hard state and a notification is sent. If the value is 1, then the warning makes perfect sense because no retry checks will be done. Paul Dubuc -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-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] notification_interval < normal_check_interval
I have a check that I only want to occur once a day, so I do this in the service definition: normal_check_interval 1440 However, when it fails, I want it to retry every 10 minutes, so I do this: retry_check_interval10 My default notification_interval is set to 15. When I run a pre-flight check, I get this: Warning: Service '' on host '' has a notification interval less than its check interval! Notifications are only re-sent after checks are made, so the effective notification interval will be that of the check interval. Is that warning telling me that notifications are only sent when a normal check occurs? What I want is for in the event of a failure, notifications to continue to be sent (every 15 minutes) until the service recovers. Will that be the case? Thanks, Mike -- Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-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] notification_interval depending upon contact
Yeah, my apologies, realized after I. Posted that I might have. Hiijacked the initial topic. Sorry, will post to ideas :).. Max On 7/20/09, Marc Powell wrote: > > On Jul 20, 2009, at 7:41 AM, Max wrote: > >> What I have been thinking about for a while and would really love to >> see is to have notifications become first class objects in nagios, >> like escalations, completely detatched from services and hosts. >> >> If we had >> >> servicenotification >> hostnotification >> >> Then configurations become hugely more flexible and easy to scale :) >> at the price of some serious recoding of parts of the nagios core and >> breaking backwards compatibility, so not easy by any measure. > > > You might want to start a new thread so the more people see this since > it's unrelated to the one you're commenting on. Go into a _lot_ more > detail about how you expect this would work. I don't really understand > what you're really trying to accomplish and how it's better based on > the comments above. > > If there's some interest, post to http://ideas.nagios.org or if > there's a lot of interest, post to nagios-devel. > > -- > Marc > > > -- > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > ___ > 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 > -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ 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] notification_interval depending upon contact
On Jul 20, 2009, at 7:41 AM, Max wrote: > What I have been thinking about for a while and would really love to > see is to have notifications become first class objects in nagios, > like escalations, completely detatched from services and hosts. > > If we had > > servicenotification > hostnotification > > Then configurations become hugely more flexible and easy to scale :) > at the price of some serious recoding of parts of the nagios core and > breaking backwards compatibility, so not easy by any measure. You might want to start a new thread so the more people see this since it's unrelated to the one you're commenting on. Go into a _lot_ more detail about how you expect this would work. I don't really understand what you're really trying to accomplish and how it's better based on the comments above. If there's some interest, post to http://ideas.nagios.org or if there's a lot of interest, post to nagios-devel. -- Marc -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ 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] notification_interval depending upon contact
What I have been thinking about for a while and would really love to see is to have notifications become first class objects in nagios, like escalations, completely detatched from services and hosts. If we had servicenotification hostnotification Then configurations become hugely more flexible and easy to scale :) at the price of some serious recoding of parts of the nagios core and breaking backwards compatibility, so not easy by any measure. Max On 7/20/09, Harald Dunkel wrote: > Max wrote: >> On Fri, Jul 17, 2009 at 10:17 AM, Mathew Walker >> wrote: >>> I think you'd then have to create two contacts per contact... one SMS and >>> one Email, then go with the info from the documentation here to set it >>> up: >>> http://nagios.sourceforge.net/docs/3_0/oncallrotation.html >> >> Yeah, that and some custom escalation rules and you should be good on >> having contacts notified via different means at different intervals. >> >> - Max >> > > Sorry, but as written before escalation rules are no option, because > they are bound to a host or service. I would like to set the notification > interval for each particular contact, not for a particular set of hosts > or services. > > Maybe Nagios has a design problem here? > > > Regards > > Harri > > > -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ 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] notification_interval depending upon contact
Max wrote: > On Fri, Jul 17, 2009 at 10:17 AM, Mathew Walker wrote: >> I think you'd then have to create two contacts per contact... one SMS and >> one Email, then go with the info from the documentation here to set it up: >> http://nagios.sourceforge.net/docs/3_0/oncallrotation.html > > Yeah, that and some custom escalation rules and you should be good on > having contacts notified via different means at different intervals. > > - Max > Sorry, but as written before escalation rules are no option, because they are bound to a host or service. I would like to set the notification interval for each particular contact, not for a particular set of hosts or services. Maybe Nagios has a design problem here? Regards Harri -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ 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] notification_interval depending upon contact
On Fri, Jul 17, 2009 at 10:17 AM, Mathew Walker wrote: > I think you'd then have to create two contacts per contact... one SMS and > one Email, then go with the info from the documentation here to set it up: > http://nagios.sourceforge.net/docs/3_0/oncallrotation.html Yeah, that and some custom escalation rules and you should be good on having contacts notified via different means at different intervals. - Max -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ 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] notification_interval depending upon contact
I think you'd then have to create two contacts per contact... one SMS and one Email, then go with the info from the documentation here to set it up: http://nagios.sourceforge.net/docs/3_0/oncallrotation.html -- Mat W. - http://www.techadre.com > Date: Fri, 17 Jul 2009 11:57:56 +0200 > From: harald.dun...@aixigo.de > To: nagios-users@lists.sourceforge.net > Subject: [Nagios-users] notification_interval depending upon contact > > Hi folks, > > Is there some way to configure different notification intervals > for different contacts? Especially I would like to configure > different notification intervals for EMail and SMS. > > I checked the host and service escalation objects, but AFAICS > they are bound to a specific host or service. This is not what > I need. And Google did not help, either. > > > Many thanx > > Harri > > > > -- > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > ___ > 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 _ Insert movie times and more without leaving Hotmail®. http://windowslive.com/Tutorial/Hotmail/QuickAdd?ocid=TXT_TAGLM_WL_HM_Tutorial_QuickAdd_062009-- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge___ 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] notification_interval depending upon contact
Hi folks, Is there some way to configure different notification intervals for different contacts? Especially I would like to configure different notification intervals for EMail and SMS. I checked the host and service escalation objects, but AFAICS they are bound to a specific host or service. This is not what I need. And Google did not help, either. Many thanx Harri -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ 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] Notification_interval
Hi,
I'm running nagios 3.0.6 on a debian etch system.
I builded a setup that was easy to manage, but now i have the problem
that i can't change my notification intervals.
When i take a look in the nagios web interface my notification
intervals are configured as 0h 30m 0s.
My config looks like this.
/etc/nagios3/conf.d/Services/
In this folder i define all my services, my ping service looks like
this:
# Service definition
define service{
use generic-service
; Name of service template to use
namegeneric-om-ping
service_description PING
is_volatile 0
check_period24x7
max_check_attempts 3
check_interval 5
retry_interval 1
notification_interval 10
notification_period 24x7
notification_optionsc,r
check_command check_ping!60.0,20%!400.0,60%
register0 ; DONT REGISTER THIS
DEFINITION - ITS NOT A REAL
SERVICE, JUST A TEMPLATE!
active_checks_enabled 1 ; Active service checks are disabled
passive_checks_enabled 1 ; Passive service checks are
enabled/disabled
}
Then i have a folder per client where i define the services the client
is allowed to use:
define service{
use generic-om-
ping ; Name of service template to use
hostgroup_name om-xen-linux-critical
contact_groups om-contact,om-sms
}
The service
define hostgroup {
hostgroup_name om-xen-linux-critical
alias Openminds XEN Servers
- kritisch
}
define host{
use linuxxen
host_name host
alias host Virtual Server
address ip.from.the.host
hostgroups om-xen-linux
}
My linuxxen en generic-host template look like this:
# Server host template
define host{
use generic-om-host ; Name of
host template to use
namelinuxxen
check_command check-host-alive
register0 ; DONT REGISTER THIS
DEFINITION - ITS NOT A REAL HOST, JUST A TEMPLATE!
}
Generic-host template:
define host{
name
generic-host; The name of this host template - referenced in other
host definitions, used for template recursion/resolution
notifications_enabled 0 ; Host
notifications are disabled
event_handler_enabled 0 ; Host event
handler is disabled
flap_detection_enabled 0 ; Flap
detection is disabled
process_perf_data 1 ;
Process performance data
retain_status_information 1 ; Retain
status information across program restarts
retain_nonstatus_information1 ; Retain non-status
information across program restarts
max_check_attempts 10;
register
0 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL HOST, JUST A
TEMPLATE!
}
Generic-service template:
# generic service template definition
define service{
namegeneric-service ; The 'name'
of this service template
active_checks_enabled 1 ; Active service
checks are enabled
passive_checks_enabled 1 ; Passive service
checks are enabled/accepted
parallelize_check 1 ; Active service
checks should be parallelized (disabling this can lead to major
performance problems)
obsess_over_service 0 ; We should obsess
over this service (if necessary)
check_freshness 0 ; Default is to NOT
check service 'freshness'
notifications_enabled 1 ; Service
notifications are enabled
event_handler_enabled 1 ; Service event
handler is enabled
flap_detection_enabled 0 ; Flap detection is
enabled
failure_prediction_enabled 1 ; Failure prediction
is enabled
process_perf_data 1 ; Process performance
data
retain_status_information 1 ; Retain status
information across program restarts
retain_nonstatus_information1 ; Retain non-status
information across program restarts
register0 ; DONT REGISTER THIS
DEFINITION - ITS NOT A REAL SERVICE, JUST A
Re: [Nagios-users] notification_interval seems to be ignored
> Just to wrap up this topic, I finally defeated this problem by changing > the output of my ambient temperature monitor to not return the actual > temperature in the server room. This made the message static and > unchanging and prevented repeated notifications from going out. I'm coming into this a bit late, but are you sure you don't have state_stalking enabled for this service? You will get a new notification if the various notification filters are passed, and: 1) The state has changed, or 2) The notification_interval has been reached, or 3) is_volatile is set, or 4) state_stalking is enabled, and the text output of the plugin has changed We use state_stalking for some services, eg SNMP error alerts (where we want to re-notify if a new alert comes in, but not if its just the same one again) Steve - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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] notification_interval seems to be ignored
Just to wrap up this topic, I finally defeated this problem by changing the output of my ambient temperature monitor to not return the actual temperature in the server room. This made the message static and unchanging and prevented repeated notifications from going out. I did completely stop and restart Nagios, but only after I made the above change, so I don't know for sure that my change caused the problem to go away, but I strongly suspect so. I didn't have the time to change the notifications script. However, notifications are logged in /var/log/syslog on my system. They always agree with the occurrence of notifications that I received. When I get some time, I'd be happy to try to investigate this problem further, since it's not supposed to happen and my solution removes some functionality that's desirable. If anyone can give me any pointers or documents regarding running Nagios in debug mode, I'll try it and report back my finding. Thanks, again, for all the help and suggestions offered regarding my problem. -Kevin -Original Message- From: Andreas Ericsson [mailto:[EMAIL PROTECTED] Sent: Monday, November 19, 2007 5:01 PM To: Zembower, Kevin Cc: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] notification_interval seems to be ignored Zembower, Kevin wrote: > Just a follow-up: Setting 'is_volatile 0' explicitly in the service > definition didn't seem to affect this behavior; it still sent me 3 > notifications, seemingly when the temperature changed. > Right, this is fairly weird. Escalations aren't in effect, is_volatile is set to zero. notification_interval is 0 and no other nagios install has this problem. Can you stop Nagios, make really sure it isn't running and start it again? Also verify that absolutely nothing else is sending notifications. You can do that by replacing the notification script with a home- hacked version that logs something somewhere every time it sends a notification and then cross-check that log with your notifications. If it still sends multiple notifications, It'll be quite hard to fix without enabling debugging in nagios, and that's quite tedious :-/ -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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] notification_interval seems to be ignored
Zembower, Kevin wrote: > Just a follow-up: Setting 'is_volatile 0' explicitly in the service > definition didn't seem to affect this behavior; it still sent me 3 > notifications, seemingly when the temperature changed. > Right, this is fairly weird. Escalations aren't in effect, is_volatile is set to zero. notification_interval is 0 and no other nagios install has this problem. Can you stop Nagios, make really sure it isn't running and start it again? Also verify that absolutely nothing else is sending notifications. You can do that by replacing the notification script with a home- hacked version that logs something somewhere every time it sends a notification and then cross-check that log with your notifications. If it still sends multiple notifications, It'll be quite hard to fix without enabling debugging in nagios, and that's quite tedious :-/ -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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] notification_interval seems to be ignored
Just a follow-up: Setting 'is_volatile 0' explicitly in the service definition didn't seem to affect this behavior; it still sent me 3 notifications, seemingly when the temperature changed. Thanks for any additional suggestions and advice. -Kevin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Zembower, Kevin Sent: Monday, November 19, 2007 2:11 PM To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] notification_interval seems to be ignored Andreas, thanks for your response. My notification_interval is set to 0, so theoretically it should send me either no repeated notifications, or a notification every 5 minutes, my normal_check_interval. I triggered an ambient temperature warning and let it run for an hour and 42 minutes. The time between notifications was 10, 26, 5, 12, 5, 5 and 25 minutes. In each case, the temperature had changed from the previous notification. The only definition of is_volatile was in the generic-service_nagios2.cfg files, where it's set to 0. I've now included it explicitly in the service definition for my ambient temperature monitor. I'll let you know if this makes a difference. Thanks, again, for your help. -Kevin iginal Message- From: Andreas Ericsson [mailto:[EMAIL PROTECTED] Sent: Monday, November 19, 2007 1:02 PM To: Zembower, Kevin Cc: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] notification_interval seems to be ignored Zembower, Kevin wrote: > Still trying to investigate why the notification_interval seems to be > ignored on my alert based on the ambient temperature in my server room. > It's not, but nagios only attempts to send notifications when it has performed a check, afair. If you set notification_interval to lower than your normal_check_interval, will it then send notifications with intervals matching normal_check_interval? > One thought that I had was that the temperature was changing between > alerts, even though it was still in the critical or warning state. Would > this cause repeated notifications to be sent out? Only if is_volatile is set for the service. -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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 SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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] notification_interval seems to be ignored
Andreas, thanks for your response. My notification_interval is set to 0, so theoretically it should send me either no repeated notifications, or a notification every 5 minutes, my normal_check_interval. I triggered an ambient temperature warning and let it run for an hour and 42 minutes. The time between notifications was 10, 26, 5, 12, 5, 5 and 25 minutes. In each case, the temperature had changed from the previous notification. The only definition of is_volatile was in the generic-service_nagios2.cfg files, where it's set to 0. I've now included it explicitly in the service definition for my ambient temperature monitor. I'll let you know if this makes a difference. Thanks, again, for your help. -Kevin iginal Message- From: Andreas Ericsson [mailto:[EMAIL PROTECTED] Sent: Monday, November 19, 2007 1:02 PM To: Zembower, Kevin Cc: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] notification_interval seems to be ignored Zembower, Kevin wrote: > Still trying to investigate why the notification_interval seems to be > ignored on my alert based on the ambient temperature in my server room. > It's not, but nagios only attempts to send notifications when it has performed a check, afair. If you set notification_interval to lower than your normal_check_interval, will it then send notifications with intervals matching normal_check_interval? > One thought that I had was that the temperature was changing between > alerts, even though it was still in the critical or warning state. Would > this cause repeated notifications to be sent out? Only if is_volatile is set for the service. -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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] notification_interval seems to be ignored
Zembower, Kevin wrote: > Still trying to investigate why the notification_interval seems to be > ignored on my alert based on the ambient temperature in my server room. > It's not, but nagios only attempts to send notifications when it has performed a check, afair. If you set notification_interval to lower than your normal_check_interval, will it then send notifications with intervals matching normal_check_interval? > One thought that I had was that the temperature was changing between > alerts, even though it was still in the critical or warning state. Would > this cause repeated notifications to be sent out? Only if is_volatile is set for the service. -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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] notification_interval seems to be ignored
Still trying to investigate why the notification_interval seems to be ignored on my alert based on the ambient temperature in my server room. One thought that I had was that the temperature was changing between alerts, even though it was still in the critical or warning state. Would this cause repeated notifications to be sent out? I've pasted in the last notification I received at the end of this message. Note that the duration is just 6 seconds, even though it arrived 10 minutes after the first notification. I also just received a third alert, 40 minutes after the first one. On this one, the temperature was also different from the second one. The duration was again 6 seconds. So, it does seem as if if the service message changes (the temperature value changes), the alert is sent again. Anyway to stop this feature, and only send alerts when the state changes? Thanks for your continued advice and suggestions. -Kevin * Nagios * Notification Type: PROBLEM Service: Ambient Temperature Host: www.jhuccp.org State: WARNING for 0d 0h 0m 6s Address: 10.253.192.204 Info: Temperature WARNING: CCP server room temperature of 69.8F exceeds warning temperature of 60 Date/Time: Mon Nov 19 11:36:28 EST 2007 ACK by: Comment: - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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] notification_interval seems to be ignored
> -Original Message- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Zembower, Kevin > Sent: Thursday, November 15, 2007 11:57 AM > To: nagios-users@lists.sourceforge.net > Subject: Re: [Nagios-users] notification_interval seems to be ignored > > Hmmm, I don't think that's the case. Wouldn't this show it: > [EMAIL PROTECTED]://etc/nagios2/conf.d$ ps aux |grep nagios > nagios 30699 0.0 0.6 22096 3364 ?SNsl Sep19 6:53 > /usr/sbin/nagios2 -d /etc/nagios2/nagios.cfg > I think the only instance of Nagios is PID 30699. Looks correct. Was the notification_interval ever set to 5? is_volatile enabled? Could you have possibly changed those settings since September 19 and not restarted nagios? I'd restart or HUP the daemon anyway just to be safe. -- Marc - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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] notification_interval seems to be ignored
I've written a custom plug-in to monitor the ambient temperature probe
on my Dell PowerEdge server. It's a wrapper around the standard
check_smtp plugin. It's been working correctly for months now. I pasted
the code for this in at the end of this message.
Yesterday at 2:00 the compressor failed in my server room and the
temperature went up to 90F. My notification was correctly sent, and I
was happy. However, I've received a notification every 5 minutes since
then that the temperature is over 80.
In the service definition, I have notification_intervals set to 0:
# check that ambient temperature from Dell sensor is less than 80 and 90
degree F.
# Notify the 'temp' group only.
define service {
hostgroup_name temp_sensor
service_description Ambient Temperature
check_command check_ambtempF!80!90
#For testing, set the temperature too low
# check_command check_ambtempF!60!70
use generic-service
notification_interval 0; set > 0 if you want to be
renotified
contact_groups temp
}
In generic-service.nagios2.cnf, the notification_interval is also set to
0. Furthermore, I don't have any escalations defined.
And, I just discovered that even though I disabled notifications for
this service using the nagios2 GUI, I'm still getting notified every
five minutes.
Can anyone suggest anything I can try to fix this behavior? Did I
overlook something in how I wrote the plugin?
My system is Nagios 2.6, as installed by the Debian 3.0 package system.
Thanks for any advice or suggestions.
-Kevin
Kevin Zembower
Internet Services Group manager
Center for Communication Programs
Bloomberg School of Public Health
Johns Hopkins University
111 Market Place, Suite 310
Baltimore, Maryland 21202
410-659-6139
[EMAIL PROTECTED]://etc/nagios2/conf.d$ cat
/usr/lib/nagios/plugins/check_ambtempF
#! /usr/bin/perl -w
# check_ambtempF is a perl wrapper around the Nagios check_snmp plugin
# to check the ambient temperature sensor in Dell PowerEdge servers.
# Written by Kevin Zembower, 13-Sep-2007
use strict;
use Getopt::Std;
my %opts;
getopts('dhc:w:H:',\%opts);
# Use this line below to dump the environment variables for debugging
system "env|sort >/tmp/plugins_env.$$" if defined($opts{d});
my %NAGIOS_ENV = map { $_ => $ENV{$_} } grep /^NAGIOS_/, keys %ENV;
if ( defined($opts{h}) ) {
print = $crit ) {
$output .= "CRITICAL: CCP server room temperature of ${tempF}F
exceeds critical temperature of $crit\n";
$output .= "Probable air conditioning failure.\n";
print $output;
exit 2;
} elsif ( defined $warn && $tempF >= $warn ) {
$output .= "WARNING: CCP server room temperature of ${tempF}F
exceeds warning temperature of $warn\n";
$output .= "Probable air conditioning failure.\n";
print $output;
exit 1;
} else {
$output .= "OK: CCP server room temperature is ${tempF}F\n";
print $output;
exit 0;
}
[EMAIL PROTECTED]://etc/nagios2/conf.d$
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
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] notification_interval seems to be ignored
I don't think the notification_interval was ever set to 5. I tried to set it to 15, to test it, but it made no difference. After every change I did '/etc/init.d/nagios2 reload'. I also just now did '/etc/init.d/nagios2 restart', but this also didn't have any effect; I'm still getting the notifications every 5 minutes. The only mention of 'is_volatile' is in /etc/nagios2/conf.d/generic-services_nagios2.cfg, where it's set to 0. Thanks for your thoughts and suggestions. -Kevin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marc Powell Sent: Thursday, November 15, 2007 2:05 PM To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] notification_interval seems to be ignored > -Original Message- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Zembower, Kevin > Sent: Thursday, November 15, 2007 11:57 AM > To: nagios-users@lists.sourceforge.net > Subject: Re: [Nagios-users] notification_interval seems to be ignored > > Hmmm, I don't think that's the case. Wouldn't this show it: > [EMAIL PROTECTED]://etc/nagios2/conf.d$ ps aux |grep nagios > nagios 30699 0.0 0.6 22096 3364 ?SNsl Sep19 6:53 > /usr/sbin/nagios2 -d /etc/nagios2/nagios.cfg > I think the only instance of Nagios is PID 30699. Looks correct. Was the notification_interval ever set to 5? is_volatile enabled? Could you have possibly changed those settings since September 19 and not restarted nagios? I'd restart or HUP the daemon anyway just to be safe. -- Marc - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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 SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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] notification_interval seems to be ignored
Hmmm, I don't think that's the case. Wouldn't this show it: [EMAIL PROTECTED]://etc/nagios2/conf.d$ ps aux |grep nagios nagios 30699 0.0 0.6 22096 3364 ?SNsl Sep19 6:53 /usr/sbin/nagios2 -d /etc/nagios2/nagios.cfg nagios 29497 0.0 0.1 2528 1016 pts/0S10:25 0:00 su -s /bin/bash - nagios nagios 29498 0.0 0.3 3268 1868 pts/0S10:25 0:00 -su nagios3034 0.0 0.1 2216 884 pts/0R+ 12:55 0:00 ps aux nagios3035 0.0 0.1 1644 556 pts/0S+ 12:55 0:00 grep nagios [EMAIL PROTECTED]://etc/nagios2/conf.d$ I think the only instance of Nagios is PID 30699. Thanks for your suggestion. -Kevin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marc Powell Sent: Thursday, November 15, 2007 12:34 PM To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] notification_interval seems to be ignored > -Original Message- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Zembower, Kevin > Sent: Thursday, November 15, 2007 10:54 AM > To: nagios-users@lists.sourceforge.net > Subject: [Nagios-users] notification_interval seems to be ignored > Yesterday at 2:00 the compressor failed in my server room and the > temperature went up to 90F. My notification was correctly sent, and I > was happy. However, I've received a notification every 5 minutes since > then that the temperature is over 80. > And, I just discovered that even though I disabled notifications for > this service using the nagios2 GUI, I'm still getting notified every > five minutes. > > Can anyone suggest anything I can try to fix this behavior? Did I > overlook something in how I wrote the plugin? These symptoms are consistent with having multiple nagios daemons running at the same time. -- Marc - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ 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 SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ 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] notification_interval seems to be ignored
> -Original Message- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Zembower, Kevin > Sent: Thursday, November 15, 2007 10:54 AM > To: nagios-users@lists.sourceforge.net > Subject: [Nagios-users] notification_interval seems to be ignored > Yesterday at 2:00 the compressor failed in my server room and the > temperature went up to 90F. My notification was correctly sent, and I > was happy. However, I've received a notification every 5 minutes since > then that the temperature is over 80. > And, I just discovered that even though I disabled notifications for > this service using the nagios2 GUI, I'm still getting notified every > five minutes. > > Can anyone suggest anything I can try to fix this behavior? Did I > overlook something in how I wrote the plugin? These symptoms are consistent with having multiple nagios daemons running at the same time. -- Marc - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ 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] "notification_interval" from the "serviceescalation" is ignored?
(Ilya: I have added the nagios-users mailing list back into the CC list.
Always make sure to include the mailing list so that others can follow
the discussion and possibly learn from it.)
On Sat, 2007-09-01 at 09:35 +0200, [EMAIL PROTECTED] wrote:
> > On Fri, 2007-08-31 at 09:56 +0200, Ilya Ruprecht wrote:
> >
> > > Ok, i understand. But netherless, something is wrong -
> > > look at my posting:
> > >
> > > the "notification_interval" of SSH is set to 60, but i became
> > > ALL notifications in 10 minute interval.
> >
> > In your original post, you said you defined this escalation:
> >
> > define serviceescalation{
> > hostgroup_name vpn-server
> > service_description SSH
> > first_notification 1
> > last_notification 5
> > notification_interval 3
> > contact_groups linux-admins
> > }
> >
> > That escalation takes effect on the first notification, and thus
> > notification_interval gets changed to "3". With the two escalations you
> > defined, the "notification_interval 60" line from your service
> > definition never takes effect.
>
> Exactly! That's what i mean! Neither the notification_interval from the
> service-definition, nor
> the notification_interval from the serviceescalation-definition was
> considered.
Yes, they are both considered. It's just that the notification_interval
from your escalation overrides the value from the service definition.
> But where then the 10-minutes interval came from? from the "check_interval"
> from service-definition?
Yes. That is what happens when you have a check_interval that is
greater than the notification_interval. A notification_interval of "3"
does not guarantee that notifications will be sent every 3 minutes. It
only guarantees that consecutive notifications will be 3 or more minutes
apart. If the check_interval is 10, then you will get notifications
every 10 minutes.
--
Rick Mohr
Systems Developer
Ohio Supercomputer Center
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
___
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] "notification_interval" from the "serviceescalation" is ignored?
On Thu, 2007-08-30 at 14:12 +0200, Ilya Ruprecht wrote: > Furthermore, the "notification_interval" in the service-part is described as > "Re-notify about service problems every XXX". > Note: "about service problems". > Now, if i set the notification_interval to a lower value then a > "normal_check_interval", i.e. "9", i get following warning-message > at nagios pre-flight-check: [snip] > But, hell, what the "normal_check_interval" have to do with > "notification_interval"?! > These two are completely different things! Or have i misunderstood something? Perhaps this will help clear things up. The "notification_interval" option sets an upper limit on how often notifications are sent. The "normal_check_interval" options controls how often the check is run. If notification_interval=10 and normal_check_interval=5, you can get a situation like this one (I'll use t=XX to try and convey the timeline when events occur). [t=0] Check runs. [t=0] Check fails. [t=0] Nagios sends notification. [t=5] Check runs [t=5] Check fails [t=5] Time since last notifications is 5 which is less than notification_interval=10. Nagios prevents notification. [t=10] Check runs. [t=10] Check fails. [t=10] Time since last notification is 10 which is greater than or equal to notification_interval=10. Nagios sends notification. However if notification_interval=5 and normal_check_interval=10, you get this. [t=0] Check runs. [t=0] Check fails. [t=0] Nagios sends notification. [t=10] Check runs. [t=10] Check fails. [t=10] Time since last notification is 10 which is greater than or equal to notification_interval=10. Nagios sends notification. Nagios only sends notifications immediately after a check (it won't resend an old value). So if normal_check_interval >= notification_interval, you effectively have notification_interval = normal_check_interval. That is why Nagios prints the warning message: "Warning: Service 'SSH' on host 'vpn-gw1-local' has a notification interval less than its check interval! Notifications are only re-sent after checks are made, so the effective notification interval will be that of the check interval." That seems to be what is happening in your case. -- Rick Mohr Systems Developer Ohio Supercomputer Center - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ 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] "notification_interval" from the "serviceescalation" is ignored?
Ilya Ruprecht wrote: > Hi all again! > > I installed Nagios 3.0b2 and tested the serviceescalations with it - with > the same result: > > "notification_interval" is ignored if i enter a value another then "0"(zero). > If i enter a zero - or even nothing - then i see in the webgui - > "Notify Only Once (No Re-notification)" in the "Notification Interval"-column > for > these hosts. > Even if I enter an clearly nonsense, like "jsdfjfsdakjl" - the value is > ignored and > the "pre-flight-check" dont brings an error. > > > It's a BUG! Isn't it? > It certainly appears to be, yes. -- Andreas Ericsson [EMAIL PROTECTED] OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ 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] "notification_interval" from the "serviceescalation" is ignored?
Hi all again! I installed Nagios 3.0b2 and tested the serviceescalations with it - with the same result: "notification_interval" is ignored if i enter a value another then "0"(zero). If i enter a zero - or even nothing - then i see in the webgui - "Notify Only Once (No Re-notification)" in the "Notification Interval"-column for these hosts. Even if I enter an clearly nonsense, like "jsdfjfsdakjl" - the value is ignored and the "pre-flight-check" dont brings an error. It's a BUG! Isn't it? Ilya - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ 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] "notification_interval" from the "serviceescalation" is ignored?
Hi admins!
Following situation: Debian 4.0 + Nagios 3.0b1.
I defined a service-template SSH:
define service{
namecheck-ssh-service ; The
'name' of this service template
check_command check_ssh
service_description SSH
active_checks_enabled 1 ; Active
service checks are enabled
passive_checks_enabled 1 ; Passive
service checks are enabled/accepted
parallelize_check 1 ; Active
service checks should be parallelized (disabling this can lead to major
performance problems)
obsess_over_service 1 ; We should
obsess over this service (if necessary)
check_freshness 0 ; Default is to
NOT check service 'freshness'
notifications_enabled 1 ; Service
notifications are enabled
event_handler_enabled 1 ; Service event
handler is enabled
flap_detection_enabled 1 ; Flap
detection is enabled
failure_prediction_enabled 1 ; Failure
prediction is enabled
process_perf_data 1 ; Process
performance data
retain_status_information 1 ; Retain status
information across program restarts
retain_nonstatus_information1 ; Retain
non-status information across program restarts
is_volatile 0 ; The service
is not volatile
check_period24x7; The service
can be checked at any time of the day
max_check_attempts 3 ; Re-check the
service up to 3 times in order to determine its final (hard) state
normal_check_interval 10 ; Check the
service every 10 minutes under normal conditions
retry_check_interval1 ; Re-check the
service every two minutes until a hard state can be determined
contact_groups linux-admins; Notifications
get sent out to everyone in the 'admins' group
notification_optionsw,u,c,r ; Send
notifications about warning, unknown, critical, and recovery events
notification_interval 60 ; Re-notify
about service problems every hour
notification_period 24x7; Notifications
can be sent out at any time
register0 ; DONT REGISTER
THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
}
Then i defined a hostgroup, for which i use the SSH service
define hostgroup{
hostgroup_name vpn-server
alias VPN-Gateways
members vpn-gw1-remote,vpn-gw1-local
}
Now i defined a service that uses the SSH-template and
is applied to the group "vpn-server"
define service{
use check-ssh-service
notes SSH auf Linux-Servern
hostgroup_name vpn-server
service_description SSH
}
And at last i defined two service-escalations for SSH
(i've set the intervals so short only for testing purposes)
define serviceescalation{
hostgroup_name vpn-server
service_description SSH
first_notification 1
last_notification 5
notification_interval 3
contact_groups linux-admins
}
define serviceescalation{
hostgroup_name vpn-server
service_description SSH
first_notification 5
last_notification 0
notification_interval 10
contact_groups linux-admins
}
"interval_length" is set to 60 seconds in nagios.cfg.
So far, so good.
1. PROBLEM:
===
Now, i get following notifications (these here are the syslog-entries):
Aug 30 13:05:38 unicorn nagios: SERVICE ALERT:
vpn-gw1-local;SSH;CRITICAL;SOFT;1;CRITICAL - Socket timeout after 10 seconds
Aug 30 13:06:38 unicorn nagios: SERVICE ALERT:
vpn-gw1-local;SSH;CRITICAL;SOFT;2;CRITICAL - Socket timeout after 10 s
[Nagios-users] notification_interval
Hi list Is possible to define a different notification_interval for each contactgroup?? What i want to do? I want for the same service different contacgroups to be notifified with a different interval. (grp1 every 3h and grp2 every 5h). Or the only way to do this is using service/host escalations? Regards <> --- --- --- <> Brandino Andreas [EMAIL PROTECTED] <> --- --- --- <> - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ 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] notification_interval in serviceescalation ignored
++ 22/02/07 17:35 +0100 - Sjaak Nabuurs: >Looks like an performance issue, long timeouts on plugins. >Can you track the check_execution_time and the check_latency when you >have an escalation. Generally, these seem to be allright. At any given time the service check latency is about 3 to 10 seconds on average, the service check execution time is on average less then 1 second. I don't believe these are too high (375+ hosts, 1775+ services). However after posting the previous post, I re-read the documentation for the n'th time and I came across this particular line: | In any case where there are multiple valid escalation definitions | for a particular notification, Nagios will choose the smallest | notification interval. And I believe this is exactly my problem. So, I rewrote the config and I am now awaiting a live example (and if that takes too long, I will create a long-lasting critical :)). -- Rejo Zenger <[EMAIL PROTECTED]> https://rejo.zenger.nl signature.asc Description: Digital signature - 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___ 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] notification_interval in serviceescalation ignored
Hello Rejo
Looks like an performance issue, long timeouts on plugins.
Can you track the check_execution_time and the check_latency when you
have an escalation.
Any sugestion on performance : parralizing check's.
Monitor how much nagios processes on good and bad times are running.
Sjaak
Rejo Zenger wrote:
>Hi there,
>
>I am still strugling with the following problem. I do not expect this to
>be a bug, but until now I have not been able to get it working the way I
>want it. Anybody with a good suggestion?
>
>
>
>
>>The problem in short: the escalations are working like a charm, but the
>>notification interval of the escalation seems to be ignored. In more
>>detail, the configuration is as follows:
>>
>>| define serviceescalation {
>>| first_notification 1
>>| last_notification 0
>>| notification_interval 900
>>| contact_groups cg-all-sane
>>| service_description $service
>>| host_name $host
>>| escalation_options r,w,u,c
>>| }
>>
>>| define serviceescalation {
>>| first_notification 12
>>| last_notification 0
>>| notification_interval 3600
>>| escalation_period twentyfourseven
>>| contact_groups cg-storingsdienst-escalatie
>>| service_description $service
>>| host_name $host
>>| escalation_options r,c
>>| }
>>
>>| define serviceescalation {
>>| first_notification 4
>>| last_notification 0
>>| notification_interval 1800
>>| escalation_period twentyfourseven
>>| contact_groups cg-storingsdienst
>>| service_description $service
>>| host_name $host
>>| escalation_options r,w,u,c
>>| }
>>
>>| interval_length=1
>>
>>| define service {
>>| name s
>>| register 0
>>| max_check_attempts 6
>>| normal_check_interval 120
>>| retry_check_interval 20
>>| check_period twentyfourseven
>>| notification_interval 300
>>| notification_period twentyfourseven
>>| notifications_enabled 1
>>| register 0
>>| notification_options w,u,c,r,f
>>| contact_groups cg-all-insane
>>
>>I believe this would, in case of a long lasting problem, result in:
>>- a notification to all contacts in cg-all-sane every 15 minutes, starting
>> immediatelly when there is a problem
>>- a notification to all contacts in cg-storingsdienst every 30 minutes if
>> problem has not been resovled or acknowledged within 20 minutes
>>- a notification to all contacts in cg-storingsdienst-escalatie every 60
>> minutes if problem has not been resovled or acknowledged within 1 hour
>>
>>There are no overlaps in contacts between the various contactgroups (I have
>>created separate e-mailaddresses to be notified, to avoid problems).
>>
>>Testing this setup resulted in the following notifications:
>>
>> 07:50:44 cg-all-sane
>> 08:07:32 cg-all-sane
>> 08:24:32 cg-all-sane
>> 08:41:24 cg-all-sane, cg-storingsdienst
>> 08:58:19 cg-all-sane, cg-storingsdienst
>> 09:15:10 cg-all-sane, cg-storingsdienst
>> 09:32:16 cg-all-sane, cg-storingsdienst
>> 09:49:25 cg-all-sane, cg-storingsdienst
>> 10:06:31 cg-all-sane, cg-storingsdienst
>> 10:23:38 cg-all-sane, cg-storingsdienst
>> 10:40:38 cg-all-sane, cg-storingsdienst
>> 10:57:40 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
>> 11:14:46 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
>> 11:29:49 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
>> 11:46:58 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
>>
>>After this the problem was resolved. I am happy with the escalation, but the
>>thing that does not work is the notification interval. It seems the setting
>>is being ignored. What is it I am doing wrong here?
>>
>>
>
>Any help is appreciated.
>
>
>
>
>
>-
>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
>
>
>
>___
>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
>
>
>
>No virus found in this incoming message.
>Checked by AVG Free Edition.
>Version: 7.5.441 / Virus Database: 268.18.3/696 - Release Date: 21-2-2007 15:19
>
>
--
Re: [Nagios-users] notification_interval in serviceescalation ignored
Hi there,
I am still strugling with the following problem. I do not expect this to
be a bug, but until now I have not been able to get it working the way I
want it. Anybody with a good suggestion?
>The problem in short: the escalations are working like a charm, but the
>notification interval of the escalation seems to be ignored. In more
>detail, the configuration is as follows:
>
> | define serviceescalation {
> | first_notification 1
> | last_notification 0
> | notification_interval 900
> | contact_groups cg-all-sane
> | service_description $service
> | host_name $host
> | escalation_options r,w,u,c
> | }
>
> | define serviceescalation {
> | first_notification 12
> | last_notification 0
> | notification_interval 3600
> | escalation_period twentyfourseven
> | contact_groups cg-storingsdienst-escalatie
> | service_description $service
> | host_name $host
> | escalation_options r,c
> | }
>
> | define serviceescalation {
> | first_notification 4
> | last_notification 0
> | notification_interval 1800
> | escalation_period twentyfourseven
> | contact_groups cg-storingsdienst
> | service_description $service
> | host_name $host
> | escalation_options r,w,u,c
> | }
>
> | interval_length=1
>
> | define service {
> | name s
> | register 0
> | max_check_attempts 6
> | normal_check_interval 120
> | retry_check_interval 20
> | check_period twentyfourseven
> | notification_interval 300
> | notification_period twentyfourseven
> | notifications_enabled 1
> | register 0
> | notification_options w,u,c,r,f
> | contact_groups cg-all-insane
>
>I believe this would, in case of a long lasting problem, result in:
> - a notification to all contacts in cg-all-sane every 15 minutes, starting
> immediatelly when there is a problem
> - a notification to all contacts in cg-storingsdienst every 30 minutes if
> problem has not been resovled or acknowledged within 20 minutes
> - a notification to all contacts in cg-storingsdienst-escalatie every 60
> minutes if problem has not been resovled or acknowledged within 1 hour
>
>There are no overlaps in contacts between the various contactgroups (I have
>created separate e-mailaddresses to be notified, to avoid problems).
>
>Testing this setup resulted in the following notifications:
>
> 07:50:44 cg-all-sane
> 08:07:32 cg-all-sane
> 08:24:32 cg-all-sane
> 08:41:24 cg-all-sane, cg-storingsdienst
> 08:58:19 cg-all-sane, cg-storingsdienst
> 09:15:10 cg-all-sane, cg-storingsdienst
> 09:32:16 cg-all-sane, cg-storingsdienst
> 09:49:25 cg-all-sane, cg-storingsdienst
> 10:06:31 cg-all-sane, cg-storingsdienst
> 10:23:38 cg-all-sane, cg-storingsdienst
> 10:40:38 cg-all-sane, cg-storingsdienst
> 10:57:40 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
> 11:14:46 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
> 11:29:49 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
> 11:46:58 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
>
>After this the problem was resolved. I am happy with the escalation, but the
>thing that does not work is the notification interval. It seems the setting
>is being ignored. What is it I am doing wrong here?
Any help is appreciated.
--
Rejo Zenger <[EMAIL PROTECTED]> https://rejo.zenger.nl
signature.asc
Description: Digital signature
-
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___
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] notification_interval in serviceescalation ignored
++ 14/02/07 20:34 +0100 - Hugo van der Kooij:
>> The problem in short: the escalations are working like a charm, but the
>> notification interval of the escalation seems to be ignored. In more
>> detail, the configuration is as follows:
>>
>> | define serviceescalation {
>> | first_notification 1
>> | last_notification 0
>> | notification_interval 900
>> | contact_groups cg-all-sane
>> | service_description $service
>> | host_name $host
>> | escalation_options r,w,u,c
>> | }
>
>That would 900 * the standard time unit.
>
>That satndard unit being 60 seconds in most installations gets you a
>notification every 900 minutes which is every 15 hours.
Which is why I quoted that particular setting in my original posting as
well: "interval_length=1" In other words, this is 900 times 1 second
which equals 15 minutes.
The problem is the setting "notification_interval" seems to be ignored.
I see too many notifications, not too little. :)
--
Rejo Zenger <[EMAIL PROTECTED]> https://rejo.zenger.nl
signature.asc
Description: Digital signature
-
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___
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] notification_interval in serviceescalation ignored
On Wed, 14 Feb 2007, Rejo Zenger wrote:
> The problem in short: the escalations are working like a charm, but the
> notification interval of the escalation seems to be ignored. In more
> detail, the configuration is as follows:
>
> | define serviceescalation {
> | first_notification 1
> | last_notification 0
> | notification_interval 900
> | contact_groups cg-all-sane
> | service_description $service
> | host_name $host
> | escalation_options r,w,u,c
> | }
That would 900 * the standard time unit.
That satndard unit being 60 seconds in most installations gets you a
notification every 900 minutes which is every 15 hours.
Hugo.
--
[EMAIL PROTECTED] http://hvdkooij.xs4all.nl/
This message is using 100% recycled electrons.
-
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
___
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] notification_interval in serviceescalation ignored
Hi there,
The problem in short: the escalations are working like a charm, but the
notification interval of the escalation seems to be ignored. In more
detail, the configuration is as follows:
| define serviceescalation {
| first_notification 1
| last_notification 0
| notification_interval 900
| contact_groups cg-all-sane
| service_description $service
| host_name $host
| escalation_options r,w,u,c
| }
| define serviceescalation {
| first_notification 12
| last_notification 0
| notification_interval 3600
| escalation_period twentyfourseven
| contact_groups cg-storingsdienst-escalatie
| service_description $service
| host_name $host
| escalation_options r,c
| }
| define serviceescalation {
| first_notification 4
| last_notification 0
| notification_interval 1800
| escalation_period twentyfourseven
| contact_groups cg-storingsdienst
| service_description $service
| host_name $host
| escalation_options r,w,u,c
| }
| interval_length=1
| define service {
| name s
| register 0
| max_check_attempts 6
| normal_check_interval 120
| retry_check_interval 20
| check_period twentyfourseven
| notification_interval 300
| notification_period twentyfourseven
| notifications_enabled 1
| register 0
| notification_options w,u,c,r,f
| contact_groups cg-all-insane
I believe this would, in case of a long lasting problem, result in:
- a notification to all contacts in cg-all-sane every 15 minutes, starting
immediatelly when there is a problem
- a notification to all contacts in cg-storingsdienst every 30 minutes if
problem has not been resovled or acknowledged within 20 minutes
- a notification to all contacts in cg-storingsdienst-escalatie every 60
minutes if problem has not been resovled or acknowledged within 1 hour
There are no overlaps in contacts between the various contactgroups (I have
created separate e-mailaddresses to be notified, to avoid problems).
Testing this setup resulted in the following notifications:
07:50:44 cg-all-sane
08:07:32 cg-all-sane
08:24:32 cg-all-sane
08:41:24 cg-all-sane, cg-storingsdienst
08:58:19 cg-all-sane, cg-storingsdienst
09:15:10 cg-all-sane, cg-storingsdienst
09:32:16 cg-all-sane, cg-storingsdienst
09:49:25 cg-all-sane, cg-storingsdienst
10:06:31 cg-all-sane, cg-storingsdienst
10:23:38 cg-all-sane, cg-storingsdienst
10:40:38 cg-all-sane, cg-storingsdienst
10:57:40 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
11:14:46 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
11:29:49 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
11:46:58 cg-all-sane, cg-storingsdienst, cg-storingsdienst-escalatie
After this the problem was resolved. I am happy with the escalation, but the
thing that does not work is the notification interval. It seems the setting
is being ignored. What is it I am doing wrong here?
Thank you in advance for your help. It's the only showstopper for the
implementation of this nagios instance... :)
PS. Only modifications to config bits above are a replacement of service and
host.
--
Rejo Zenger <[EMAIL PROTECTED]> https://rejo.zenger.nl
signature.asc
Description: Digital signature
-
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___
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] notification_interval (per user)
Hi Matteo You can use escalations to change to notifying some on the first notification and others on the second and all subsequent notifications. - David Schlecht (dschl) --- This thread is located in the archive at this URL: http://www.nagiosexchange.org/nagios-users.34.0.html?&tx_maillisttofaq_pi 1[showUid]=21914 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ 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] notification_interval (per user)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > [EMAIL PROTECTED] wrote on 15/09/2006 10:37:59: > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi, >> >> I know that it is possible to limit to 1 the number of sent out messages >> with the notification_interval option but as far as I know this is just >> possible in the definition of hosts and services. >> >> Instead I would like to set it for one contact. In other words I would >> like that a single contact receives the notifications just once. > > Set the notification_interval to 0 which makes sure that only 1 email or > page is sent out > > It's in the docs if you need further info Thanks. I know but this (as far as I understood) can only be set for a given service not a given contact. This means that I should duplicate *every* service and for each service: service1 notify contact_sms once per sms service1 notify contact every 120m per email I have more or less 50 entries that I should duplicate. I would like something like service1 notify contact_sms, contact per sms and email and then in contacs.cfg set globally that corti_sms should receive only one notification. Thanks again Matteo - -- Matteo Corti ETH Zurich [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFCqcXLEG/T0gggJsRAluDAKCtPGsf+oElLQLvYXmcV5Ufk58WtQCeJdKd jKtEY9azL82leHcTQc8ST64= =Bo7X -END PGP SIGNATURE- - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ 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] notification_interval (per user)
[EMAIL PROTECTED] wrote on 15/09/2006 10:37:59: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > I know that it is possible to limit to 1 the number of sent out messages > with the notification_interval option but as far as I know this is just > possible in the definition of hosts and services. > > Instead I would like to set it for one contact. In other words I would > like that a single contact receives the notifications just once. Set the notification_interval to 0 which makes sure that only 1 email or page is sent out It's in the docs if you need further info rob This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. ** BNP Paribas Private Bank London Branch is authorised by CECEI & AMF and is regulated by the Financial Services Authority for the conduct of its investment business in the United Kingdom. BNP Paribas Securities Services London Branch is authorised by CECEI & AMF and is regulated by the Financial Services Authority for the conduct of its investment business in the United Kingdom. BNP Paribas Fund Services UK Limited is authorised and regulated by the Financial Services Authority - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ 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] notification_interval (per user)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I know that it is possible to limit to 1 the number of sent out messages with the notification_interval option but as far as I know this is just possible in the definition of hosts and services. Instead I would like to set it for one contact. In other words I would like that a single contact receives the notifications just once. In my case I have two contacts: corti_sms and corti with different notification periods. It would be nice if I could (for the same service) have regular emails sent to corti and just one sms sent to corti_sms. Any suggestion? Many thanks, Matteo - -- Matteo Corti ETH Zurich [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFCnR3LEG/T0gggJsRAmd7AKDPOPoEFvRqqpC64JMqEaaGeXR9rQCghCYt 1G0mqn8gQyCCfCFV+SdV1/Q= =md/R -END PGP SIGNATURE- - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ 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] notification_interval = 0 and retained state but still get notifications on restart
> -Original Message- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Colm Ennis > Sent: Friday, February 10, 2006 1:27 PM > To: nagios-users@lists.sourceforge.net > Subject: [Nagios-users] notification_interval = 0 and retained state but > still get notifications on restart > > i use nagios 1.2. > > i have set: > notification_interval = 0 > for all hosts and services as we only want to be alerted once when a > host/service goes down. > > i have many devices/services and so autoprovision nagios config updates > nightly. > > in order to load these config changes i restart nagios. to reduce the > impact of this we retain state across restarts using: > retain_state_information=1 > use_retained_program_state=1 > > however when nagios restarts it alerts for all hosts/services which are > down despite haveing notification_interval = 0. I'm doing pretty much the same thing and I don't see this problem. It's a little bit different in that all my checks are passive but that shouldn't be a significant difference. Do you have the following directives in your host/service definitions or templates -- retain_status_information 0 ; Retain status information across program restarts retain_nonstatus_information1 ; Retain non-status information across program restarts In my case I don't retain_status_information, you will probably want to. Another difference is that I have a really high notification_interval as opposed to 0 but I don't expect that to be significant either -- notification_interval 10080 > > is there a way to do either of the following: > a) load new config without restarting nagios Send nagios a HUP signal. -- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ 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] notification_interval = 0 and retained state but still get notifications on restart
i use nagios 1.2. i have set: notification_interval = 0 for all hosts and services as we only want to be alerted once when a host/service goes down. i have many devices/services and so autoprovision nagios config updates nightly. in order to load these config changes i restart nagios. to reduce the impact of this we retain state across restarts using: retain_state_information=1 use_retained_program_state=1 however when nagios restarts it alerts for all hosts/services which are down despite haveing notification_interval = 0. is there a way to do either of the following: a) load new config without restarting nagios b) stop nagios alerting a host/service on restart if it has already done so and notification_interval = 0? does this happen in 2.0? should i upgrade? thanks for your help, colm --- 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://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 ___ 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
