Announcement

Collapse
No announcement yet.

No access on port 10051

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

    No access on port 10051

    Hi,



    I just launched zabbix from the pre-configured iso..

    My test environment is : my laptop (172.16.2.69), zabix server (172.16.2.103), test server (172.16.2.1).

    I'm running into this issue :


    I'm unable to telnet the zabbix server on 172.16.2.103 10051 from my laptop.

    However, on the server console, a telnet 172.16.2.103 10051 work's. Meaning the service is listening also on the eth0 interface.


    Someone got an idea on this ?

    I guess since this isn't working, communication between agent and server is also impossible.

    #2
    Is there a firewall running on your laptop or in your network that might be blocking it?

    Comment


      #3
      no there's not. neither on my laptop or on the test server

      telnet from the test server to the zabbix server doesn't work either

      that's seems to indicate that there's something on the zabbix server which is blocking, but i made nothing special..it's just the default configuration

      by the way, telnet to zabbix server on port 80 work's..

      i don't get it
      Last edited by alvoryx; 04-08-2011, 20:59.

      Comment


        #4
        ok found it :


        By default, only two ports are open - 22 (SSH) and 80 (HTTP). To open additional ports - for example, Zabbix server and agent ports - modify iptables rules with SuSEfirewall2 utility:

        SuSEfirewall2 open EXT TCP zabbix-trapper zabbix-agent

        Then reload the firewall rules:

        SuSEfirewall2 stop
        SuSEfirewall2 start



        that was it..

        but why aren't they open by default ? doesn't the agent need it to work ?

        Comment

        Working...
        X