Ad Widget

Collapse

zabbix-agent 2.2 - no route to host

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • eljibe
    Member
    • Apr 2014
    • 31

    #1

    zabbix-agent 2.2 - no route to host

    Hi all,

    I have successfully installed the zabbix server on a CentOS 6.5 virtual machine (through virtualbox). I added the zabbix repositories, disabled selinux (ok, it wasn't done, but is now)... Things look good and I have a nice web interface telling me everything is fine. So far, so good.
    So now I set up a new virtual machine on which I want to install the agent. I went through the same process, disabled iptables and selinux, added the repositories, specified my first machine in the agent config file as a server (I gave it the ip address).
    But when I try to add an item, things don't seem to work.
    I keep getting the [113] no route to host in the web interface.
    Plus when I try to telnet the agent on port 10050 I get "Connection closed by foreign host." instantaneously.
    Any idea (I suck at networking, so do not hesitate to point me where I can look at if this is a network problem) ?
    Both VMs use bridged network interfaces, and can communicate with the internet.
  • aib
    Senior Member
    • Jan 2014
    • 1615

    #2
    Could you ping second VM from first one and vice verse?

    Could you use telnet connection?
    Code:
    telnet {ip_of_second_vm} 10050
    Sincerely yours,
    Aleksey

    Comment

    • eljibe
      Member
      • Apr 2014
      • 31

      #3
      Yes, ping worked, telnet didn't, for a reason I don't understand.
      But I ended up solving my problem, by editing the agentd configuration file and setting the Server and ServerActive keys, filling them up with the IP address of the zabbix server and settinc the zabbix_can_network to on. I must say I don't know what fixed the issue though.

      Comment

      • aib
        Senior Member
        • Jan 2014
        • 1615

        #4
        Originally posted by eljibe
        settinc the zabbix_can_network to on.
        This setting fixed your problem.
        You just allow zabbix to work through Firewall.

        Adding both settings - Server= and ServerActive= it's not important. Except you are going to mix "Zabbix Agent" and "Zabbix Agent(active)" checks type for this particular host.

        Keyword "Server=" works only for "Zabbix Agent"
        Keyword "ServerActive=" works only for "Zabbix Agent(active)"

        Anyway - you solved your problem without any advice. Good for you!
        Sincerely yours,
        Aleksey

        Comment

        Working...