From owner-freebsd-questions@FreeBSD.ORG Thu Nov 19 13:17:13 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 C0D191065676 for ; Thu, 19 Nov 2009 13:17:13 +0000 (UTC) (envelope-from utf128@googlemail.com) Received: from mail-gx0-f218.google.com (mail-gx0-f218.google.com [209.85.217.218]) by mx1.freebsd.org (Postfix) with ESMTP id 822E68FC0C for ; Thu, 19 Nov 2009 13:17:13 +0000 (UTC) Received: by gxk10 with SMTP id 10so2015704gxk.3 for ; Thu, 19 Nov 2009 05:17:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=Ypk5uVIh7pxp4BieiGTCHxmohQoDTVF9I4DXEu9bKa0=; b=d6f+JlnRaDSyhDrCtxBcjQ+XuWMnu7RAJeE0nQu4C/J87QXu7/Z3pujkGWugFqwlSA TNuWixNOLsnU7jxtW2gSAtMh6Iy8SBLeotGx3fBQjeax3S/9TvcQvWHROCXWX+aJmg9t LOVVCtnzJ3WUX7vSkgLZeIG4KuqAcNpGescWY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=v10eKDsHzFWb+yu+XLgClLIe+a40iZAHTm+ayxBvuHApUOdpmx9muSEU/VNWX1hScC g+f8H/+7aTp0rnMpIRQEhVJVOl+tKaEbfxAKHxe50srs7BPsuJi9NWzYJq+CVpQ6ue5g 8bd43+UqTIFudiixBRg8j9tmlUdXEFvsZe/C4= MIME-Version: 1.0 Received: by 10.150.14.3 with SMTP id 3mr109800ybn.288.1258634803638; Thu, 19 Nov 2009 04:46:43 -0800 (PST) Date: Thu, 19 Nov 2009 13:46:43 +0100 Message-ID: From: "utf128@googlemail.com" To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 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: Thu, 19 Nov 2009 13:17:13 -0000 Hello everybody, I encountered same problems and am kinda glad to see I'm not alone. I use FreeBSD 7.1-RELEASE-p8 (GENERIC) on a VIA EPIA board (800MHz C3). This box for the moment does nothing but torrent. I use two instances of rtorrent. Each with an own user and in its own screen session. Let's name them A and B. A seeds around 300 torrents and B around 500 (each rtorrent instance communicates just to one specific tracker). The configuration is exactly the same, except B communicates with the track only using https (A does plain http). While A works 100% perfect an stable, B crashes the machine reproducible. When using rtorrent 0.8.3/0.12.3 this happened only about once a month. After upgrading to 0.8.4/0.12.4 the rate of crashes increased to about once a week. now i upgraded to 0.8.5/0.12.5 and cannot even start instance B without crashing the machine immediately just several minutes after I started it. Sometimes it somehow "survives" the starting procedure (where actually all seeding torrents are registered at the tracker at more or less the same time) but then it takes about 10min - 2 hours after the hole systems crashes again. Like I mentioned: instance B works perfectly without any problems. I'm prett y sure I encountered the problem also (even not the heavily) during times instance B was only seeding about 300 torrents... For me the system simply reboots and doesn't freeze. The logs are clear and show no advice concerning the problem. It's not a matter of hardware since I changed the board (which included CPU, RAM, NIC,...) and also the hard disc month ago. Also a heat problem can be excluded. Any clou about all that? btw: I don't use PF at all... regards - Michael On Wed, 21 Oct 2009, cpghost wrote: > > Hi, > > could a resource leak or bug in pf(4) crash a RELENG_7 router (as of > Oct 6th)? > > I'm experiencing frequent crashes on my soekris net4801 home router > for some months now, and I'm wondering if it could be some kind of > pf-related bug similar to this on OpenBSD: > > http://www.mail-archive.com/misc@openbsd.org/msg58042.html > > More precisely, when I fire up rtorrent-devel on some *other* machine > (not the router!), everything runs fine at first. It could also run > very fine for many days. BUT should I start a torrent with a large > number of seeders which could saturate my link for an extended period > of time, the soekris router would suddenly freeze... but not > immediately: more like a few hours (3 to 6) or so of relatively heavy > traffic. Only a hard reboot of the router would help. Please note > that rtorrent is NOT running on the router, only its traffic is being > redirected through the router. > > So I'm suspecting some bug / resource leak in pf that would bring the > kernel down somehow. What kind of resources should I monitor (and > how)? Maybe that could bring some clues? > > Oh, before anybody asks: I have no crashdumps, the router freezes > totally without panicking. And it doesn't recover automatically > even after many hours. > > Any ideas? > > Thanks, > -cpghost.