From owner-freebsd-net Mon Oct 29 15:44:11 2001 Delivered-To: freebsd-net@freebsd.org Received: from acura.isprime.com (acura.isprime.com [130.94.138.66]) by hub.freebsd.org (Postfix) with ESMTP id C19C037B401 for ; Mon, 29 Oct 2001 15:44:09 -0800 (PST) Received: from winter (localhost [127.0.0.1]) by acura.isprime.com (8.11.3/8.11.2) with SMTP id f9TNi5W49077 for ; Mon, 29 Oct 2001 18:44:06 -0500 (EST) Message-ID: <000501c160d3$7b7362d0$cb8b5e82@winter> From: "Phil Rosenthal" To: Subject: Running out of sockets, TIME_WAIT state Date: Mon, 29 Oct 2001 18:43:16 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Disposition-Notification-To: "Phil Rosenthal" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have the kernel configured with 65536 sockets. This system is very fast, connected to a very fast network, with a very fast storage system. It is handling about 5000 connections per second and is maxing out its 65536 sockets (because so many are sitting in TIME_WAIT status). This box is pushing ~90 megabit out of a gig-e card and is only using about 50% cpu, but unfortunately it cant answer any more connections because there are no more sockets available. i tried lowering msl, but that seems to make the system act "wierd" (all the webserver processes seem to block at the same status) -- and i tried upping the sockets to 131072, but that seems to cause the system to panic. any ideas? --Phil To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message