Ad Widget

Collapse

Nothing from Agent 2.0.6 to Server 1.8.11

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • 3of0
    Junior Member
    • May 2012
    • 9

    #1

    Nothing from Agent 2.0.6 to Server 1.8.11

    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.
    Last edited by 3of0; 03-05-2013, 22:52.
  • stucki
    Junior Member
    • Mar 2006
    • 15

    #2
    RTM!

    just as always..read the manual.
    pre 2.0 server can not talk to a new agent.
    Last edited by tchjts1; 05-05-2013, 07:58.

    Comment

    • 3of0
      Junior Member
      • May 2012
      • 9

      #3
      Please forgive my ignorance. I have looked for 4 days before posting and I hadn't found anything difinitive. could you point me to where it says this? I've found these pages (one of which IS TFM) that doesn't exactly say for me.

      https://www.zabbix.com/forum/showthread.php?t=26346 - One person said they got it working.
      https://www.zabbix.com/documentation.../compatibility - I see information about Servers and Proxies, but nothing as far as Agents go. I didn't think Agents are Distributed Monitoring nodes, so I didn't think that applied.

      Comment

      • 3of0
        Junior Member
        • May 2012
        • 9

        #4
        https://www.zabbix.com/forum/showthread.php?t=26335 - This is the closest I could find that even addresses the issue, and shows that they are compatable.

        Maybe I'm reading the wrong manual? Please point me in the right direction.

        Comment

        • Heilig
          Senior Member
          Zabbix Certified Trainer
          Zabbix Certified SpecialistZabbix Certified Professional
          • Mar 2013
          • 366

          #5
          You're right, there is no information in the documentation about the compatibility of the old version of Zabbix server with the new version of the agent (for example, it is not clear, Zabbix Server 1.8 is fully compatible with the agent 2.0.6 or not). Personally, I doubt that they are fully compatible.

          If go back to your question. Did you check availability of port between Zabbix server and agent? Please, execute on zabbix server:
          telnet agent_IP 10050

          Comment

          • 3of0
            Junior Member
            • May 2012
            • 9

            #6
            It works! It was the firewall, thank you for the suggestion of trying to telnet from the server to the agent. It threw me for a huge loop with the error of "telnet: Unable to connect to remote host: No route to host", but digging enough lead me to the solution of adding a firewall rule to the agent computer. Below are the steps I did to get the agent to respond to the host trying to telnet to port 10050.

            Code:
            service iptables stop
            cp /etc/sysconfig/iptables /etc/sysconfig/iptables.original #Incase I oops
            vi /etc/sysconfig/iptables
                #Inserted the following line next to the rule opening port 22, saved and quit.
                -A INPUT -m state --state NEW -m tcp -p tcp --dport 10050 -j ACCEPT
            service iptables start
            /etc/init.d/zabbix-agent restart
            Information started showing up on the server instantly. 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.

            Thanks again, I appreciate it!
            Last edited by 3of0; 09-05-2013, 23:34. Reason: spelling derp

            Comment

            Working...