Ad Widget

Collapse

Perf_count works only in Passive Agent

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • norbertorozas
    Junior Member
    • Apr 2014
    • 12

    #1

    Perf_count works only in Passive Agent

    After many researches I could not find an answer... Any help?

    I'm running Zabbix 2.2 to monitor some Windows Servers 2008 R2.

    On Windows I'm using zabbix agent with this set:

    PerfCounter = app_threads_counter,"\.NET CLR LocksAndThreads(Syspro.Driver.APP)\# of current logical Threads",60


    When using Zabbix Agent in normal condition it works fine:




    However, since host will be installed inside sub-network, we decided to use Active mode. All other Items work fine in Active mode, excepted for this PerfCounter. When I just change mode, zabbix does not receive PerfCounter info:



    ... and, as I restart Windows agentd:

    2500:20141020:114920.595 Starting Zabbix Agent [APP3]. Zabbix 2.2.1 (revision 40801).
    2500:20141020:114920.595 using configuration file: C:\zabbix_agentd.conf
    34812:20141020:114920.798 agent #0 started [collector]
    31220:20141020:114920.798 agent #1 started[listener #1]
    17804:20141020:114920.798 agent #3 started[listener #3]
    7572:20141020:114920.798 agent #2 started[listener #2]
    20952:20141020:114920.798 agent #4 started [active checks #1]
    20952:20141020:114924.433 active check configuration update from [1XX.1X3.10X.18:10051] started to fail (ZBX_TCP_READ() failed: [0x0000274C] Uma tentativa de conexão falhou porque o componente conectado não respondeu

    corretamente após um período de tempo ou a conexão estabelecida falhou

    porque o host conectado não respondeu.)


    ******************

    I've also tried to use

    perf_counter[\.NET CLR LocksAndThreads(Syspro.Driver.APP)\# of current logical Threads]

    set directly as an Item but the result is the same:
    - Works fine in normal operation (passive)
    - Doesn't work in Active mode


    Why?
    Attached Files
  • tchjts1
    Senior Member
    • May 2008
    • 1605

    #2
    "A connection attempt failed because the connected party did not respond
    correctly after a period of time, or established connection failed
    because connected host failed to respond.)"

    You may be hitting a timeout there. Have a look at 2 things:

    On your Zabbix server in zabbix_server.conf there is a field for Timeout=, if that is still at the default of 3, try incrementing it to 15 and restart your Zabbix server process.

    On your monitored host in zabbix_agentd.conf there is an identical field of Timeout=, increment that as well and restart your agent service.

    See if that helps.

    Comment

    • norbertorozas
      Junior Member
      • Apr 2014
      • 12

      #3
      Thanks!
      Using Timeout = 15 (on both zabbix_server and zabbix_agentd), restarting both.

      It seems the message 20952:20141020:114924.433 active check configuration update from [1XX.1X3.10X.18:10051] started to fail (ZBX_TCP_READ() failed: [0x0000274C]. A connection attempt failed because the connected party did not respond refers not to connection but to something while exchanging protocol (is that?)

      When using Active Mode to many other Items it works great! When using Passive Mode on perf_counter it works too!

      The problem only occurs when using perf_counter in Active mode....

      Comment

      • tchjts1
        Senior Member
        • May 2008
        • 1605

        #4
        Is there a Zabbix proxy in this mix?

        Comment

        • norbertorozas
          Junior Member
          • Apr 2014
          • 12

          #5
          No, connection is direct from Windows - zabbix_agentd --> TO --> zabbix_server on FreeBSD.

          Comment

          Working...