From: Grzegorz Bakalarski (G.Bakalarski@icm.edu.pl)
Date: Sat Sep 20 2003 - 05:51:23 EDT
Dear ALL.
I have urgent query (google'ing gave nothing).
Normaly I run an application which listen on port 22222.
But now I cam't start it because the port is "occupied"
by ... (I don't know by what)
netstat shows:
zatoka.49377 zatoka.22222 49152 0 49152 0 CLOSE_WAIT
netstat -v shows:
zatoka.49377
zatoka.22222 49152 00000000 00000000 49152 00000000 00000000 435 8192 CLOSE_WAIT
lsof|grep 22222 or lsof|grep 49377 gives nothing.
This close_wait seems to last at list for 10 hours (first problems were
reported 2am, now it is 12:00 here).
Is there any way to check who (which process, or service or ...what)
keeps the port in such state so long ?
Or the only possibility is to reboot (production!) server ???
Any help needed!
Thanks in advance!
GB
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:27:09 EDT