Re: port busy after server die.

At 07:08 PM 02/12/2004, Gustavo Guillermo wrote:
>Hello everyone, I have a nice question, I ran a WebServer,

What WebServer?

>and after 8
>days hangs and die, but TCP port wasn't released.

How do you know it wasn't released?

>I know that the solution is restart the system, but I see it in other
>times and this server can't be restarted.

Oh, an NT server maybe? Rebooting Windows is the way, but not if you are
talking about some flavour of UNIX. This is a Linux admin list BTW.

>There is some C function or command or anything that can release this
>port?

Stop the server that is keeping the port open. What port is it? What is
running on it?


-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: port busy after server die.

Gustavo Guillermo wrote:

> Hello everyone, I have a nice question, I ran a WebServer, and after 8
> days hangs and die, but TCP port wasn't released.
> I know that the solution is restart the system, but I see it in other
> times and this server can't be restarted.
>
> There is some C function or command or anything that can release this
> port?

First, check the status of the port with "netstat -at".

If there are any entries for the port in the LISTEN or ESTABLISHED
states, the port is still in use. You dan determine which processes
are associated with the socket using e.g. "fuser -vn tcp 80" (as
root).

OTOH, if there are connections in the TIME_WAIT state, you just have
to wait for them to time out.

--
Glynn Clements
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

port busy after server die.

Hello everyone, I have a nice question, I ran a WebServer, and after 8
days hangs and die, but TCP port wasn't released.
I know that the solution is restart the system, but I see it in other
times and this server can't be restarted.

There is some C function or command or anything that can release this
port?


Thanks in advance.
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: port busy after server die.

Thanks, The webserver is a Java one from something called gadmin,=20
application running on kaffe on uClib Linux environment, Of course I kn=
ow=20
the main solution is to find out what makes the server die, with this=20
commands, next time to this happens I will investigate, but I'm really=20
shure, kaffe was not running, an after 2 days I decide to restart my=20
Linux box, because I can't find out a solution, I'm a newbee about Linu=
x=20
Network Development.


Thanks. What is windows NT?

>>>>>>>>>>>>>>>>>> Mensaje original <<<<<<<<<<<<<<<<<<

El 13/02/04, 4:25:55, Glynn Clements escrib=
ió
sobre el tema Re: port busy after server die.:


> Gustavo Guillermo wrote:

> > Hello everyone, I have a nice question, I ran a WebServer, and afte=
r 8
> > days hangs and die, but TCP port wasn't released.
> > I know that the solution is restart the system, but I see it in oth=
er
> > times and this server can't be restarted.
> >
> > There is some C function or command or anything that can release th=
is
> > port?

> First, check the status of the port with "netstat -at".

> If there are any entries for the port in the LISTEN or ESTABLISHED
> states, the port is still in use. You dan determine which processes
> are associated with the socket using e.g. "fuser -vn tcp 80" (as
> root).

> OTOH, if there are connections in the TIME_WAIT state, you just have
> to wait for them to time out.

> --
> Glynn Clements
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html