[ZBX-15238] Incorrect nextcheck time in discovery rules Created: 2018 Nov 29  Updated: 2024 Apr 10  Resolved: 2018 Dec 11

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 3.0.24, 4.0.2
Fix Version/s: 3.0.25rc1, 4.0.3rc1, 4.2.0alpha2, 4.2 (plan)

Type: Problem report Priority: Minor
Reporter: Alexey Pustovalov Assignee: Andrejs Sitals (Inactive)
Resolution: Fixed Votes: 0
Labels: networkdiscovery
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: Team A
Sprint: Sprint 46, Nov 2018, Sprint 47, Dec 2018
Story Points: 0.25

 Description   

Zabbix stores current timestamp before getting and process network discovery rules. If a rule has many IP addresses or multiple services to check it can finish after new next timestamp:

So current process has the following steps:
1. Store current time
2. Perform select query for discovery rules
2.1. Perform discovery rule check
2.2. Update nextcheck field: time from 1 step + rule delay
2.3. Back to 2.1 in case of multiple rules per process

 Comments   
Comment by Andrejs Sitals (Inactive) [ 2018 Dec 03 ]

Fixed in development branches:

  • svn://svn.zabbix.com/branches/dev/ZBX-15238-30
  • svn://svn.zabbix.com/branches/dev/ZBX-15238-40
Comment by Andrejs Sitals (Inactive) [ 2018 Dec 07 ]

Available in versions:

  • pre-3.0.25rc1 r87621
  • pre-4.0.3rc1 r87622
  • pre-4.2.0alpha2 (trunk) r87623
Generated at Thu Apr 03 06:57:43 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.