We have completed some more testing and we can confirm the following:
- If you use a timezone such as Europe/London, then the bug was
triggered between 2009-10-25 23:00:00 and 2009-10-26 00:00:00
- If you use a timezone such as America/New_York, then the bug will be
triggered between 2009-11
Just to clarify, this affects all versions of Opsview from 2.14.2 to
3.3.2 (latest).
--
James
___
Opsview-users mailing list
Opsview-users@lists.opsview.org
http://lists.opsview.org/lists/listinfo/opsview-users
Same here, got lot's of stale this morning that just been kickoff by mass
check
On Mon, Oct 26, 2009 at 13:22, Mark Maas-Martin wrote:
> Hi All,
>
> From what I've seen, a simple mass re-check was enough to "kick" opsview
> into high gear again.
>
> Hope it helps,
> Mark Maas
> - "Ton Voon"
Hi All,
>From what I've seen, a simple mass re-check was enough to "kick" opsview into
>high gear again.
Hope it helps,
Mark Maas
- "Ton Voon" wrote:
> Hi,
>
>
>
> We've been made aware about a Nagios scheduling bug today. It seems to
>
> be due to the timezone changes that have occurr
Hi,
We've been made aware about a Nagios scheduling bug today. It seems to
be due to the timezone changes that have occurred in many European
countries.
The issue is that active checks are scheduled 24 hours later than
expected, which means you could be missing out on monitoring during
