# SetLogPosition in future?

**URL:** <https://community.icinga.com/t/setlogposition-in-future/11663>\
**Category:** Icinga 2\
**Created:** [March 21, 2023, 3:34am UTC](https://community.icinga.com/t/setlogposition-in-future/11663 "2023-03-21T03:34:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![0xliam](https://community.icinga.com/user_avatar/community.icinga.com/0xliam/32/1513_2.png) [@0xliam](https://community.icinga.com/u/0xliam)\
**Post date:** [March 21, 2023, 3:46am UTC](https://community.icinga.com/t/setlogposition-in-future/11663/2 "2023-03-21T03:46:09Z")

</div>

After looking at the forums more, I discovered a post I made in 2020 which appears to be the same issue - [Last check in future? Unable to reschedule - #2 by twidhalm](https://community.icinga.com/t/last-check-in-future-unable-to-reschedule/4148/2) - I will try these steps again and see if it fixes it up.

Is this a bug I should raise on GitHub? Essentially what I think has happened is NTP or the HW clock on the host has jumped into the future, a whole heap of checks isolated to one zone got scheduled 3 months into the future, and then the clock recovered, but the checks remain stuck in the future.

---

_[View the full topic](https://community.icinga.com/t/setlogposition-in-future/11663)._