Re: [Nagios-users] Time periods Issue

From: adi yesaya <adiyesaya(at)gmail.com>
Date: Wed Jun 27 2007 - 10:04:22 EDT

First i thought so too, but i tried to change the max_service_check_spread to 90 or 180 and it still happens. Does anyone have a clue?

On 6/27/07, Andy Harrison <aharrison@gmail.com> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> > Why if i schedule it couple hours ahead Nagios doesn't interleave the
> chekcs
> > but if i schedule it couple minutes ahead, it interleaves all the check?
> >
>
>
> I'm not certain, but it may have something to do with your
> max_service_check_spread being set to 60 minutes and it might be
> getting confused with your timeperiod definition being a span of only
> one hour.
>
> - --
> Andy Harrison
> public key: 0x67518262
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: http://firegpg.tuxfamily.org
>
> iD8DBQFGglIsNTm8fWdRgmIRAqruAKDZGjmw+YVAxUP3aohTTALOkZ/jpACgr8+F
> CQC+yTBRn893gFnmgyRNLIE=
> =cP2C
> -----END PGP SIGNATURE-----
>
> -------------------------------------------------------------------------
> 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
>

---

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 Received on Wed Jun 27 10:04:42 2007