Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 03 May 2007 22:09:17 -0300
From:      "Marc G. Fournier" <scrappy@freebsd.org>
To:        Robert Watson <rwatson@FreeBSD.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Socket leak (Was: Re: What triggers "No Buffer Space) Available"?
Message-ID:  <D2A2BB0F2857DF90BFC07305@ganymede.hub.org>

next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I'm trying to probe this as well as I can, but network stacks and sockets have 
never been my strong suit ...

Robert had mentioned in one of his emails about a "Sockets can also exist 
without any referencing process (if the application closes, but there is still 
data draining on an open socket)."

Now, that makes sense to me, I can understand that ... but, how would that look 
as far as netstat -nA shows?  Or, would it?  For example, I have:

mars# netstat -nA | grep c9655a20
c9655a20 stream      0      0        0 c95d63f0        0        0
c95d63f0 stream      0      0        0 c9655a20        0        0
mars# netstat -nA | grep c95d63f0
c9655a20 stream      0      0        0 c95d63f0        0        0
c95d63f0 stream      0      0        0 c9655a20        0        0

They are attached to each other, but there appears to be no 'referencing 
process' ... it is now 10pm at night ... I saved a 'snapshot' of netstat -nA 
output at 6:45pm, over 3 hours ago, and it has the same entries as above:

c9655a20 stream      0      0        0 c95d63f0        0        0
c95d63f0 stream      0      0        0 c9655a20        0        0

again, if I'm reading this right, there is no 'referencing process' ... first, 
of course, am I reading this right?

second ... if I am reading this right, and, if I am understanding what Robert 
was saying about 'draining' (alot of ifs, I know) ... isn't it odd for it to 
take >3 hours to drain?

Again, if I'm reading / understanding things right, without the 'referencing 
process', it won't show up in sockstat -u, which is why my netstat -nA numbers 
keep growing, but sockstat -u numbers don't ... which also means that there is 
no way to figure out what process / program is leaving 'dangling sockets'? :(


- ----
Marc G. Fournier           Hub.Org Networking Services (http://www.hub.org)
Email . scrappy@hub.org                              MSN . scrappy@hub.org
Yahoo . yscrappy               Skype: hub.org        ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFGOoe94QvfyHIvDvMRAj2LAKDXobcYr4VGOB+WfXYqCBTatZNZLQCfbyWa
zsG/o1K3RM3ybjA5RLiSW5s=
=8DJi
-----END PGP SIGNATURE-----




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D2A2BB0F2857DF90BFC07305>