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 spontaneously dies  (Read 1957 times)

DustWolf

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
Kad spontaneously dies
« on: January 05, 2008, 03:19:38 AM »

I am running amuled on a Ubuntu 6.10 LTS server and GUI on Ubuntu 7.10 desktop and have noticed that Kad spontaneously disconnects.

I have had trouble getting kad to bootstrap in the first place (it would keep "firewalled") but after I left it overnight it seemed to work (became "OK"). However today I noticed that Kad is off with no real explanation whatsoever and won't reconnect.

Here is what I see in the logs:
$ cat logfile | grep Kad
2008-01-02 03:42:39: Read 200 Kad contacts
2008-01-02 03:42:40: Kad started.
2008-01-02 03:42:45: Kad stopped.
2008-01-02 03:42:45: Connected to Kad (firewalled)
2008-01-02 04:02:45: Disconnected from Kad
2008-01-02 23:23:16: Read 0 Kad contacts
2008-01-02 23:23:16: Kad started.
2008-01-02 23:26:15: Kad stopped.
2008-01-02 23:26:15: Connected to Kad (firewalled)
2008-01-02 23:28:38: Connected to Kad (ok)
2008-01-03 00:23:26: Connected to Kad (firewalled)
2008-01-03 00:23:26: Connected to Kad (ok)
2008-01-03 01:16:15: Disconnected from Kad
2008-01-04 03:22:13: Read 22 Kad contacts
2008-01-04 03:22:13: Kad started.

$ cat logfile | grep UDP
2008-01-02 03:42:39: MuleUDPSocket: Created Server UDP-Socket at port 21855
2008-01-02 03:42:39: MuleUDPSocket: Created Client UDP-Socket at port 21850

I used to use eMule in this network where kad had functioned just fine (e.g.: there is nothing wrong with my router or UDP port forwarding setup).
Logged