-
Type:
Incident report
-
Resolution: Won't fix
-
Priority:
Major
-
None
-
Affects Version/s: 1.4.3
-
Component/s: Server (S)
-
None
-
Environment:Virtualised environment
When a forward time leap occurs (in a virtualised environment), zabbix will
not perform any checks until that time has been reached.
For example: my virtual server jumped to the 1st of January 2038. After
resetting the date/time to the correct datetime, zabbix will idle till the
1st of January 2038.
Manually modifying 'items.nextcheck' to the current unixtime does not
help.
Please provide a manual solution or a 'forced check' functionality in
zabbix.