Zabbix Monitoring Error

[Ravi Srivastava]

Hello,

We've been using Zabbix server and Zabbix proxy setup for monitoring our servers for years.
Now, we want to get rid of those proxy servers and just use the server to monitor our servers and networks from there.

I added the host on the Zabbix server for monitoring and used TCP (port 10050), configured the agent on the server to use the server ip in the SERVER and ACTIVE SERVER fields.
I'm getting the following error on the Zabbix portal,
Get value from agent failed: cannot connect to [[our ip]:10050]: [4] Interrupted system call

Is there something I'm missing?
Please help!

[Ravi Srivastava]

Thank you all for your input!
It was a silly mistake!

As soon as I added the rule in the windows firewall, the alert fired.
Going to get rid of those proxy servers now.

[fvilarnovo]

Server or ServerActive will depend on the type of items that you are gathering... zabbix agent vs zabbix agent (active). passive items will work under tcp/10050 vs active on tcp/10051. You should check both logs (server and agent) to see if there are errors there, however it seems like a transport issue (networking).

[cyber]

passive items will work under tcp/10050 vs active on tcp/10051.

This is not correct... these ports are on different ends of communication channel...
Agent will always listen on 10050 (default port, if not changed or not specifically configured not to use passive checks). And server/proxy are listening on port 10051 (also, if not changed from default). Item as such does not care about this.... it is the way how agent and server/proxy communicate with each other. Who is instructed to run queries in agent...
In case of passive items, server/proxy polls agent and connects to agent port (10050) and asks for item values. But even then, if ServerActive is defined, your agent will request updates from server/proxy, by connecting to server/proxy port 10051... Might not get any, but it still asks...
In case of active items, agent connects and asks from server/proxy "what I need to monitor" and sends its gathered data back to server/proxy, port 10051... Here server/proxy just provides config and receives data and agent acts on its own...

But I have to agree on the "there is network issue here" .. Local FW? Some routing issues? ports not opened? server:any -> host:10050 and host:any -> server:10051

[Ravi Srivastava]

Thank you all for your input!
It was a silly mistake!

As soon as I added the rule in the windows firewall, the alert fired.
Going to get rid of those proxy servers now.