Ad Widget

Collapse

Cannot bind to port 10050

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mgrundy
    Junior Member
    • Jan 2005
    • 10

    #1

    Cannot bind to port 10050

    I am experiencing some problems getting the zabbix_agentd to start on some machines.

    Currently I am trying to roll out Zabbix across a number of servers running a mixture of Suse Linux 9 & 10 and Suse Enterprise Server 9 & 10.

    On some the agent runs without any problem. On others all I get in the log file is the error
    Cannot bind to port 10050. Error [Cannot assign requested address]. Another zabbix_agentd already running ?

    I have checked with both ps and netstat. There are no zabbix processes running and the port is not in use by anything else. I have also tried using a different port but to no avail.

    Does anyone have any suggestions please?


    Mark
    Last edited by mgrundy; 07-09-2006, 15:14.
  • RandySpinaGE
    Member
    • Jun 2006
    • 57

    #2
    Make sure you have the correct entry for "ListenIP=" (your cards address) in zabbix_agentd.conf

    Comment

    • mgrundy
      Junior Member
      • Jan 2005
      • 10

      #3
      Many thanks.

      Simple when you know the answer!

      Comment

      • Stefaans
        Junior Member
        • Dec 2006
        • 6

        #4
        I made the same stupid mistake: copied zabbix_agentd.conf from another box, and forgot to edit the listening IP

        Comment

        • ashrocks
          Junior Member
          • Oct 2010
          • 6

          #5
          Does the listening IP in agent should be same as the Zabbix server Ip

          I am trying to do the same thing

          Connecting zabbix agent to the server.

          Both on Ubuntu OS.

          It does not bind to that port. There is no firewall problem because both IPs are inside the firewall.

          I see the same errrors in the log file.

          listenIP didnot help

          Anymore suggestions.

          Comment

          • onurzaim
            Junior Member
            • Aug 2013
            • 4

            #6
            I simply left that option unconfigured. It started working.

            Comment

            Working...