rTorrent + FreeBSD + pf = freeze?
utf128 at googlemail.com
Sat Nov 21 01:10:31 UTC 2009
well.. i think this is really something to escalate now since there is
obviously a problem. today again i tried a little bit and as told, the
isntance B crashes the system reproducible. In my opinion something like
this should really be examined further, since a userspace program
shouldn't kill the hole system...
for me this really looks like several people have similar problems but
so far there's no investigation since nobody knows what the actual problem.
any ideas how to proceed? can i provide any additional information?
since the system reboots immediately it's hard to investigate the
process of crashing itself.. at least for me.
regards - michael
On 20.11.2009 01:08, 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.
> I did not have any sort of firewall installed (neither pf, or ipfw). If
> I loaded up rtorrent and had a number of torrents open the machines
> would lock up or restart. It was reproducible at the time, but I could
> never get anyone to admit there was a bug and I'm unable to find the
> initial posting.
> Michael Schaefer wrote:
>> 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 pretty sure I encountered the problem also (even not
>> the heavily) during times instance B was only seeding about 300
>> 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:
>>> 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:
>>> 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.
>> freebsd-questions at freebsd.org mailing list
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe at freebsd.org"
More information about the freebsd-questions