Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-9067

Solaris agent item system.cpu.util values returns 0.000000 after a few minutes

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Won't fix
    • Icon: Blocker Blocker
    • None
    • 2.4.0, 2.4.1
    • Agent (G)
    • zabbix_agents_2.4.1.solaris10.sparc

      Some system counters get set to 0.000000 some minutes after restart of agent on Solaris 10 (sparc).
      The time this happens varies, usually within 30 minutes of agent restart.
      These are the only items affected:

      system.cpu.util[,user]
      system.cpu.util[,system]
      system.cpu.util[,iowait]
      system.cpu.util[,idle]
      

      This behavior is observed with the Zabbix Solaris 10 (Sparc) agent version 2.4.0 and 2.4.1 (pre-compuled binary downloaded from Zabbix).

      See log with debug (attached) - first occurence of problem (13 minutes after start of agent):
      4918:20141121:102703.308 for key [system.cpu.util[,idle]] received value [0.000000]

      zabbix@HostName /opt/zabbix $ bin/zabbix_get -s localhost -k "system.cpu.switches"
      5723982175
      zabbix@HostName /opt/zabbix $ bin/zabbix_get -s localhost -k "system.cpu.util[,user]"
      0.000000
      zabbix@HostName /opt/zabbix $ bin/zabbix_get -s localhost -k "system.cpu.util[,system]"
      0.000000
      zabbix@HostName /opt/zabbix $ bin/zabbix_get -s localhost -k "system.cpu.util[,iowait]"
      0.000000
      zabbix@HostName /opt/zabbix $ bin/zabbix_get -s localhost -k "system.cpu.util[,idle]"
      0.000000
      

      <restart agent>

      zabbix@HostName  /opt/zabbix $ bin/zabbix_get -s localhost -k "system.cpu.util[,user]"
      2.330420
      zabbix@HostName /opt/zabbix $ bin/zabbix_get -s localhost -k "system.cpu.util[,idle]"
      94.382490
      

            Unassigned Unassigned
            ronny.pettersen@evry.com Ronny Pettersen
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: