Zabbix agent on proxy refuses connection on Port 10050

[-bk-]

We have a multi-site setup with a central Zabbix server and proxies on our remote sites. Our main problem now is, that the agent on the proxies refuses the connection. Strangely enough, telnet localhost 10050 works. Logfiles give this error:

980:20100928:153744.313 Item [zabbixproxyhostname:agent.ping] error: Get value from agent failed: *** Cannot connect to [localhost]:10050 [Connection refused]

I have been searching the internet for 3 hours now and can't find any solution. I have double-checked the zabbix_agentd.conf and the zabbix_proxy.conf, but can't find any error (hostnames, bound IP addresses etc, tried several combinations). Connection from proxy to server works over a ssh tunnel.

I have defined the service names in /etc/services (but this shouldn't do any matter...).

There is no firewall, no iptables config or anything...

We are using Ubuntu server 10.04.1 x64 with actual patchlevel, zabbix 1.8.1 installed via apt and then compiled 1.8.3 binaries.

Anyone up with any idea?

[James Wells]

Greetings,

We have a multi-site setup with a central Zabbix server and proxies on our remote sites. Our main problem now is, that the agent on the proxies refuses the connection. Strangely enough, telnet localhost 10050 works. Logfiles give this error:

980:20100928:153744.313 Item [zabbixproxyhostname:agent.ping] error: Get value from agent failed: *** Cannot connect to [localhost]:10050 [Connection refused]

Right off the bat, it sounds like you have only a single entry on the Server= line in your agent configuration file.

For multi-site setups like you are describing, I tend to use 4 entries on the Server= line: The master server, the proxy server, localhost, and usually my puppet / cfengine server all comma separated.

Please note that the order is important if you are using active checks as the Agent will only query the first host listed on the Server= line. But the agent will accept queries from any server listed on that line.

[-bk-]

I found the problem, as I used pre-compiled binaries from another machine... Instead of giving me a proper error message, they didn't work properly... Poor error handling!

I also noticed that static linking of libraries (-enable-static when doing ./configure) still doesn't work. Still gives me errors that curl libraries are found in the correct version, but not usable. Should have been fixed in 1.3.6, but still isn't.

Thanks for the quick response though.

This thread can be closed!