Date: Thu, 11 Feb 1999 10:13:15 -0800 From: David Greenman <dg@root.com> To: Bill Fenner <fenner@parc.xerox.com> Cc: freebsd-bugs@FreeBSD.ORG Subject: Re: kern/10028: TCP problem binding port - address already in use Message-ID: <199902111813.KAA01018@implode.root.com> In-Reply-To: Your message of "Thu, 11 Feb 1999 09:40:02 PST." <199902111740.JAA22219@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>The following reply was made to PR kern/10028; it has been noted by GNATS. > >From: Bill Fenner <fenner@parc.xerox.com> >To: david@inty.net >Cc: freebsd-gnats-submit@FreeBSD.ORG >Subject: Re: kern/10028: TCP problem binding port - address already in use >Date: Thu, 11 Feb 1999 09:39:01 PST > > 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? He indicated to me in other email that killing routed fixed the problem. Prior to killing routed, fstat showed this: root routed 1999 0 / 7696 crw-rw-rw- null rw root routed 1999 1 / 7696 crw-rw-rw- null rw root routed 1999 2 / 7696 crw-rw-rw- null rw root routed 1999 3* route raw 0 f363fc80 root routed 1999 4* internet stream tcp f3743cc0 root routed 1999 5* internet stream tcp f3743de0 root routed 1999 6* internet stream tcp f3743f00 root routed 1999 7* internet stream tcp f37434e0 root routed 1999 8* pipe f394b980 <-> 0 0 rw root routed 1999 9* internet raw icmp f38c5ea0 root routed 1999 10* internet stream tcp f3742600 root routed 1999 11* internet stream tcp f3742cc0 root routed 1999 12* internet stream tcp f3742060 root routed 1999 13* internet stream tcp root routed 1999 14* internet stream tcp root routed 1999 15* internet dgram udp f36e0ba0 root routed 1999 16* local dgram f3950e00 <-> f3950fc0 ...which looks VERY bizzare to me, perhaps indicating some sort of memory corruption. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project 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?199902111813.KAA01018>