New Question
 
 
PRTG Network Monitor

Intuitive to Use.
Easy to manage.

200.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free PRTG
Download >>

 

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

 

Top Tags


View all Tags


What does "Could not bind socket. Address and port are already in use." mean?

Votes:

0

Your Vote:

Up

Down

After upgrading to the latest version I am getting this error on three sensors. One is an Amazon CloudWatch sensor, one is an HTTP sensor and the other is an FTP sensor. All are on the same server. Restarting the probe sometimes will bring one of them back, but then the others throw the error. The sensors were fine before the upgrade.

cloudwatch ftp sockets

Created on Mar 16, 2011 4:32:56 PM by  Laurie Collins (100) 1 1



Best Answer

Accepted Answer

Votes:

0

Your Vote:

Up

Down

If this message is shown by PRTG sensors, this means that the PRTG Probe is not able to open any outgoing TCP ports for outgoing monitoring requests.

There are two possible reasons for the message "Could not bind socket. Address and port are already in use":

  • In the probe settings you have selected an outgoing IP (and with that a network interface) that can not reach the desired target system. The IP stack on the probe system tries to open an outgoing port but the selected network interface can't provide it.
  • Sometimes overloading situations (which can be caused by PRTG, or other programs, or other problems) can cause the IP stack of the probe system to run out of outgoing port numbers. This can sometimes be cured by rebooting the probe system.

Created on Sep 12, 2011 5:35:51 PM by  Dirk Paessler [Founder Paessler AG] (10,859) 3 4

Last change on Aug 23, 2013 1:48:07 PM by  Gerald Schoch [Paessler Support]



7 Replies

Votes:

0

Your Vote:

Up

Down

Dear Laurie,

"Could not bind socket. Address and port are already in use" usually appears if PRTG can't find any free ports between 1024-5000. This can happen if there are too many sensors that base on TCP are opening ports to quickly (i.e. too short scanning intervals).

Best Regards.

Created on Mar 16, 2011 5:36:56 PM by  Torsten Lindner [Paessler Support]



Votes:

0

Your Vote:

Up

Down

I get this message after editing netflow sensors.

"Could not bind socket. Address and port are already in use."

how can i recover from this error? ( other then restart service\server)

Meir

Created on Jun 1, 2011 8:56:29 PM by  meirely (0) 1



Votes:

0

Your Vote:

Up

Down

You could try pausing and resuming the Netflow sensor.

Created on Jun 7, 2011 9:53:01 AM by  Torsten Lindner [Paessler Support]



Accepted Answer

Votes:

0

Your Vote:

Up

Down

If this message is shown by PRTG sensors, this means that the PRTG Probe is not able to open any outgoing TCP ports for outgoing monitoring requests.

There are two possible reasons for the message "Could not bind socket. Address and port are already in use":

  • In the probe settings you have selected an outgoing IP (and with that a network interface) that can not reach the desired target system. The IP stack on the probe system tries to open an outgoing port but the selected network interface can't provide it.
  • Sometimes overloading situations (which can be caused by PRTG, or other programs, or other problems) can cause the IP stack of the probe system to run out of outgoing port numbers. This can sometimes be cured by rebooting the probe system.

Created on Sep 12, 2011 5:35:51 PM by  Dirk Paessler [Founder Paessler AG] (10,859) 3 4

Last change on Aug 23, 2013 1:48:07 PM by  Gerald Schoch [Paessler Support]



Votes:

0

Your Vote:

Up

Down

In the NF9/IPFX Packets Received column I get - 10.1.1.2: 35 - inactive (ip)

Nothing in Unassigned Flows.

Templates received (ID) has about 25 numbers listed in the 2XX range.

It auto-detected Netflow 9

There is nothing in the decoded flows box

Created on Oct 30, 2015 3:24:58 PM by  Chris Heighway (0)



Votes:

0

Your Vote:

Up

Down

There is IP connectivity between collector and sender. There are only 2 devices pointed to PRTG right now and only 56 sensors used. I don't think the "Best Answer" above applies to this.

Created on Oct 30, 2015 6:00:31 PM by  Chris Heighway (0)



Votes:

0

Your Vote:

Up

Down

Hello Chris,

Have you tried restarting the Probe Service? Also please try setting another port for Netflow on the device sending the data, adapt accordingly in the sensor/or the tester. Does it work then? Can you verify with "netstat -an" that PRTG or the Netflow Tester is listening on the configured port? Make sure to pause the Netflow Sensor when using the Netflow Tester.

Kind regards.

Created on Nov 2, 2015 12:47:43 PM by  Erhard Mikulik [Paessler Support]

Last change on Nov 2, 2015 12:48:07 PM by  Erhard Mikulik [Paessler Support]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.