Ad Widget

Collapse

Get value from agent failed: ZBX_TCP_READ() failed [Connection reset by peer]

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dimes
    Junior Member
    • Jul 2011
    • 3

    #1

    Get value from agent failed: ZBX_TCP_READ() failed [Connection reset by peer]

    Hi,

    I've this problem Get value from agent failed: ZBX_TCP_READ() failed [Connection reset by peer] and dont know how to fix it. Can anyone show me how to do it step by step ? I forgot to say that i get this message where the availibility is and Z is red.
  • Davidus
    Senior Member
    • Dec 2010
    • 281

    #2
    Well, first of all you have to make Z green
    Probably you have to configure your agent
    http://www.zabbix.com/documentation/...bix_agentd_win

    Comment

    • hirschnf
      Member
      • Jan 2010
      • 56

      #3
      Hello,

      I have the same problem too.
      I monitor the agent over a zabbix_proxy. All works fine till this morning.
      I have restarted the agent and I have also restarted the proxy but it seems that the agent could not connect.

      Get value from agent failed: ZBX_TCP_READ() failed [Connection reset by peer]
      And the "Z" is still red.

      Agent-Log:
      Code:
      10076:20110714:112755.719 No active checks on server: host [pc1244.clients.x.local] not found
      10076:20110714:112955.716 No active checks on server: host [pc1244.clients.x.local] not found
      10076:20110714:113155.714 No active checks on server: host [pc1244.clients.x.local] not found
      10076:20110714:113355.712 No active checks on server: host [pc1244.clients.x.local] not found
       6616:20110714:113712.864 call to PdhCollectQueryData() failed: 3. MSG 0x00000102 - Unable to find message text [3. MSG 0x0000013D - Unable to find message text [0x57]]
      After this message the "Z" goes to green. But it takes several hours till this moment.

      Proxy-Log:
      Code:
      16998:20110714:103546.697 Zabbix Proxy stopped. Zabbix 1.8.5 (revision 19050).
       22813:20110714:103548.863 Starting Zabbix Proxy. Zabbix 1.8.5 (revision 19050).
       22813:20110714:103548.863 **** Enabled features ****
       22813:20110714:103548.863 SNMP monitoring:       YES
       22813:20110714:103548.863 IPMI monitoring:       YES
       22813:20110714:103548.864 ODBC:                   NO
       22813:20110714:103548.864 SSH2 support:          YES
       22813:20110714:103548.864 IPv6 support:           NO
       22813:20110714:103548.864 **************************
      ...
      
       22827:20110714:113355.714 Sending list of active checks to [192.168.42.23] failed: host [pc1244.clients.x.local] not found
       22829:20110714:113549.763 Executing housekeeper
       22829:20110714:113549.777 Deleted 139 records from history [0.003261 seconds]
        22819:20110714:113551.741 Enabling Zabbix host [pc1244.clients.x.local]
       22818:20110714:113558.745 Item [pc1244.clients.x.local:system[procrunning]] is not supported
       22821:20110714:113604.755 Item [pc1244.clients.x.local:vfs.fs.size[d:,free]] is not supported
       22821:20110714:113615.789 Zabbix Host [pc1244.clients.x.local]: first network error, wait for 15 seconds
       22818:20110714:113616.772 Zabbix Host [pc1244.clients.x.local]: another network error, wait for 15 seconds
       22820:20110714:113617.773 Zabbix Host [pc1244.clients.x.local]: another network error, wait for 15 seconds
       22819:20110714:113618.776 Zabbix Host [pc1244.clients.x.local]: another network error, wait for 15 seconds
       22822:20110714:113636.756 Zabbix Host [pc1244.clients.x.local]: another network error, wait for 15 seconds
       22822:20110714:113654.763 Zabbix Host [pc1244.clients.x.local]: another network error, wait for 15 seconds
       22822:20110714:113712.770 Disabling Zabbix host [pc1244.clients.x.local]
       22822:20110714:113812.787 Enabling Zabbix host [pc1244.clients.x.local]
       22819:20110714:113813.101 Item [pc1244.clients.x.local:perf_counter[\PhysicalDisk(_Total)\Avg. Disk Write Queue Length]] is not supported
       22817:20110714:113814.093 Item [pc1244.clients.x.local:perf_counter[\System\File Read Bytes/sec]] is not supported
       22820:20110714:113815.098 Item [pc1244.clients.x.local:perf_counter[\System\File Write Bytes/sec]] is not supported
       22819:20110714:113842.138 Item [pc1244.clients.x.local:perf_counter[\PhysicalDisk(_Total)\Avg. Disk Read Queue Length]] is not supported
       22820:20110714:113848.153 Item [pc1244.clients.x.local:proc_cnt[httpd]] is not supported
      So why it takes so long till the agent can be connect from the proxy system?
      And is it normal, when a host is monitored by a proxy, sometimes I see in the hosts list "proxyserver:hostname" and sometimes I only see "hostname"?

      best regards
      Frank

      Comment

      • hirschnf
        Member
        • Jan 2010
        • 56

        #4
        zabbix proxy solution

        Hello,

        for your information. I think I have found the solution for my problem. I have used a discovery rule on the zabbix server which included the monitored hosts which are monitored through a proxy system.

        After I have excluded this systems from the discovery rule it works fine.

        Comment

        Working...