nagios doesn't respect the freshness_threshold

[Mario Garcia Ortiz]

Hello,
thank you for your answer.

I don't know what are you saying about spamming, I have sent the
message just once and this six days ago!

kind regards
--
Mario Garcia Ortiz
ABSI SA
224 Bd de l'Humanité
1190 Brussels  Belgium
www.absi.be
Tel 00 322 333 40 00





On 13 March 2012 02:37, Thomas Guyot-Sionnest <dermoth at aei.ca> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 12-03-09 04:34 AM, Mario Garcia Ortiz wrote:
> > Hello,
> > we have backups running everyday in which we send the status of the
> > backup via nsca to nagios, we have set a freshness_threshold of 26
> > hours in case the status of the backups is not received after 26hours
> > the check becomes critical.
> >
> > the problem is that nagios all of sudden doesn't respect that; when
> > the backup OK message is received by nagios via nsca, it becomes
> > critical after a couple of minutes instead of waiting the specified
> > freshness threshold period..
> >
> > is there a way to solve this issue? this happens with nagios running
> > on solaris 10.
>
> Please DO NOT spam the list by posting multiple times - you should
> expect at least one day to get an answer, if not more.
>
> Check that your check has "Active check disabled" from the interface -
> if active checks are enabled that's your issue.
>
> - --
> Thomas
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk9epMAACgkQ6dZ+Kt5BchYatACfZMZN5keQvBUPxTtF766G2KVH
> 5RUAoKcR3R1KbFDlznRlOsIRu+9iFDJX
> =cGpR
> -----END PGP SIGNATURE-----

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
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