Monitored host with wrong time breaks housekeeper logic on proxy

XMLWordPrintable

    • Type: Problem report
    • Resolution: Unresolved
    • Priority: Trivial
    • None
    • Affects Version/s: 5.2.5
    • Component/s: Proxy (P)
    • None

      Even if zabbix proxy is online, monitored host with wrong time will force housekeeper not to remove records from proxy_history table for up to ProxyOfflineBuffer.

      Steps to reproduce:
      On proxy:
      HousekeepingFrequency=1
      ProxyOfflineBuffer>48
      ProxyLocalBuffer=0

      Add few hosts to monitor via proxy.
      On one host disable ntp and set time to, for example, now() - 3d.

      Result:
      records in proxy_history table stored for 2 days.
      Expected:
      records deleted from proxy_history by housekeeper since proxy is online and ProxyLocalBuffer=0.

      There are two "clock" fields in proxy_history table:
      timestamp from monitored host written to clock
      timestamp from proxy itself written to write_clock

      housekeeper uses clock field to filter records, so wrong time on monitored host breaks delete logic.

            Assignee:
            Zabbix Support Team
            Reporter:
            Oleg Morozov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: