Ad Widget

Collapse

zabbix server deamon hogs cpu! issue

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • JamesPatton
    Junior Member
    • Nov 2021
    • 2

    #1

    zabbix server deamon hogs cpu! issue

    000383:20060721:142801 Getting value of [ifDescr50] from host [ws2003.lan.xxxxx.xx] failed
    000383:20060721:142801 The value is not stored in database.
    000383:20060721:142801 Error doing snmp_open()


    this message repeats itself constantly with various other values(for the same host running windows and an snmp daemon. the serverd and mysql daemon top out at 40-45% cpu utilisation. removing the host through configuration resolves the cpu hogging and extensive error message logging. but what causes serverd to make such a mess of things?
  • cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4807

    #2
    Error doing snmp_open().
    I guess your host is not answering properly. Can you get values with snmpget/walk?
    And it would be good to always add info about you setup. Version, proxies/no proxies etc...

    Comment

    • JamesPatton
      Junior Member
      • Nov 2021
      • 2

      #3
      Thanks, sire. It helped me. Hadn't tried it before...

      Comment

      • LenR
        Senior Member
        • Sep 2009
        • 1005

        #4
        When that happens, Zabbix should put that item in "not supported" status to lower the load of failed items. SNMP can be slow to respond, what is your "timeout" setting? Zabbix should wait for "Refresh Unsupported Items" time before trying again. (It may try snmp items twice before they go unsupported). If these items are never going unsupported, you may need to increase your timeout setting.

        Comment

        Working...