Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Radek]

Same environment here: More or less constant public IP-address and constant internal IP-address behind NAT/NAPT with (working) port forwardings. I'm in Germany, so no Fastweb.

It maybe worth mentioning though , that my router (Bintec X1200 II) has a symmetric NAT. Most SoHo-Routers don't have that. It is almost exclusively found in the more expensive router variants.

Last time I restarted amuled (CVS 2005-12-07) I had a kad connection for some 24+ hours, with several reconnects during that period. The behaviour didn't change at all since last post.

I'll try today's snapshot later.

[vdb]

For CVS 20051210 I can say that it does the same again. I don't have the logs to verify the connect/disconnect behaviour (running detached daemon), but it seems that after roughly 26 hours the connection to Kad is gone again. Only way to connect to it is shutting down and restarting the daemon.

I also run the daemon behind a NATtin router, with the 3 ports forwarded to the Linux box. The provider I use claims to not use traffic shaping devices of any sorts on their network.

I'll run the monolith for a while today to see if it the Kad connect also appears on that one. To be continued.....

[vdb]

To bring this thread to a close, I think it is fixed now, thanks guys:

2005-12-19 09:14:39: Read 0 Kad contacts
2005-12-19 09:14:40: Kad started.
2005-12-19 09:14:46: Kad stopped.
2005-12-19 09:14:46: Connected to Kad (firewalled)
2005-12-19 09:17:41: Connected to Kad (ok)
2005-12-19 10:14:40: Connected to Kad (firewalled)
2005-12-19 10:14:41: Connected to Kad (ok)
2005-12-19 12:14:43: Connected to Kad (firewalled)
2005-12-19 12:14:43: Connected to Kad (ok)
2005-12-19 14:14:45: Connected to Kad (firewalled)

2005-12-22 07:15:48: Connected to Kad (firewalled)
2005-12-22 07:15:48: Connected to Kad (ok)
2005-12-22 08:15:47: Connected to Kad (firewalled)
2005-12-22 08:15:47: Connected to Kad (ok)
2005-12-22 09:15:47: Connected to Kad (firewalled)
2005-12-22 09:15:47: Connected to Kad (ok)

It seems the disconnect no longer happens, although there still is this odd behaviour where it connects every few hours. But if it stays on Kad, I'm happy  

[stefanero]

btw is there something happening every houre at your pc?
since this looks to me like a self made problem with the

firewalled -- ok

it happens once every houre, you could almost set the clock

[mithrandir77]

I have had this problem for two days...

Today it seems to work correctly

[vdb]

There are lots of things happening every hour: Cron jobs checking things. But these are all scheduled to run on minute 1 or 2 of the hour.

This behaviour of aMule is happening every hour on the starting time of aMule, independant of what time that actually is. It must be something within aMule to trigger this. (or perhaps something in my router, but it doesn't show anything in it's logs, and then why would it do something on just port 4676?). Also you might note that it does not happen every hour, sometimes it skips one or two hours before doing the firewall/ok sequence.

Perhaps noteworthy that I do not use the standard aMule ports on my Linux daemon, I have upped them a few to be able to run 2 mules simultaniously.

[Kry]

aMule recheckes the firewalled state every hour. If the re-check ping packets don't get back, it assumes its firewalled. Later, they get back and it marks as OK. So it's perfectly normal behaviour.

[vdb]

Thanks for this explanation, and again, a great job fixing all these things!

[Radek]

I'm testing CVS-20051222 since 21:00  yesterday and till now everything is ok. Kad stays connected with it's more or less hourly status messages.

Too early for me to state something but looking good...

BTW: What do these

2005-12-22 21:03:27: Kad started.
2005-12-22 21:03:27: Servers: Connected
2005-12-22 21:03:27: Verbindung hergestellt auf: Razorback 2.0
2005-12-22 21:03:27: Verbunden zu Razorback 2.0 mit hoher ID
...
2005-12-22 21:03:27: Servernachricht: nicht geloggt werden. Wir arbeiten mit First-Laod zusammen und empfehlen euch einen 14 Tage Testaccount.
2005-12-22 21:03:27: Servernachricht: http://ng.razorback2.com
2005-12-22 21:03:32: Kad stopped.
2005-12-22 21:03:32: Kad verbunden (firewalled)
2005-12-22 21:03:52: Kad verbunden (ok)

red lines mean? Kad starts, then stops, and after that is connected?! It's somewhat confusing for me ?(

[Radek]

Not looking so good anymore - some hours later kad got disconnected again :-(

Partial Log

Code: [Select]

2005-12-22 21:03:26: Servers: Trying to connect
2005-12-22 21:03:26: Verbinde zu Razorback 2.0 (195.245.244.243 - 195.245.244.243:4661)
2005-12-22 21:03:26: Lese 39 Kad-Kontakte
2005-12-22 21:03:27: Verbunden zu Razorback 2.0 (195.245.244.243:4661)
2005-12-22 21:03:27: Kad started.
2005-12-22 21:03:27: Servers: Connected
2005-12-22 21:03:27: Verbindung hergestellt auf: Razorback 2.0
...
2005-12-22 21:03:32: Kad stopped.
2005-12-22 21:03:32: Kad verbunden (firewalled)
2005-12-22 21:03:52: Kad verbunden (ok)
...
2005-12-23 03:03:29: Kad verbunden (firewalled)
2005-12-23 03:03:29: Kad verbunden (ok)
...
2005-12-23 11:03:31: Kad verbunden (firewalled)
2005-12-23 11:03:31: Kad verbunden (ok)
2005-12-23 14:03:30: Kad verbunden (firewalled)
2005-12-23 14:03:30: Kad verbunden (ok)
...
2005-12-23 19:03:56: Kad getrennt
where the german "verbunden" means "connected" and "getrennt" means "disconnected"

"status" in amulecmd told me, that kad was stopped(!).

Some hours later I tried "connect kad" in amulecmd: Reply was "successfull", but nothing happened at all.
Next was "connect" in amulecmd, which told me sth like "servers already connected" and "connecting to kad".
The corresponding part of the log shows

Code: [Select]

2005-12-24 00:34:48: Lese 200 Kad-Kontakte
2005-12-24 00:34:48: Kad started.
and nothing more about kad until now (some 10 hours). But now "status" replies "kad disconnected".

CVS-20051222 amuled/amulecmd/amuleweb on Debian Sarge

[vdb]

Unfortunately I have the same thing here again with CVS 20051217:
[me@mine .aMule]$ cat logfile | grep Kad
2005-12-23 23:55:00: Read 0 Kad contacts
2005-12-23 23:55:01: Connected to Kad (firewalled)
2005-12-23 23:55:06: Connected to Kad (ok)
2005-12-24 03:55:02: Connected to Kad (firewalled)
2005-12-24 03:55:02: Connected to Kad (ok)
2005-12-24 05:32:21: Disconnected from Kad
[me@mine .aMule]$

Again nothing happening even closely around this time, it just goes "poof". And it did so wel the last few days.

Now that I think of it, until tonight I was constantly downloading multiple files. Tonight I had only 2 left to finish and they were going very intermittently. Maybe the disconnect occurs if there is no activity for a while on the download side of Kad?

[Radek]

Maybe the disconnect occurs if there is no activity for a while on the download side of Kad?

That's exactly my idea of some weeks ago. I also have quite few downloads which are very rare, too. So it might be a problem connected to not having much traffic. Or maybe the settings concerning the learning of new servers have some impact? I disabled this learning from other clients, because it was considered dangerous in some other threads.

[acehigh]

Thanks to Radek that showed me this thread.

I found the same problems you are pointing here in this thread.

I noticed the same connect every hour or two and the explanation from Kry fits.

I think the true problem is instead the disconnection from Kad and the inability to reconnect again without a restar of the daemon. I can't test the gui version because amuled runs in a machine where there is no X.
Has someone do some tests on the monolithic version?
I'm currently running the cvs 29122005 and still has the same disconnection problem. I tried the 04122055, 22122005 and this.

Someone of the developers can put some sort of debug info in the logfile when the kad disconnection happens so we can post the logfile in that occurrence?

[acehigh]

In any case: Happy new year to everybody!

[Pinky's Brain]

New user here, running 2.10 from debian unstable suffering from the same problem.

If I try to bootstrap with amulegui it fails, and the log file simply reads something like this :
2006-01-26 09:38:04: Read 200 Kad contacts
2006-01-26 09:38:04: Kad started.
2006-01-26 09:41:52: Kad stopped.

If I try to start kad with amulecmd it simply says it succeeds, but it really doesnt.

Has this been fixed in CVS? The changelog in the daily tarball mentions no such thing, and Im a little hesitant to run from CVS given the horror stories on the front page