[ZBX-17891] Re-reading the log file despite on skip, mtime-noreread options Created: 2020 Jun 09  Updated: 2024 Apr 10  Resolved: 2020 Jun 30

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 4.4.9, 5.0.1
Fix Version/s: 4.0.22rc1, 4.4.10rc1, 5.0.2rc1, 5.2.0alpha1, 5.2 (plan)

Type: Problem report Priority: Blocker
Reporter: Andrei Gushchin (Inactive) Assignee: Andris Zeila
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Team: Team A
Sprint: Sprint 65 (Jun 2020)
Story Points: 2

 Description   

Steps to reproduce:
have some log file on monitoring with zabbix agent active with key

log[/tmp/log.txt,,,101,skip,,120.0,mtime-noreread]

update the file regurarly

  • change time in the system back or forward (it could happen when system is rebooted)

Result:

  • agent re-read the file from begin every time despite on options and detecting the time changing and adjusting the mtime:
    26565:20200607:082950.670 the system time has been pushed back, adjusting active check schedule
     26565:20200607:082951.670 System clock has been set back in time. Setting agent mtime 46 seconds back.
     26565:20200607:072950.343 the system time has been pushed back, adjusting active check schedule
     26565:20200607:072951.344 System clock has been set back in time. Setting agent mtime 3675 seconds back.
    

Expected:
Do not re-read the file.



 Comments   
Comment by Andris Zeila [ 2020 Jun 10 ]

Released ZBX-17891 in:

  • pre-4.0.22rc1 94bdaae750
  • pre-4.4.10rc1 b547a36e3b
  • pre-5.0.2rc1 485536b2d2
  • pre-5.2.0alpha1 a4c5f9ed3f

Updated documentation:

Generated at Sun Apr 27 09:30:34 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.