Re: release a Hung TCP port without machine boot
- From: Rick Jones <rick.jones2@xxxxxx>
- Date: Mon, 26 Jun 2006 17:35:59 GMT
ap <pereira.albert@xxxxxxxxx> wrote:
You need to use the tool called lsof, downloadable from the internet.
and use it to find out the process which has locked on to the port
# lsof -tcp <port number>
then using the ps -ef trace out the application/program who is using
hte port and then proceed further..
If his "hung" port is a case where he cannot restart a server
application, there may not still be a process to kill - it may be that
there are still connections in TIME_WAIT. In that case, it is
important to make sure the server application is properly written to
set SO_REUSEADDR before trying to bind() to its well-known port
number.
Hence the reason I was asking the OP just why he thought he had a
"hung port." Hopefully the OP will respond soon.
rick jones
--
No need to believe in either side, or any side. There is no cause.
There's only yourself. The belief is in your own precision. - Jobert
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...
.
- Follow-Ups:
- Re: release a Hung TCP port without machine boot
- From: Ulrich Windl
- Re: release a Hung TCP port without machine boot
- References:
- release a Hung TCP port without machine boot
- From: Bujji
- Re: release a Hung TCP port without machine boot
- From: Rick Jones
- Re: release a Hung TCP port without machine boot
- From: ap
- release a Hung TCP port without machine boot
- Prev by Date: Re: Newbie question - please
- Next by Date: Re: HP-UX11i Password Authentication
- Previous by thread: Re: release a Hung TCP port without machine boot
- Next by thread: Re: release a Hung TCP port without machine boot
- Index(es):
Relevant Pages
|
|
