Ad Widget

Collapse

ZBX_TCP_READ: connection reset by peer

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • shoong
    Junior Member
    • Feb 2016
    • 5

    #1

    ZBX_TCP_READ: connection reset by peer

    Hi Guys,

    Long time lurker and I've usually been able to find my answer based on previous posts. However, I can't figure this one out.
    • CentOS 6.5
    • Zabbix Server 2.4.2


    I added the agent to my local windows box to test before I start adding it to every system we currently have. I have configured the file on the agent:
    • Server: 127.0.0.1
    • ServerActive: 192.168.72.104 (Zabbix Server IP)


    zabbix_agent.log
    2713:20160216:103225.099 Starting Zabbix Agent [utl-zabbix01.dev.priv]. Zabbix 2.4.2 (revision 50419).
    2713:20160216:103225.099 using configuration file: /etc/zabbix/zabbix_agentd.conf
    2713:20160216:103225.100 agent #0 started [main process]
    2715:20160216:103225.106 agent #1 started [collector]
    2717:20160216:103225.108 agent #3 started[listener #2]
    2719:20160216:103225.108 agent #5 started [active checks #1]
    2718:20160216:103225.110 agent #4 started[listener #3]
    2716:20160216:103225.110 agent #2 started[listener #1]
    2719:20160216:103225.111 active check configuration update from [zabbix:10051] started to fail (cannot resolve [zabbix])
    1242:20160218:150217.099 Starting Zabbix Agent [utl-zabbix01.dev.priv]. Zabbix 2.4.2 (revision 50419).
    1242:20160218:150217.104 using configuration file: /etc/zabbix/zabbix_agentd.conf
    1242:20160218:150217.105 agent #0 started [main process]
    1246:20160218:150217.107 agent #1 started [collector]
    1247:20160218:150217.109 agent #2 started[listener #1]
    1249:20160218:150217.112 agent #3 started[listener #2]
    1251:20160218:150217.112 agent #4 started[listener #3]
    1252:20160218:150217.114 agent #5 started [active checks #1]
    1252:20160218:150217.115 active check configuration update from [zabbix:10051] started to fail (cannot resolve [zabbix])

    Under the zabbix web gui
    • Host name: *made it a generic name, does this have to match what my computer name is?*
    • Groups: Discovered Hosts
    • Agent interfaces: IP Address: 192.168.42.179 (this is the IP of my box, I also tried inputting the Zabbix Server IP with no luck)
    • Templates: App_Zabbix_agent and ICMP_Ping


    I have tried resetting my local box. I also reset my box everytime I made a change. Any help will be appreciated. Let me know if you need any other information.
  • glebs.ivanovskis
    Senior Member
    • Jul 2015
    • 237

    #2
    Originally posted by shoong
    1252:20160218:150217.115 active check configuration update from [zabbix:10051] started to fail (cannot resolve [zabbix])
    Check ServerActive setting, I guess you have "zabbix" instead of IP there.

    Agent wants to connect to "zabbix:10051" but fails. This may be a DNS problem, zabbix does not resolve to the IP of your Zabbix server.

    Also host name in the frontend must match Hostname setting in the agent configuration file if you want active checks to work.

    Comment

    • shoong
      Junior Member
      • Feb 2016
      • 5

      #3
      Originally posted by glebs.ivanovskis
      Check ServerActive setting, I guess you have "zabbix" instead of IP there.

      Agent wants to connect to "zabbix:10051" but fails. This may be a DNS problem, zabbix does not resolve to the IP of your Zabbix server.

      Also host name in the frontend must match Hostname setting in the agent configuration file if you want active checks to work.
      Hi Glebs,

      Thanks for your reply. when you say frontend do you mean on the web gui? i changed zabbix to the ip of the host and it now stats host [utl-zabbix01.dev.priv] not found.

      i'm assuming i'll have to plug that name in somewhere?

      Comment

      • shoong
        Junior Member
        • Feb 2016
        • 5

        #4
        Originally posted by glebs.ivanovskis
        Check ServerActive setting, I guess you have "zabbix" instead of IP there.

        Agent wants to connect to "zabbix:10051" but fails. This may be a DNS problem, zabbix does not resolve to the IP of your Zabbix server.

        Also host name in the frontend must match Hostname setting in the agent configuration file if you want active checks to work.
        Do I have to set a hostname or can I leave it commented out on the windows agent conf side and CentOS agent conf side?

        Comment

        • shoong
          Junior Member
          • Feb 2016
          • 5

          #5
          issue resolved. the hostnames parameter on both my window's box agent conf and centos agent conf had to be the same.

          Comment

          Working...