softstates and retry check intervals

Tharanga tharanga at roomsnet.com
Fri Jan 6 02:23:52 CET 2006


Hello,

Yes..i didnt include the nrpe thing here.but even for asterisk process it
gives crtical when first check fail. i need to recheck 3 times and throw the
critical alert..i think this can used to prevent NRPE time out over WAN link
to trigger false alarms.

thanks in advance
Tharanga



----- Original Message ----- 
From: "Tedman Eng" <teng at dataway.com>
To: "'Tharanga'" <tharanga at roomsnet.com>;
<nagios-users at lists.sourceforge.net>
Sent: Friday, January 06, 2006 2:44 AM
Subject: RE: [Nagios-users] softstates and retry check intervals


> > define service{
> >        use                             generic-service
> >        host_name                       Linux-PBX
> >        service_description             PBX-Asterisk process
> >        check_command                   check_snmp_process!asterisk
> >        }
>
> I don't see NRPE in your service config.
> How can NRPE be timing out if it's not defined (here)?
>
>
>
> > -----Original Message-----
> > From: Tharanga [mailto:tharanga at roomsnet.com]
> > Sent: Wednesday, January 04, 2006 6:03 PM
> > To: Danny Russell; nagios-users at lists.sourceforge.net
> > Subject: Re: [Nagios-users] softstates and retry check intervals
> >
> >
> > Hello Danny,
> >
> > Thxs for the immeidate reply. actualy i need to do this
> > "In order to prevent false alarms, Nagios allows you to
> > define how many
> > times a service or host check will be retried before the
> > service or host is
> > considered to have a real problem."
> >
> > but my one process went to NRPE time out..it gives critical
> > alert..but its a
> > false alarm. if nagios can check that service 3 times..if all
> > three times
> > fails..it should alert...
> > this is my servises.cfg
> >
> >
> > define service{
> >        use                             generic-service
> >  ; Name of
> > service template to use
> >
> >        host_name                       Linux-PBX
> >        service_description             PBX-Asterisk process
> >        is_volatile                     0
> >        check_period                    24x7
> >        max_check_attempts              3
> >        normal_check_interval           1
> >        retry_check_interval            1
> >        contact_groups                  linux-admins
> >        notification_interval           240
> >        notification_period             24x7
> >        notification_options            w,u,c,r
> >        check_command                   check_snmp_process!asterisk
> >        }
> >
> > thxs in advance
> > Tharanga
> >
> >
> >
> > ----- Original Message ----- 
> > From: "Danny Russell" <drussell at mpifix.com>
> > To: "Tharanga" <tharanga at roomsnet.com>;
> > <nagios-users at lists.sourceforge.net>
> > Sent: Thursday, January 05, 2006 7:46 AM
> > Subject: RE: [Nagios-users] softstates and retry check intervals
> >
> >
> > Notifications are only sent out for HARD States. The retry check
> > interval is how quickly should I start checking as soon as
> > this service
> > is in an non-okay status. The maximum check attempts is how many
> > consecutive checks must be the same before it is considered a hard
> > state, up until then it was a soft state.
> >
> > This can probably explain it better:
> > http://nagios.sourceforge.net/docs/2_0/statetypes.html
> >
> >
> >
> > -----Original Message-----
> > From: nagios-users-admin at lists.sourceforge.net
> > [mailto:nagios-users-admin at lists.sourceforge.net] On Behalf
> > Of Tharanga
> > Sent: Wednesday, January 04, 2006 6:38 PM
> > To: nagios-users at lists.sourceforge.net
> > Subject: [Nagios-users] softstates and retry check intervals
> >
> > Greetings,
> >
> > My nagios system alerts as critical when the system gives CHECK_NRPE
> > time
> > out. so..i need to retry 3 attempts using retry intervals..then after
> > this 3
> > checks i want to send the critical alert. but theres a method called
> > softstates in nagios.
> >
> > can any one help me to configure this..
> > thxs in advance
> > Tharanga
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> > files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.
> > DOWNLOAD SPLUNK!
> > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > ::: Please include Nagios version, plugin version (-v) and OS when
> > reporting any issue.
> > ::: Messages without supporting info will risk being sent to /dev/null
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep
> > through log files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.
> > DOWNLOAD SPLUNK!
> > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > ::: Please include Nagios version, plugin version (-v) and OS
> > when reporting any issue.
> > ::: Messages without supporting info will risk being sent to /dev/null
> >




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null





More information about the Users mailing list