CRIT "Snapshot with a creation time in the future" - All times look synced, didn't have that before 2.3

Troubleshooting
41

I changed the timezone in the docker-container of checkmk from CET to UTC and the error is gone. Waiting for sideefects…

42

Since updating to 2.2.0p36 of the Enterprise version, I’ve had the same problem but still have no idea how to solve it.

43

I have the same problem since updating to 2.2.0p36

44

same issue here as well after update to p36

45

The question here is what timezone has your vcenter and your CheckMK server?

46

In my case both vCenter and Checkmk server run on CET.

47

vCenter is in UTC, checkmk is in EET.
I’ve changed it now to UTC also, but this wasnt an issue until now.

48

Yes this combination should be no problem.
The most important part is, how does the timestamp from the vCenter looks like at such a problem time and what is your timestamp on the local machine at the same time.
There are different scenarios possible.

49

Hi all,
we are still running on Raw Edition which was updated yesterday to 2.2p36.
Since then we are faced with the same problem so it seems the Werk #17197 dos not fix!
Both, CheckMK Sites and vCenter are set on CET.
And furthermore we updated Ububtu to 24.04.1LTS before also and must realize there are known Problems with DNS in this release, could that be an Hint?

Thanks to all
Dieter

50

Hello,

Same issue for us since updating to 2.2p36.
vCenter GMT, vCenter CET.
Worked fine before the update

Thanks
Matthew

51

2.2.0.p37 fixed it for me.

1 Like
52

yes, it seems p37 fixed it for us also
thank’s a lot

53

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact an admin if you think this should be re-opened.