aMule Forum
English => aMule Help => Topic started by: eithel on June 19, 2006, 12:44:58 PM
-
Hi everyone, I have been running aMule in my Debian box for quite long and I'm recently suffering some problems with Kad since the last build came out (2.1.3). My Kad connects ok, changes from "firewalled" to "ok" after a few minutes, but after some time, maybe a couple of hours or so, it turns "off" automatically. This is very annoying because I get less sources, particularly for files with less sources. :(
Did any of you observe this behaviour? Any suggestions on how to fix it? ?(
Thanks in advance for your time and congratulations to the development team for this wonderful application (ole vuestros güevos!). :baby:
Greetings from Spain!
-
your using the daemon or the normal aMule?
-
Sorry, forgot to mention that I'm using the standard GUI version of aMule.
Thanx!
-
I used to have this behaviour a lot with 2.1.0, 2.1.1 and 2.1.2, but for now it seems that 2.1.3 is running well.
As for a solution, there has not been one suggested yet. There is a thread on the forum (here (http://forum.amule.org/thread.php?threadid=8604&sid=&threadview=0&hilight=&hilightuser=0&page=1)) which is quite long, but nobody seems to really know why it is happening.
Best advice: Check the status every now and then and restart the monolith or daemon.