Ad Widget

Collapse

[1.4.4] Some active checks don't work

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • uweiss
    Junior Member
    • Jun 2006
    • 27

    #1

    [1.4.4] Some active checks don't work

    Hello,

    I have never used active checks before.
    Now i added some active checks for one of my hosts (the server itself for testing). Somehow some of them work fine, some don't.

    Everything which checks Processor load, Processes and System (uptime,...) works fine.

    But Memory, Network and Swap stuff does not work.

    I use "vm.memory.size[buffers]" here for example, but it's the same for all others which don't work.

    The agent was updated fine:
    Code:
     24190:20080110:130640 Parsed [vm.memory.size[buffers]:30:0]
     24190:20080110:130640 In add_check('vm.memory.size[buffers]', 30, 0)
    It can get the value but somehow fails:
    Code:
     24190:20080110:130841 For key [vm.memory.size[buffers]] received value [4833280]
     24190:20080110:130841 XML before sending [<req><host>bm1zMS5pY3Jjb20uY2g=</host><key>dm0ubWVtb3J5LnNpemVbYnVmZmVyc10=</key><data>NDgzMzI4MA==</data></req>]
     24190:20080110:130841 NOT OK [127.0.0.1:vm.memory.size[buffers]] [NOT OK]
    
     24190:20080110:131011 For key [vm.memory.size[buffers]] received value [1531904]
     24190:20080110:131011 XML before sending [<req><host>bm1zMS5pY3Jjb20uY2g=</host><key>dm0ubWVtb3J5LnNpemVbYnVmZmVyc10=</key><data>MTUzMTkwNA==</data></req>]
     24190:20080110:131011 NOT OK [127.0.0.1:vm.memory.size[buffers]] [NOT OK]
    But as soon i switch from "ZABBIX agent (active)" to "ZABBIX agent" the value is updated immediately. So i don't think it's a problem of the item configuration.

    Any ideas what that could be?

    Thank you
    Urs
  • uweiss
    Junior Member
    • Jun 2006
    • 27

    #2
    I now added the checks for my MySQL DB which are predefined in the agentd config.

    All defined as active checks in zabbix. All checks uses mysqladmin to get the values. But four of them work fine as active check, two (mysql.qps, mysql.uptime) don't.

    Same thing as in my first post:
    Code:
     22760:20080117:111433 Run remote command [mysqladmin -uzabbixchk -pxxx status|cut -f9 -d":"] Result [7] [ 77.197]...
     22760:20080117:111433 For key [mysql.qps] received value [ 77.197]
     22760:20080117:111433 XML before sending [<req><host>bm1zMDEuaWNyY29tLmNo</host><key>bXlzcWwucXBz</key><data>IDc3LjE5Nw==</data></req>]
     22760:20080117:111433 NOT OK [127.0.0.1:mysql.qps] [NOT OK]
    
     22760:20080117:111433 Run remote command [mysqladmin -uzabbixchk -pxxx status|cut -f2 -d":"|cut -f1 -d"T"] Result [9] [ 172152  ]...
     22760:20080117:111433 For key [mysql.uptime] received value [ 172152  ]
     22760:20080117:111433 XML before sending [<req><host>bm1zMDEuaWNyY29tLmNo</host><key>bXlzcWwudXB0aW1l</key><data>IDE3MjE1MiAg</data></req>]
     22760:20080117:111433 NOT OK [127.0.0.1:mysql.uptime] [NOT OK]
    Switching these two checks to "normal" check and they work fine.

    How can it be that two checks which only get a different part of the same output only works on one of them??

    Thanks
    Urs

    Comment

    Working...