Print

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

[yankee]

I am using aMule 2.1.0. I hadn't run the client in a few days and started it up again yesterday. I am sharing 16 files (about 15 GB) and I started noticing that I get many requests for uploads, but many of them just flash up in the uploads window for a second and then disappear. Sometimes a request will succeed and the upload goes as normal. If all the upload slots are taken by these successful uploaders, my queue quickly builds up to about 120. When the slots go away, the queue quickly drops back to 0 and the flashing of requests commences.

I have opened up the TCP and UDP ports in my firewall, and before yesterday I never had any trouble with uploads. Any thoughts?

[yankee]

As the problem persists, I have done a little debugging and here is some sample log output:

For those connections that get dropped I get the following entries (IP address changed)

2006-02-23 09:37:10: ED2k Client: Accepted connection from 192.168.0.1
2006-02-23 09:37:11: Local Client Protocol: Local Client: OP_HELLOANSWER to 192.168.0.1
006-02-23 09:37:11: Local Client Protocol: Local Client: OP_SECIDENTSTATE
2006-02-23 09:37:14: ED2k Client: 'http://emule-project.net' has passed the secure identification, V2 State: 0
2006-02-23 09:37:15: ED2k Client: --- Deleted client "Client http://emule-project.net on IP:Port  192.168.0.1:4662 using eMule v0.47a"; Reason was Client 'http://emule-project.net' (IP:192.168.0.1)  caused a wxSOCKET_LOST event.

As I stated in my first post, this happens to most the clients that try to connect to my client, but not all of them. Any clue what is going on?

Thanks!

[WK1]

I have the exact same problem! I've only had it for an hour though, so I haven't gotten six uploads yet.

It was working fine for me last week. I haven't used it in that time, but rather used amule daemon on a dedicated machine. I have since turned off the dedicated amule machine, and come back to my main machine. Now, almost every upload disappears immediately. It jus flashes by. I am using amule 2.1.6 on debian sarge.

I can't imagine what could be causing this?!? I haven't done any debugging; I wouldn't know where to start. I just keep hoping it will solve itself.

I came to this forum searching for the answer, but all I found was this half year old, unanswered post. Does anyone have any clue what could be wrong with amule? Thank you.

Update:

The only thing I think of is that maybe this is normal? Perhaps the gui is flawed somehow, and misdisplays people doing searches or something. Maybe the people flashing across the upload pane aren't really looking for files that we have? It just looks like it due to some aMule bug?

It's just a theory. I'm going to leave aMule on all night, see how it goes. Maybe I'll get the full upload and large queue I'm used to again. I'll report back here. Hopefully someone has an answer to this, but I think it is an old, yet unresolved aMule bug. Nobody on any similar threads seems to have an answer.

Update 2:

Theory number two. This activity is of a malicious nature. I do not have an ip filter installed. I don't know how to check the IPs regarding this activity. Someone else on the emule (yes, emule) boards had the same problem, and this activity was coming from a limited set of ip ranges. Perhaps the RIAA is using some trick to find out what I'm sharing? Or perhaps this is a leech trick. The leech trick doesn't make a lot of sense, though, because I wasn't uploading anything to anybody at the time, they could have had all of my bandwidth.

So, theory number two is "malicious behavior." Either spying or sabatoge. Again, just a theory.

Here is a link to the similar emule thread:
http://forum.emule-project.net/index.php?showtopic=109705&st=0

And btw, I've been running for a couple hours or so, and my upload is high, and my queue list is large again. So, i guess it solved itself. Or the sabatour, if that is what it was, has moved on (or is in my queue).

Update 3:

When a chunk finished, and it was time to cycle the queue again, my uploads, once again, started dropping like flies. That didn't last long. Same problem as with OP.

So, theory number three. My ISP is Comcast. This seems to be a consistent problem with Comcast. It's like they have identified my server, and when a person tries to connect to me to download, Comcast sends a disconnect packet. So, basically, it is a race. Comcast wins 95% of the time, because they are in the middle, and therefore have an advantage. 2-5% of the time, a client actually wins, and they get to download from me. This is, once again, just another theory. But I think this one is it. I am almost positive.

The thread I linked to above seems to have actually come to this conclusion, that those with this problem are using comcast. If you are using comast, and have come to the thread trying to find out why your uploads drop like flies, this is probably why.

[MKS]

I have the same problem as well.  And my provider is Comcast, too.  I used to run eMule on the same machine and didn't experience these difficulties.  It seems to me that this is a bug of some sort in aMule.

Update:
Actually, I tried to run eMule just now and I am having the same sort of problem.  So, it probably means that Comcast is to blame here... it looks like it's blocking p2p traffic.  I don't think it is a bug in aMule.  There are similar stories on the eMule forum and people who report these problems are also with Comcast.