Port 50000 not listening still the system thinks it is in use
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Port 50000 is high up in the ephemeral range so I wouldn't expect it to be used for a client connection unless the ephemeral range had been fiddled with or the host is extremely busy, would you please provide output from the following:
Depending on how fast you try to open a new socket an the same port it might still be seen as occupied by the kernel. Also I doubt that nc is that badly programmed but maybe a nother program used the port before. Not sure but i think the so_lingering socket options goes with this.
Port 50000 is high up in the ephemeral range so I wouldn't expect it to be used for a client connection unless the ephemeral range had been fiddled with or the host is extremely busy, would you please provide output from the following:
Code:
netstat -tunlp
netstat -an
The output of those commands does not contain the port number 50000. I can't comment on the "ephemeral range" part in your feedback.
This ticket has been assigned to me and I have got to resolve it.
Not sure if the following will show more then netstat, but it cannot hurt to try:
Code:
lsof -i :50000
Quote:
Can a system restart resolve the issue?
Maybe, but if something is listening on port 50000 and is started at boot you'll end up with the same situation. Another thing that might be frustrating: If it does work after a reboot, what was "wrong" in the first place....
Does not show anything. I have got approval from the Dev Team for the reboot of the system. It would be bad on my part if that does not resolve the issue because they would put up questions... blah... blah!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.