Error?? inetd[38476]: 19000/udp: bind: Address already in use
-
Logs are getting spammed with this - what is causing it?
Sep 3 06:45:56 inetd[38476]: 19000/tcp: bind: Address already in use
Sep 3 06:45:56 inetd[38476]: 19000/udp: bind: Address already in use
Sep 3 06:45:56 inetd[38476]: 19000/udp: bind: Address already in use
Sep 3 06:45:56 inetd[38476]: 19001/tcp: bind: Address already in use
Sep 3 06:45:56 inetd[38476]: 19001/tcp: bind: Address already in use
Sep 3 06:45:56 inetd[38476]: 19002/udp: bind: Address already in use
Sep 3 06:45:56 inetd[38476]: 19002/udp: bind: Address already in use
Sep 3 06:35:56 inetd[38476]: 19000/tcp: bind: Address already in use
Sep 3 06:35:56 inetd[38476]: 19000/tcp: bind: Address already in use
Sep 3 06:35:56 inetd[38476]: 19000/udp: bind: Address already in use
Sep 3 06:35:56 inetd[38476]: 19000/udp: bind: Address already in use
Sep 3 06:35:56 inetd[38476]: 19001/tcp: bind: Address already in use
Sep 3 06:35:56 inetd[38476]: 19001/tcp: bind: Address already in use
Sep 3 06:35:56 inetd[38476]: 19002/udp: bind: Address already in use
Sep 3 06:35:56 inetd[38476]: 19002/udp: bind: Address already in use -
It means what it says, something else (perhaps another inetd process?) is already bound to those ports.
Check the output of "sockstat" to see who/what has those ports bound.
-
I do not seem to be getting them once I checked this box under advanced firewall/nat
Disables the automatic creation of additional NAT redirect rules for access to port forwards on your external IP addresses from within your internal networks. Note: Reflection for port forward entries is skipped for ranges larger than 500 ports.
I have no need for nat reflection, and this seems to have fixed the error. Why? is the question - shouldn't automatic redirect rules use ports that are not in use?
-
It normally does, but that may also depend on what other services you are running on the box or what else may be on those ports. I don't think it checks if a port is in use, it just grabs a range that is typically not used.
-
well I just did a sockstat and don't see anything listening on those ports.. Let me turn it back on and see if the errors come back and then I will check with sockstat.
