[ZBX-18794] System time is out of sync flapping Created: 2020 Dec 21  Updated: 2023 Oct 25  Resolved: 2020 Dec 24

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 5.0.6
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Evren Yurtesen Assignee: Zabbix Support Team
Resolution: Won't fix Votes: 0
Labels: linux,, macro,, ntp, template,
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2020-12-21-11-32-06-730.png     PNG File image-2020-12-21-11-38-31-202.png    

 Description   

Steps to reproduce:

  1. Setup a machine with ~60s time difference with Zabbix server.
  2. Use Zabbix Linux template which checks system time difference

Result:
It causes flapping trigger execution on borderline cases. See screenshot (I had the {$SYSTEM.FUZZYTIME.MAX} set as 30s

Expected:
Only one warning/problem entry until issue is fixed.

I suggest that a new variable {$SYSTEM.FUZZYTIME.MIN} is introduced which defaults to half of {$SYSTEM.FUZZYTIME.MAX}. Can macros have math?  maybe by default

{$SYSTEM.FUZZYTIME.MIN} = {$SYSTEM.FUZZYTIME.MAX} / 2 ?

or

{$SYSTEM.FUZZYTIME.MIN} = 30s (which is half of default 60s value)

Any suggestions are welcome?

 Comments   
Comment by Evren Yurtesen [ 2020 Dec 21 ]

The screenshot was lost in problem description...

Comment by Edgar Akhmetshin [ 2020 Dec 24 ]

Hello,

Time synchronisation must be configured on the servers. 30 seconds is already a lot.

Please be advised that this section of the tracker is for bug reports only. The case you have submitted can not be qualified as one, so please reach out to [email protected] for commercial support or consultancy services. Alternatively, you can also use our IRC channel or community forum (https://www.zabbix.com/forum) for assistance. With that said, we are closing this ticket. Thank you for understanding.

Regards,
Edgar

Comment by Evren Yurtesen [ 2020 Dec 29 ]

@edgar.akhmetshin It is a bug in the template. Because the trigger misbehaves. Trigger should NOT flap. I think you misunderstood the problem.

The problem is NOT the difference being 30 seconds or 60 seconds or how much the time difference is between a host and zabbix server.

The problem is when the difference is close to the limit set, the trigger starts flapping and sends many warnings unnecessarily. This can be avoided using hysteresis. You may want to read this blog entry if you want to learn about it. https://blog.zabbix.com/no-more-flapping-define-triggers-the-smart-way/1488/

I am not sure why you closed the ticket without waiting for me to respond. Can you please re-open it?

Comment by Joe [ 2023 Oct 25 ]

This bug is still present.....why was it closed?

Comment by Evren Yurtesen [ 2023 Oct 25 ]

The person who checked the issue apparently did not understand the nature of the problem from my description.

I tried to explain again but got no response. I do not know if they receive updates about this bug. So possibly nobody read my last message.

Perhaps you could make a new bug report and link to this one? put the link here too and I can vote it up. Thanks!

Generated at Mon May 12 08:01:02 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.