[ZBX-22274] A note should be added to item test description that time between server and proxy should be in sync Created: 2023 Jan 27  Updated: 2024 Apr 10  Resolved: 2023 Feb 19

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Documentation (D)
Affects Version/s: 5.0.32rc1, 6.0.14rc1, 6.2.7rc1, 6.4.0rc1
Fix Version/s: 5.0.32rc1, 6.0.14rc1, 6.2.8rc1, 6.4.1rc1, 7.0.0alpha1, 7.0 (plan)

Type: Documentation task Priority: Trivial
Reporter: Sergejs Olonkins Assignee: Natalija Burisina (Inactive)
Resolution: Fixed Votes: 0
Labels: documentation, itemtest, taskmanager
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Team: Team D
Sprint: Sprint 96 (Jan 2023), Sprint 97 (Feb 2023)
Story Points: 0.125

 Description   

Problem description: in case if some host is monitored by proxy and server time is falling behind proxy time for a couple of minutes, then the item test functionality (which is described here) will not work properly, because the proxy will not process the request and will return an error message "The task has been expired."
This does not apply to cases when different timezones are used for proxy and server (item test works fine in this case).

Suggestion is to add a note ti the above mentioned documentation to make sure that server time and proxy time are synchronized (this doesn't apply to different timezones) to avoid such situations.



 Comments   
Comment by dimir [ 2023 Feb 01 ]

So, when server receives the task it sets the timestamp and then when proxy receives the request it ignores it because "too much time passed".

Shouldn't it be so that server just passes the request to the proxy and proxy just sets the "nextcheck" according to its time? In this case everything would be working fine. Looks like an easy fix.

Comment by Vladislavs Sokurenko [ 2023 Feb 01 ]

It depends, maybe it took too long to deliver the task and it shouldn't be executed.

Comment by Natalija Burisina (Inactive) [ 2023 Feb 09 ]

solonkins , thank you for reporting this.

 

Documentation updated:

Generated at Tue Jun 17 08:19:32 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.