From owner-freebsd-stable@FreeBSD.ORG Wed Jun 13 17:45:24 2007 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 35EE216A46E; Wed, 13 Jun 2007 17:45:24 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.freebsd.org (Postfix) with ESMTP id E17D413C48A; Wed, 13 Jun 2007 17:45:23 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from localhost (maia-4.hub.org [200.46.204.183]) by hub.org (Postfix) with ESMTP id 8E47AB47A86; Wed, 13 Jun 2007 14:45:23 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 78140-02; Wed, 13 Jun 2007 14:45:22 -0300 (ADT) Received: from ganymede.hub.org (blk-89-241-126.eastlink.ca [24.89.241.126]) by hub.org (Postfix) with ESMTP id 83CC3B47A84; Wed, 13 Jun 2007 14:45:22 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 333EC5CAB6; Wed, 13 Jun 2007 14:45:22 -0300 (ADT) Date: Wed, 13 Jun 2007 14:45:22 -0300 From: "Marc G. Fournier" To: Jeremy Chadwick , Ulrich Spoerlein Message-ID: <7EEECFAE63E9B976653B3254@ganymede.hub.org> X-Mailer: Mulberry/4.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: stable@freebsd.org, rwatson@freebsd.org Subject: Re: Unix domain socket leak in 6-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2007 17:45:24 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Wednesday, June 13, 2007 09:17:36 -0700 Jeremy Chadwick wrote: > I've seen this kind of problem with domain sockets (at least on Linux > with a multi-use tool called busybox) where on error conditions the > code never bothered to close the existing socket it opened, thus > resulting in leaks/resource exhaustion over time. The code later got > fixed, but a pretty nasty bug especially when the program is used in > a lot of embedded products... > > In regards to FreeBSD, I remember reading some mails from Robert Watson > last month in regards to UNIX domain socket code changes: > > http://monkey.org/freebsd/archive/freebsd-stable/200705/msg00200.html 'k, just to ring in here ... I can definitely attest to there being a leak here, as it was me that was originally burned by it ... in my case, I eventually was able to isolate which VPS/jail was causing it and haven't run it since, but was never able to determine exactly what was causing it, since there wasn't really anything unusual running in that jail :( But ... based on the discussions that were had at the time, it was my understanding that if all applications were shut down on the server (to the bare minimal), eventually the kernel GC should clean up all residual sockets ... when I did this (shut down all applications but the very bare minimum) and waited for 10+ minutes, socket usage never drop'd below about 4k sockets in use, or something like that ... Unlike Ulrich, I wasn't running LDAP at the time, so that wasn't the cause for me ... I could easily enough restart that jail if there was some more useful information I could get from it, but the thread kinda dwindled off over time, and rebooting a server ever 3 days was getting a wee bit annoying to my clients :) But, if someone has something they'd like me to do to provide more info, I'm willing to do it (short of anything that requires DDB / console access ... that server is remote) ... - ---- 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) iD8DBQFGcC0y4QvfyHIvDvMRApuZAJ9xKfa2/LqkcMkFEr4vrtnLt3ObcQCg43hs 7QX1hYskbQh/L8XJn1r1/Ts= =xKdx -----END PGP SIGNATURE-----