Ad Widget

Collapse

Lots of "UNKNOWN" after upgrade from 1.8.2 to 2.0.4

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • darktux
    Junior Member
    • Apr 2013
    • 11

    #1

    Lots of "UNKNOWN" after upgrade from 1.8.2 to 2.0.4

    Lots of hosts switch from "UNKNOWN" to whatever status they really have, i cant really pinpoint the problem.


    Does anybody have som suggestions.


    My setup:
    zabbix 2.0.4 with a postgresdb on another server.
    avg-cpu: %user %nice %system %iowait %steal %idle
    1.53 0.02 0.17 0.02 0.00 98.27

    load average: 0.03, 0.08, 0.05
    total used free shared buffers cached
    Mem: 7981 7307 674 0 477 5903
    -/+ buffers/cache: 925 7055
    Swap: 4094 20 4074


    Number of hosts (monitored/not monitored/templates) 323 190 / 82 / 51
    Number of items (monitored/disabled/not supported) 13835 10389 / 3067 / 379
    Number of triggers (enabled/disabled)[problem/unknown/ok] 2854 2399 / 455 [37 / 0 / 2362]
    Number of users (online) 44 5
    Required server performance, new values per second 136.51 -
    Last edited by darktux; 22-04-2013, 16:09. Reason: Problem solved
  • tchjts1
    Senior Member
    • May 2008
    • 1605

    #2
    I think you have 2 options... go to Zabbix version 2.0.5 or follow this post:


    Hope that helps.

    Comment

    • darktux
      Junior Member
      • Apr 2013
      • 11

      #3
      Originally posted by tchjts1
      I think you have 2 options... go to Zabbix version 2.0.5 or follow this post:


      Hope that helps.



      Thanks for your help, ive just changed the item/trigger. ill post back later to let you know.

      //P

      Comment

      • darktux
        Junior Member
        • Apr 2013
        • 11

        #4
        system[procrunning] was the problem

        After some logdiving i found that in one of our templates we where checking for: "system[procrunning]", and each time it did we got a "network error", and the host hung for 45 sec.
        I disabled the item and voila ! no more "UNKNOWN" status on items.
        I guess that while it was waiting to retry the failing item, our other items expired and becam "UNKNOWN"

        This is how our log looked:
        25799:20130422:124739.311 Zabbix agent item [system[procrunning]] on host [ns2] failed: first network error, wait for 45 seconds
        25786:20130422:124740.336 Zabbix agent item [system[procrunning]] on host [lb4] failed: first network error, wait for 45 seconds
        25798:20130422:124742.317 Zabbix agent item [system[procrunning]] on host [Prod15] failed: first network error, wait for 45 seconds
        25765:20130422:124747.397 Zabbix agent item [system[procrunning]] on host [prod23] failed: first network error, wait for 45 seconds
        25799:20130422:124748.531 Zabbix agent item [system[procrunning]] on host [Prod13] failed: first network error, wait for 45 seconds

        Have a nice day !

        Comment

        Working...