Ad Widget

Collapse

Items: agent active / passive ?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • NOB
    Senior Member
    Zabbix Certified Specialist
    • Mar 2007
    • 469

    #1

    Items: agent active / passive ?

    Hi,

    in my simple mind I thought, that all checks (items) I can request from
    remote (passive) should also be possible locally by the agent (active).
    However, when I change, e.g., the check for disk free on drive e: (Windows)
    from "agent" to "agent (active)" no data are send.

    Is this expected or is it a bug in 1.3.5 (beta) ?

    Does it correspond to the problem with "zabbix_agentd -t arg"
    on Windows (1.3.5) which is described in this thread

    Of course, this is not valid the other way around, i.e. some active checks
    can not be done remote (like logfile watching).

    In order to avoid overloading our server, we need to do as much as local
    checks as possible.

    Regards,

    Norbert.
  • Alexei
    Founder, CEO
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2004
    • 5654

    #2
    1.3.5 had serious issues with processing of active and not only active checks. It is already fixed. Please wait for 1.3.6.
    Alexei Vladishev
    Creator of Zabbix, Product manager
    New York | Tokyo | Riga
    My Twitter

    Comment

    • NOB
      Senior Member
      Zabbix Certified Specialist
      • Mar 2007
      • 469

      #3
      Oh, I see.

      The problem was the hostname.
      The Windows agent installer sets the hostname to, say, "server".
      But in the DB on the server it's name is "server.xxx.org".
      Once fixed in the agent config, the value for vfs.fs.size[e:,free]
      send the correct value (about 7GB) for the correct server !

      On the other hand, the 'eventlog[application]' active check on the
      same server now shows (in the Web-Interface) exactly the same value as
      the last entry for the free size of drive "e:" i.e. about 7 GB.

      If this is corrected in the next beta, too, fine.

      BTW: There is a bug in frontends/php/history.php on line 404:
      Index "priority" undefined (or so).
      I changed "priority" to "severity" but am not sure whether this is OK.

      Regards,

      Norbert.
      Last edited by NOB; 25-04-2007, 10:22.

      Comment

      Working...