Date: Thu, 11 Feb 1999 09:50:01 -0800 (PST) From: David Hedley <david@inty.co.uk> To: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/10028: TCP problem binding port - address already in use Message-ID: <199902111750.JAA44203@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/10028; it has been noted by GNATS. From: David Hedley <david@inty.co.uk> To: Bill Fenner <fenner@parc.xerox.com> Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/10028: TCP problem binding port - address already in use Date: Thu, 11 Feb 1999 17:49:30 +0000 (GMT) On Thu, 11 Feb 1999, Bill Fenner wrote: > In message <199902111529.HAA01792@hub.freebsd.org>you write: > >Often when the program exits (usually on a signal), the kernel does not > >'unbind' the port (i.e. netstat -na shows the port still in LISTEN state). > > Have you tried using "lsof" from /usr/ports/sysutils/lsof to figure out > what process is associated with the LISTEN socket? Could this server have > spawned a child which still has the socket open? > On further investigation it looks more like some interaction with 'routed'. It seems that when the problem happens, there are connections to port 8080 held in 'CLOSE_WAIT', and this is causing the kernel to not unbind the port. However, if I kill 'routed' (which is running), then the CLOSE_WAIT connections disappear and the port is no longer bound to anything. This is particularly strange in that the routing table is identical before and after 'routed' is killed. David -- Dr David Hedley,Inty Development,Bristol,UK,0117 9050500,http://www.inty.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902111750.JAA44203>