Ad Widget

Collapse

Connection Reset By Peer: Server v1.1.6 - Client v1.4

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • CuSo4
    Junior Member
    • Jun 2007
    • 4

    #1

    Connection Reset By Peer: Server v1.1.6 - Client v1.4

    Hello, I have a Zabbix server (version 1.1.6) running, and 7 Zabbix clients (version 1.1.6). When I try to add a new client (version 1.4), I get a "Connection reset by peer"-error.

    The server log says:

    ... Timeout while receiving data from [Hostname]
    ... Connection reset by peer.
    ... Host [Hostname] will be checked after 60 seconds

    I've tried both in active and passive mode.

    The client log in active mode says:

    ... zabbix_agentd started. ZABBIX 1.4.
    ... zabbix_agentd collector started
    ... zabbix_agentd active check started [serverhostname:10051]

    The client log in passive mode says:

    ... zabbix_agentd started. ZABBIX 1.4.
    ... zabbix_agentd collector started

    When I telnet from the server to the client I get:
    # telnet clienthostname 10050
    Trying x.x.x.x...
    Connected to clienthostname
    Escape character is '^]' .

    but there isn't any reaction after that. (I tried typing "version[zabbix_agentd]")


    When I telnet from the server to the client I get:
    # telnet serverhostname 10051
    Trying x.x.x.y...
    Connected to serverhostname
    Escape character is '^]'.
    QUIT
    Connection closed by foreign host.

    I have added the client & server configuration files as attachment.

    Does anyone has any suggestions about how to solve this problem?
    Thanks in advance!
    Attached Files
  • StanZoid
    Member
    • Oct 2005
    • 47

    #2
    I have seen this same problem in my environment, and it has been caused every time by the agent machine not having a route back to the zabbix server. Add a route and fix the problem!

    Stanzoid

    Comment

    • CuSo4
      Junior Member
      • Jun 2007
      • 4

      #3
      Thanks for your reply!
      However, I checked the routes, and everything seems to be fine.
      I have another client on the same vlan that works correcty.
      Furthermore, I can ping and ssh from server to client, which should also rule out a routing configuration error...

      Comment

      Working...