From owner-freebsd-questions@FreeBSD.ORG Sun Nov 22 22:11:48 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BB6110656AD for ; Sun, 22 Nov 2009 22:11:48 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from fw.farid-hajji.net (fw.farid-hajji.net [213.146.115.42]) by mx1.freebsd.org (Postfix) with ESMTP id AB90B8FC19 for ; Sun, 22 Nov 2009 22:11:47 +0000 (UTC) Received: from phenom.cordula.ws (phenom [192.168.254.60]) by fw.farid-hajji.net (Postfix) with ESMTP id 6AA1A3734D; Sun, 22 Nov 2009 23:11:45 +0100 (CET) Date: Sun, 22 Nov 2009 23:11:44 +0100 From: cpghost To: Peter Kieser Message-ID: <20091122221144.GA18306@phenom.cordula.ws> References: <4B058999.20504@gmail.com> <4B05DE15.9070209@kieser.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B05DE15.9070209@kieser.ca> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-questions@freebsd.org, Michael Schaefer Subject: Re: rTorrent + FreeBSD + pf = freeze? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Nov 2009 22:11:48 -0000 On Thu, Nov 19, 2009 at 04:08:53PM -0800, Peter Kieser wrote: > This problem has been going on for at least the past 2 years. I've had > the exact same issue with rtorrent locking up or restarting machines > running FreeBSD, regardless of the hardware used. All I can say is that the machine that runs rtorrent itself doesn't crash (on me), no matter how much traffic it gets. BUT the FreeBSD router that NATs this traffic via pf does crash... and just as you've observed: more frequently lately than before. A crash once or twice a week is common now, while it was once every 4 to 6 months last year... That router also acts as a mail- and webserver, so it is not only dedicated to routing. Maybe that's significant. I don't know what it is, but it seems to happen more often when there's disk activity *on the router* than when the disks are mostly idle. Perhaps disk and net subsystems concurrently using a non-locked resource and killing each other? Have you tried to run rtorrent and the router on two different FreeBSD machines? Does it lock the router, or does it crash the rtorrent box only, or both? -cpghost. -- Cordula's Web. http://www.cordula.ws/