Ad Widget

Collapse

W32 Agent "not supported"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • BrianC
    Junior Member
    • May 2006
    • 8

    #1

    W32 Agent "not supported"

    In the last couple of betas, and with 1.1, I cannot get most of the Windows agent checks to work.

    As a regular zabbix check, the log file shows:

    Parameter [diskused[c:]] is not supported by agent on host [host] Old status [0]

    The same parameter with an active check shows:

    Type of received value [ZBX_NOTSUPPORTED] is not suitable for [cpu_util5@host]

    I haven't tried all the Windows specific options, but so far only agent.ping is working. This is using the v1.1 server and agent, but I've had the problem since at least beta11. It was working with beta9.

    Also, I've never been able to get any actions to trigger. I've tried severity, severity + trigger value, trigger + trigger value, and trigger name + trigger value, but no combination has worked yet.
  • Eugene
    Member
    • Feb 2006
    • 57

    #2
    Now, Win32 ZABBIX agent use "global" naming for parameters of all platforms.

    For example:
    "diskfree", "disktotal", "diskused" - grouped to "vfs.fs.size"
    "cpu_util" ... "cpu_util15" - grouped to "system.cpu.util"

    See manual

    Comment

    • BrianC
      Junior Member
      • May 2006
      • 8

      #3
      That did the trick for the checks. Thanks. Now I just need to get actions working, but I'll start a seperate thread for that one.

      Comment

      Working...