From: Gustavo Guillermo <gustavo@compunauta.com>
To: linux-admin@vger.kernel.org
Subject: Re: port busy after server die.
Date: Sat, 14 Feb 2004 02:35:20 GMT [thread overview]
Message-ID: <20040214.2352000.1856133159@linux.local> (raw)
In-Reply-To: <16427.64883.554931.941250@cerise.nosuchdomain.co.uk>
Thanks, The webserver is a Java one from something called gadmin,
application running on kaffe on uClib Linux environment, Of course I know
the main solution is to find out what makes the server die, with this
commands, next time to this happens I will investigate, but I'm really
shure, kaffe was not running, an after 2 days I decide to restart my
Linux box, because I can't find out a solution, I'm a newbee about Linux
Network Development.
Thanks. What is windows NT?
>>>>>>>>>>>>>>>>>> Mensaje original <<<<<<<<<<<<<<<<<<
El 13/02/04, 4:25:55, Glynn Clements <glynn.clements@virgin.net> escribió
sobre el tema 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 <glynn.clements@virgin.net>
-
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
prev parent reply other threads:[~2004-02-14 2:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 3:08 port busy after server die Gustavo Guillermo
2004-02-12 20:27 ` Scott Taylor
2004-02-12 22:25 ` Glynn Clements
2004-02-14 2:35 ` Gustavo Guillermo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040214.2352000.1856133159@linux.local \
--to=gustavo@compunauta.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).