Interrupted system call from Proxy to Server

[markl]

Hi All,

I have an issue where my proxy (new) (on Solaris 10 SPARC) won't communicate with the Zabbix server (Ubuntu 9.0.4 Server). I'm getting the following message in the proxy log:

Unable connect to the server [x.x.x.x]:10051 [Cannot connect to [x.x.x.x:10051] [Interrupted system call]]

The server with the proxy on it works fine when using an agent talking directly to the zabbix server, but the server is remote so I wanted to use a proxy so I could still store data when the comms link is broken between proxy and server.

I've searched through the forums and found mentions of timeouts etc so I've upp'ed the timeout values on both the proxy config and the server config, but with no joy. Does anyone have any ideas?

Many thanks,

Mark.

[richlv]

did active agent work for you ?
note that for proxy you must have port 10051 accessible on zabbix server from the proxy machine and a proxy created in the frontend with a maching name as set in proxy config file.
btw, active agent also caches values if server is unavailable - maybe that's enough in your situation.

[markl]

Thanks for the reply but I'm still having trouble.

If I put an agent on the same server as the proxy, it communicates fine between agent and zabbix server. If I replace the agent with the proxy then I get the Interrupted system call. As far as I was aware, the agent and the proxy go through the same ports on the Zabbix Server (please correct if I'm wrong with this). Any help would be greatly appreciated.

ps. We have both 10050 and 10051 open at both ends through the firewall.

Many thanks,

Mark.

[markl]

Ah ha! I think we've discovered the issue (just waiting to test it out). Basically, its to do with our firewall (which I have no control over). I'm assuming the agent is working as it can also initiate connection from the server to the agent. However, the reverse won't work going from the proxy to the server. Hopefully when we change our firewall to take incoming connections and route them correctly, then all will work fine.. fingers crossed.

I'll update when I know more.

Cheers,

Mark.

[simonc]

Ah ha! I think we've discovered the issue (just waiting to test it out). Basically, its to do with our firewall (which I have no control over). I'm assuming the agent is working as it can also initiate connection from the server to the agent. However, the reverse won't work going from the proxy to the server. Hopefully when we change our firewall to take incoming connections and route them correctly, then all will work fine.. fingers crossed.

I'll update when I know more.

Cheers,

Mark.

Is that your problem is solved?

Thanks