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.
What does "Could not bind socket. Address and port are already in use." mean?
Votes:
0
Best Answer
Accepted Answer
Votes:
0
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
Last change on Aug 23, 2013 1:48:07 PM by
7 Replies
Votes:
0
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
Votes:
0
You could try pausing and resuming the Netflow sensor.
Created on Jun 7, 2011 9:53:01 AM by
Accepted Answer
Votes:
0
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
Last change on Aug 23, 2013 1:48:07 PM by
Votes:
0
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
Last change on Nov 2, 2015 12:48:07 PM by
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.
Add comment