aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Kad turns off automatically after a couple of hours  (Read 2143 times)

eithel

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
Kad turns off automatically after a couple of hours
« 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!
Logged

stefanero

  • Some Support
  • Developer
  • Hero Member
  • *****
  • Karma: 8
  • Offline Offline
  • Posts: 4235
Re: Kad turns off automatically after a couple of hours
« Reply #1 on: June 19, 2006, 04:51:42 PM »
your using the daemon or the normal aMule?
Logged
In its default setup, Windows XP on the Internet amounts to a car
parked in a bad part of town, with the doors unlocked, the key in
the ignition and a Post-It note on the dashboard saying, "Please
don't steal this."

eithel

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
Re: Kad turns off automatically after a couple of hours
« Reply #2 on: June 19, 2006, 09:49:19 PM »
Sorry, forgot to mention that I'm using the standard GUI version of aMule.

Thanx!
Logged

vdb

  • Full Member
  • ***
  • Karma: 1
  • Offline Offline
  • Posts: 215
Re: Kad turns off automatically after a couple of hours
« Reply #3 on: June 20, 2006, 04:29:13 PM »
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) 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.
Logged
A waste is a terrible thing to mind.