Hi, we have a windows 10 machine, with ~30 active checks. However all of them show a time with around 10 minutes in the past as 'latest check'. that triggers host unreachable due to .nodata-trigger.
checks are every 60 seconds and report current values.
Last check reports now 2019-06-04 07:03:38
zabbix current time is 07:13:38
windows 10 current time is 2019-06-04,07:13:37.777,+02:00
where does the wrong time for 'latest' check come from?
All other hosts show correct 'latest check'-time.
Thank you.
Stefan
checks are every 60 seconds and report current values.
Last check reports now 2019-06-04 07:03:38
zabbix current time is 07:13:38
windows 10 current time is 2019-06-04,07:13:37.777,+02:00
where does the wrong time for 'latest' check come from?
All other hosts show correct 'latest check'-time.
Thank you.
Stefan