LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   [crit] (98) Address already in use: make_sock could not bind to port 3339. (https://www.linuxquestions.org/questions/linux-networking-3/%5Bcrit%5D-98-address-already-in-use-make_sock-could-not-bind-to-port-3339-a-17633/)

ForumKid 04-03-2002 06:48 PM

[crit] (98) Address already in use: make_sock could not bind to port 3339.
 
[crit] (98) Address already in use: make_sock could not bind to port 3339. Every once in a while I get this error and i have to reboot my server in order for people to access my web server again. WHen i Get this error I can try to go to my web site, it says www.mysite.com found..waiting for reply, but then never gets a reply. I have to reboot.

What would cause this????

Any ideas??

Mik 04-04-2002 02:04 AM

As root run the following command:

netstat -lnp | grep 3339

That should tell you which process is listening on that port. You can then restart or try to recover that process in someother way. This should save you a reboot.

ForumKid 04-04-2002 07:22 AM

Thanks Mik,
I can just kill the process or restart it to aviod rebooting.

My question is, the process running on that port is httpd. Where does port 3339 come from? Isnt apache smart enough to know if its in use to kill it and restart it or just choose another port?

This problem only happens out of the blue...Not sure if it has something to do with me stopping and restarting the web server while the process has not died yet.

Thanks so much for your time. I really appreciate it.
ForumKid

Mik 04-04-2002 08:56 AM

I don't know what it's using port 3339 for. Are you per chance using that port to serve your webpages or using it for a virtual host?

If there was still an instance of apache running which wasn't closed properly then starting up a new one would generate an error similar to that one.
Only one application can bind to a port and it doesn't have control over other applications. I assume it's a port it's listening on which is usually a fixed number so it won't go picking other numbers. But why it's using 3339 I don't know.

madhu78 06-10-2008 02:38 AM

Its working ..
 
Thank you very much. By using the "netstat -lnp | grep 3339" i was able to identify the conflicting process. Killed it and restart the process freshl again. Everything is working cool now.

Thanks once again.


All times are GMT -5. The time now is 03:02 AM.