Date: Wed, 02 May 2007 14:34:55 -0300 From: "Marc G. Fournier" <scrappy@freebsd.org> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: What triggers "No Buffer Space Available"? Message-ID: <7F7C3ECEFCC7914576DA2033@ganymede.hub.org> In-Reply-To: <d763ac660705012000w5a5ae338id7c268a3fc082d0f@mail.gmail.com> References: <366565EAE2F989935287015E@ganymede.hub.org> <d763ac660705012000w5a5ae338id7c268a3fc082d0f@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- --On Wednesday, May 02, 2007 11:00:17 +0800 Adrian Chadd <adrian@freebsd.org>
wrote:
> It doesn't panic whe it happens, no?
Nope ... I can login via ssh (sometimes it takes a try or two, but I can always
login) and then do a 'reboot', and all is well again for another 72 hours or so
...
> I'd check the number of sockets you've currently got open at that
> point.
ie:
# netstat | egrep "tcp4|udp4" | awk '{print $1}' | uniq -c
171 tcp4
103 udp4
or is there a better command I should be using?
> Some applications might be holding open a whole load of sockets
> and their buffers stay allocated until they're closed. If they don't
> handle/don't get told about the error then they'll just hold open the
> mbufs.
Is there any way of determining which apps are holding open which sockets? ie.
lsof for open files?
- ----
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)
iD8DBQFGOMu/4QvfyHIvDvMRAldVAJ9B4uUUGbON16nWw+dR5QKveyQevACgju4M
TtBVUWAqf2PGqHVQxOnRbew=
=4/1c
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7F7C3ECEFCC7914576DA2033>