

My system seems pretty stable without azureus. I haven't really got any other java programs to test to see if it's the vm, but I would have thought if it were the vm, switching to a different implementation would have fixed that.Salius wrote:Yes, it is very likely Java to blame as opposed to Azureus, but it could be either at this point. Or neither for that matterzgredek wrote: So, it's java to blame, not azureus or hardware?
I'm not sure but what if gentoo hangs even with azureus turned off?![]()

switching kernels also made my beryl performance go through the roof - at first it was barely crawling around and redraws in firefox and konqueror and amarok took ages.zxy wrote:I had no-2.6.18-no2 installed and changed to mm-2.6.19_rc5-r2.
no kernel was running ok, until lately, maybe it was time to recompile it, as I updated many apps, (dbus, ...)
but mm runs fine now and azureus too. Azureus runs now for 1 day with no problems.

Thanks for the suggestion but as I saw some days ago, ktorrents need to be worked on for some more time to be actually usable.StifflerStealth wrote: Just a suggestion: KTorrent is now in version 2.1 Beta and in portage. You may want to give that a try. Azureus for me takes a long time to start up and KTorrent is instant, it even supports the IP Filtering and the loading of the same database that safe peer uses.Just a suggestion.
Disk cache makes sense... It's now set to 4MB, before it was more (16, 32MB or so). Will check if it helps.StifflerStealth wrote: Now on to thread related things
I have this issue that you describe, as I mentioned earlier. Now that I think about it, the one thing that I did was to lower the disc cacheing thing. If Disc caching was off, it ran like crap, if the space allowed for it was too much, then Azureus crashed like you describe. I think I have it set at a 2 meg cache now. You could try playing with those numbers. I don't know if you tried this yet or now. But Like I said before, I have had it with Java and Azureus.
Cheers.

So you have the same problem... You can turn on azureus logs (options -> logging) but, at least I, couldn't find anything unusual there.tomalakborg wrote: hey guys - I wanted to chime in because I think I have the same problem.
I recently upgraded from 2.6.17-something to 2.6.18-r4, as well as some other system updates (azureus was not one of them).
It torrented fine for a while, but then it's doing this BS thing where it dies after 50-75mins. Complete X lockup, no hope of saving it. I ran the X session from an ssh session to see if I could recover some output, but I got nothing. Are there azureus/java logs I can check out?
As to a new kernel I recommend you try the newest possible -mm. Also, examine your network, we might not be alone here:)tomalakborg wrote: I'm going to try a new kernel and -aeDN world + revdep-rebuild
Think logically - you changed the kernel - no problem for a whole day, then it started... It clearly depends on the kernel, not java version (I checked whatever java was available) or hardware. You may also want to switch your network card and I suggest you choose _not_ a realtek chipset, they're cheap, popular but poor when it comes to performance. The second idea is about security. I sounds kinda strange for Linux but as torrent network grew significally we may be experiencing more and more of such anomalities...tomalakborg wrote:
UPDATE
After the world remerge, things worked for a whole day! Then they failed again
I tried everything, rolling back kernel, uninstalling sun-jdk 1.6 (although even with 1.6, azureus was set to use 1.5... shouldn't have made a difference). There's no difference between azureus and azureus-bin as far as this problem is concerned (although =azureus-bin-2.3.something will only last a few minutes). I'm convinced that this is a java problem. I swapped the hard drive into an identical machine that was running win2k without problems, so it's not hardware.
Any ideas? This is frustrating to no end!

I guess you're talking about wxGTK, If you want a GTK interface, you can disable the "gtk" USE flag and use gnome-btdownload for a really simple client, or get Deluge (although quiet buggy)zgredek wrote:Runnig a torrent client through wine where there is (or at least SHOULD be) a decent native client is nonsense...
I fired up azureus 2.5.0.0 and it seems a lot faster, will see if it crashes just like the previous version.
bittorrent wants to emerge ~20MB of stuff and packages I clearly don't want on my system...This is the last thing I'm gonna check.

There isn't? I guess I was hallucinating when I took this screenshot (and yes, you could do this months ago too.). Anyway KTorrent is quite mature and full featured. I tried all the torrent clients out there and KTorrent and Azureus are the only ones that satisfy my tastes, but KTorrent's integrated search is the reason why I use it (that and avoiding Java apps like the plagueAst0r wrote: The ktorrent client is not at all configurable. I wasn't ever able to get it to work in active mode. But with the regular bittorrent client, you can set up the port to use. That's probably why you were having trouble with ktorrent: because it doesn't have any (obvious) way to change the port to listen on. So ...
Back when I used it there were no such options, or at least it was not very obvious how to get them. I still prefer the standard bittorrent client with gtk support as I get very good speeds with it.sirdilznik wrote:There isn't? I guess I was hallucinating when I took this screenshot (and yes, you could do this months ago too.).Ast0r wrote: The ktorrent client is not at all configurable. I wasn't ever able to get it to work in active mode. But with the regular bittorrent client, you can set up the port to use. That's probably why you were having trouble with ktorrent: because it doesn't have any (obvious) way to change the port to listen on. So ...

Blast! I just blew out my gentoo install without backing .config up (my kernel config is very light and easy to remember what devices to enable stuff for)sirdilznik wrote: I had a similar problem a while back when running a torrent client. It would run fine for a seemingly random amount of time (usually 15 min - 2 hours), then it would completely lock my machine up and I would have to reboot. The problem would up being Adaptive File Readahead in my kernel config. Once I disabled that feature and recompiled my kernel, the problems went away. My torrents download/upload fine for days at a time regardless of which client I use now. I wonder if maybe you have Adaptive File Readahead enabled in your kernel?
Code: Select all
strace -o azureus.trace azureus > azureus.log
strace -o amule.trace amule > amule.logCode: Select all
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
NETDEV WATCHDOG: eth0: transmit timed out
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
NETDEV WATCHDOG: eth0: transmit timed out
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
NETDEV WATCHDOG: eth0: transmit timed out
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
NETDEV WATCHDOG: eth0: transmit timed out
e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex
NETDEV WATCHDOG: eth0: transmit timed out
...