After upgrading, my Amazon CloudWatch, HTTP, and FTP sensors on the same server show errors. Restarting the probe sometimes resolves one, but the others fail. They were fine before the upgrade. How can I fix this?
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.
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.
