Ad Widget

Collapse

Age or Last seen (age) counting backwards.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • adsandiego
    Junior Member
    • Feb 2015
    • 1

    #1

    Age or Last seen (age) counting backwards.

    Zabbix version 2.4.3
    zbx_server_1 has zabbix server installed (no zabbix agent installed)
    zbx_server_2 has zabbix proxy installed (no zabbix agent installed)
    zbx_server_3 has mysql installed (no zabbix agent installed)

    Zabbix agent version 2.4.1 and 2.4.2
    monitor_svr_1 is windows 2008 R2 and has zabbix agent installed
    monitor_svr_2 is windows 2008 R2 and has zabbix agent installed

    monitor_svr_1 is monitored through proxy
    monitor_svr_2 is monitored without proxy


    Question:
    - When i create a problem/trigger like stopping the Zabbix Agent service on monitor_svr_1/2, it will get displayed on the Dashboard under Last 20 issues with error message "Zabbix agent on monitor_svr_1/2 is unreachable for 5 minutes" but the Age is counting backwards and starts with "29m" then "28m 59s ..."
    - Same problem appears on monitor_svr_2.

    Troubleshooting Steps
    - restart zabbix-server
    - restart zabbix-proxy
    - restart zabbix-agent
  • adsandie
    Junior Member
    • Dec 2014
    • 2

    #2
    I just tried this on version 2.4.4.1 and 2.4.2.1.

    Age timestamp is correct on 2.4.2.1 and not on 2.4.4.1.

    Age timestamp starts from 0s on 2.4.2.1
    Age timestamp starts from 29m on 2.4.4.1

    Comment

    • bSpach
      Junior Member
      Zabbix Certified Specialist
      • Aug 2013
      • 12

      #3
      This usually happens when the time on your server does not quite match up with your workstation that you are accessing the GUI from. It is a PHP/httpd issue - it uses your local system time, not the time of the web server.

      You may also notice gaps at the ends of your graphs that makes it look as though the Zabbix server is behind in processing, when it is not.

      Syncing your clocks in all of your environments, using NTP, to the same time source is highly recommended.

      Comment

      • adsandie
        Junior Member
        • Dec 2014
        • 2

        #4
        Thanks, the time on zbx_server_1 was off from the web front end. I had to manually correct it since we're not using ntp.

        Comment

        Working...