Re: rTorrent + FreeBSD + pf = freeze?
Hi Michael, On 24.11.2009 00:41, Michael K. Smith wrote: We had similar crashes with PF, although not related to rtorrent specifically. However, we use the following sysctl values that have helped stability and performance immensely. net.inet.carp.preempt=1 net.inet.carp.arpbalance=0 net.inet.icmp.icmplim=2000 net.inet.tcp.sendspace=65536 net.inet.tcp.recvspace=65536 net.inet.tcp.blackhole=2 net.inet.udp.blackhole=1 kern.ipc.somaxconn=32768 net.inet.tcp.mssdflt=1460 kern.ipc.maxsockbuf=16777216 kern.ipc.nmbclusters=32768 kern.maxfiles=65536 kern.maxfilesperproc=32768 kern.maxvnodes=60 net.inet.tcp.delayed_ack=0 net.inet.tcp.inflight.enable=0 net.inet.tcp.path_mtu_discovery=0 net.inet.tcp.recvbuf_auto=1 net.inet.tcp.recvbuf_inc=16384 net.inet.tcp.recvbuf_max=16777216 net.inet.tcp.rfc1323=1 net.inet.tcp.sendbuf_auto=1 net.inet.tcp.sendbuf_inc=8192 net.inet.udp.maxdgram=57344 net.inet.udp.recvspace=65536 net.local.stream.recvspace=65536 net.inet.tcp.sendbuf_max=16777216 thank you for the hint. I tried those values which seem to affect the traffic class i'm talking about. So what I actually changed is listed below: sysctl kern.ipc.somaxconn=512 sysctl net.inet.tcp.sendspace=65536 sysctl kern.ipc.maxsockbuf=1048576 sysctl kern.ipc.nmbclusters=32768 sysctl kern.maxvnodes=20 sysctl net.inet.tcp.recvbuf_max=16777216 sysctl net.local.stream.recvspace=65536 Interesting enough I really was able to start the mentioned rtorrent instance without crashing the machine. but unfortunately the crash just was delayed so that the machine rebooted after ~3hours. However these values seemed to affect the stability and are somehow related with the problem. For now i'm just upgrading to 8.0-RELEASE and will see how things change.. regards - michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rTorrent + FreeBSD + pf = freeze?
On 22.11.2009 23:11, cpghost wrote: 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? even though i haven't been asked i might want to answer ;) Since my box really exclusively does rtorrent i don't think it's related to routing or NAT. pf is not active at all. Routing and NAT for my setup is done by a dedicated different box (which isn't affected by all this, apart from that it doesn't run freebsd). so for me this really looks like a /networking/ issue, which is not dedicated to routing or NAT in particular.. for me this now becomes kinda problematic, since i cannot even start the second rtorrent instance without crashing the machine immediately.. :( regards - michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rTorrent + FreeBSD + pf = freeze?
On 22.11.2009 23:11, cpghost wrote: 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? even though i haven't been asked i might want to answer ;) Since my box really exclusively does rtorrent i don't think it's related to routing or NAT. pf is not active at all. Routing and NAT for my setup is done by a dedicated different box (which isn't affected by all this, apart from that it doesn't run freebsd). so for me this really looks like a /networking/ issue, which is not dedicated to routing or NAT in particular.. for me this now becomes kinda problematic, since i cannot even start the second rtorrent instance without crashing the machine immediately.. :( regards - michael ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rTorrent + FreeBSD + pf = freeze?
On 11/23/09 2:28 PM, Michael Schaefer utf...@googlemail.com wrote: On 22.11.2009 23:11, cpghost wrote: 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? even though i haven't been asked i might want to answer ;) Since my box really exclusively does rtorrent i don't think it's related to routing or NAT. pf is not active at all. Routing and NAT for my setup is done by a dedicated different box (which isn't affected by all this, apart from that it doesn't run freebsd). so for me this really looks like a /networking/ issue, which is not dedicated to routing or NAT in particular.. for me this now becomes kinda problematic, since i cannot even start the second rtorrent instance without crashing the machine immediately.. :( regards - michael We had similar crashes with PF, although not related to rtorrent specifically. However, we use the following sysctl values that have helped stability and performance immensely. net.inet.carp.preempt=1 net.inet.carp.arpbalance=0 net.inet.icmp.icmplim=2000 net.inet.tcp.sendspace=65536 net.inet.tcp.recvspace=65536 net.inet.tcp.blackhole=2 net.inet.udp.blackhole=1 kern.ipc.somaxconn=32768 net.inet.tcp.mssdflt=1460 kern.ipc.maxsockbuf=16777216 kern.ipc.nmbclusters=32768 kern.maxfiles=65536 kern.maxfilesperproc=32768 kern.maxvnodes=60 net.inet.tcp.delayed_ack=0 net.inet.tcp.inflight.enable=0 net.inet.tcp.path_mtu_discovery=0 net.inet.tcp.recvbuf_auto=1 net.inet.tcp.recvbuf_inc=16384 net.inet.tcp.recvbuf_max=16777216 net.inet.tcp.rfc1323=1 net.inet.tcp.sendbuf_auto=1 net.inet.tcp.sendbuf_inc=8192 net.inet.udp.maxdgram=57344 net.inet.udp.recvspace=65536 net.local.stream.recvspace=65536 net.inet.tcp.sendbuf_max=16777216 Regards, Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rTorrent + FreeBSD + pf = freeze?
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/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rTorrent + FreeBSD + pf = freeze?
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: Hello, 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. Regards, -Peter 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 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/m...@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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rTorrent + FreeBSD + pf = freeze?
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/m...@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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rTorrent + FreeBSD + pf = freeze?
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 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/m...@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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rTorrent + FreeBSD + pf = freeze?
Hello, 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. Regards, -Peter 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 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/m...@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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org smime.p7s Description: S/MIME Cryptographic Signature
Re: rTorrent + FreeBSD + pf = freeze?
On Thu, Oct 22, 2009 at 03:20:20PM -0800, Henrik Hudson wrote: On Wed, 21 Oct 2009, cpghost wrote: 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/m...@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. Possibly a heat issue? I've seen many a little dlink style or similar router work fine until it has to churn through a lot of packets and then it just can't handle it, starts getting warm doing all the computation and then eventually freezes. I'm not ruling out a memory leak or similar, but I'm currently doing the same with a little atom ITX board and it handles all the torrents for myself and the roomies without issue. I'm using rtorrent myself with pf and 8.0-RC1-stable. I believe the pf code is backported to 7. Also, if it was just a memory leak it will still happen with non-torrent traffic, just most likely slower. Have you tried throttling back the amount of connections and speed that rtorrent makes? I've suspected a heat issue too, but sysutils/env4801 logging every 1 minute didn't show anything suspicious prior to the crashes. The system crashes ONLY on bittorrent traffic. Saturating the link (in one or both directions) even for many days in a row with 5 to 10 concurrent TCP streams to fixed destinations didn't cause any crashes. Yes, I've played with bandwidth and nr. of connections in rtorrent, and, if at all, I have a feeling (but I can't proove it) that the number of concurrent connections doesn't harm, but that the higher the output bandwidth, the more likely the crash. The only thing I didn't test yet was to replace the original DC transformer with another one that is a tad better dimensioned. Those transformers that are sent with the net4801(s) tend to degrade over the years for some reason (drying capacitors?). If it's not a software issue, this could be the cause of the crashes. henrik Thanks for the hints, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rTorrent + FreeBSD + pf = freeze?
Afaik the problem with fillling the router with torrent traffic as opposed to a single host, is that the the many connections to the many host fill up the (yes and this i don't know so I'll just say router). So Its not the torrent traffic itself.. its that you have a lot of packets going a million places. And as the others say, I've also seen a lot of small routers go down on it, with the only solution is to set a max in number of connections. On Fri, Oct 23, 2009 at 8:16 PM, cpghost cpgh...@cordula.ws wrote: On Thu, Oct 22, 2009 at 03:20:20PM -0800, Henrik Hudson wrote: On Wed, 21 Oct 2009, cpghost wrote: 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/m...@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. Possibly a heat issue? I've seen many a little dlink style or similar router work fine until it has to churn through a lot of packets and then it just can't handle it, starts getting warm doing all the computation and then eventually freezes. I'm not ruling out a memory leak or similar, but I'm currently doing the same with a little atom ITX board and it handles all the torrents for myself and the roomies without issue. I'm using rtorrent myself with pf and 8.0-RC1-stable. I believe the pf code is backported to 7. Also, if it was just a memory leak it will still happen with non-torrent traffic, just most likely slower. Have you tried throttling back the amount of connections and speed that rtorrent makes? I've suspected a heat issue too, but sysutils/env4801 logging every 1 minute didn't show anything suspicious prior to the crashes. The system crashes ONLY on bittorrent traffic. Saturating the link (in one or both directions) even for many days in a row with 5 to 10 concurrent TCP streams to fixed destinations didn't cause any crashes. Yes, I've played with bandwidth and nr. of connections in rtorrent, and, if at all, I have a feeling (but I can't proove it) that the number of concurrent connections doesn't harm, but that the higher the output bandwidth, the more likely the crash. The only thing I didn't test yet was to replace the original DC transformer with another one that is a tad better dimensioned. Those transformers that are sent with the net4801(s) tend to degrade over the years for some reason (drying capacitors?). If it's not a software issue, this could be the cause of the crashes. henrik Thanks for the hints, -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- Med Venlig Hilsen Kalle R. Møller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: rTorrent + FreeBSD + pf = freeze?
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/m...@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. Possibly a heat issue? I've seen many a little dlink style or similar router work fine until it has to churn through a lot of packets and then it just can't handle it, starts getting warm doing all the computation and then eventually freezes. I'm not ruling out a memory leak or similar, but I'm currently doing the same with a little atom ITX board and it handles all the torrents for myself and the roomies without issue. I'm using rtorrent myself with pf and 8.0-RC1-stable. I believe the pf code is backported to 7. Also, if it was just a memory leak it will still happen with non-torrent traffic, just most likely slower. Have you tried throttling back the amount of connections and speed that rtorrent makes? henrik -- Henrik Hudson li...@rhavenn.net - God, root, what is difference? Pitr; UF ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
rTorrent + FreeBSD + pf = freeze?
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/m...@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. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
