From owner-freebsd-questions@FreeBSD.ORG Sun Feb 25 10:23:25 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DAACE16A402 for ; Sun, 25 Feb 2007 10:23:25 +0000 (UTC) (envelope-from gpeel@thenetnow.com) Received: from thenetnow.com (thenetnow.com [69.90.69.141]) by mx1.freebsd.org (Postfix) with ESMTP id B6C9113C441 for ; Sun, 25 Feb 2007 10:23:25 +0000 (UTC) (envelope-from gpeel@thenetnow.com) Received: from hpeel.ody.ca ([216.240.12.2] helo=GRANT) by constellation.thenetnow.com with esmtpa (Exim 4.54) id 1HLGXH-0006HY-V6 for freebsd-questions@freebsd.org; Sun, 25 Feb 2007 05:23:20 -0500 Message-ID: <00aa01c758c6$f8dadb90$6501a8c0@GRANT> From: "Grant Peel" To: Date: Sun, 25 Feb 2007 05:23:20 -0500 Organization: The Net Now MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 Subject: Fw: FIN_WAIT_2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Grant Peel List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 10:23:25 -0000 my problem is that so many of my vm-pop3d processes get in that state that semi-frequently, we get locked out of downloading email. I kill all the vm-pop3d processes then we have to wait for all the FIN_WAIT_2 to die befor i can restart the vm-pop3d process. If I try to start vm-pop3d before all the FIN_WAIT_2 sockets die, I get a 'Can't bind to port" error. When I do the lsof thing it shows no files or processes connected to that port, or socket. -Grant > ----- Original Message ----- > From: "Christian Walther" > To: "Grant Peel" > Cc: > Sent: Saturday, February 24, 2007 9:53 AM > Subject: Re: FIN_WAIT_2 > > >> On 24/02/07, Grant Peel wrote: >>> Hi all, >>> >>> Just wondering if anyone has found / knows of a way to kill sockets that >>> are stuck in FIN_WIAT_2 state - without rebooting the server. >>> >>> When I kill the processes (in this case the pop3 server) that allows the >>> connection, it still takes about 3 hours for the socket to time out and >>> die. >> >> What is your problem with sockets being in this state? Normaly they >> don't consume any resources that would lead to performance problems. >> As you say, they die eventually. >> Sockets in this state are no problem, it's just that the client failed >> to sent the last ACK to the server, which would finally close the >> communication. >> >> >