I have an existing server with 1.8.11 that I have used various 1.8.x agents with successfully. I have a new OEL 6.4 box that I'm using repository mentioned on zabbix's download section. I've installed the agent, setup the config file, and followed the logs as far as i can until they stopped reporting anything.
I have my 1.8.11 server on Debian Wheezy pointing to the 2.0.6 agent on OEL 6.4, and the agent pointing to the server. There are no complaints in the logs saying that they cannot see each other and no data in the server. Infact, the logs don't show any conversations with each other at all.. The DebugLevel is 3 on both the server and agent. The only information I can get is the web interface showing that the Agent is unavailable, and the latest data showing that the Host status is unreachable since the day I installed the agent.
The exact error the web interface gives is: Get value from agent failed: *** Cannot connect to [[servername]:10050: [113] No route to host
Both agent and server can ping each other by name and IP. I've even specified them to talk to each other via IP's.
I'm lost with what to try next.
I have my 1.8.11 server on Debian Wheezy pointing to the 2.0.6 agent on OEL 6.4, and the agent pointing to the server. There are no complaints in the logs saying that they cannot see each other and no data in the server. Infact, the logs don't show any conversations with each other at all.. The DebugLevel is 3 on both the server and agent. The only information I can get is the web interface showing that the Agent is unavailable, and the latest data showing that the Host status is unreachable since the day I installed the agent.
The exact error the web interface gives is: Get value from agent failed: *** Cannot connect to [[servername]:10050: [113] No route to host
Both agent and server can ping each other by name and IP. I've even specified them to talk to each other via IP's.
I'm lost with what to try next.
I didn't believe a firewall would be the issue. And I never knew that a firewall could generate such a telnet error on a remote host. 
Comment