Steps to reproduce:

1. Temporarily set server time forward eg. by 6 months
2. Start Zabbix server and let it run for a while so it updates trends tables; this will cause bogus "future" data (clock > now()) to be saved to tables trends and trends_uint
3. Restart server with correct time

Result:

• Tables trends and trends_uint fail to update, without error messages in the server log

Expected:

• error message in the server logs, or
• server updates trends nonetheless

Workaround implemented:

• cron job to update items with max(clock) from the trends tables
• trigger to indicate max(clock) > now()