Print

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

[jared1999]

Sometimes, after running for a while (at least 12 hours), the entries in the serverlist get deleted one by one until it is empty. So far I have not observed anything that could be a possible trigger for this behaviour, and have not been able to reproduce it at will. Source searching also stops when this happens, but uploads and downloads work as normal. I also stay connected to the current active server.

[deltaHF]

check: preferences / server / remove dead servers ..

cheers

[eddolix]

Hello to all,
from version aMule 2.0.0 and in the 2.0.1 it succeeds also me that the serveur list is always with a single serveur that one to which they are connected, even if in the preferences disable to cancel the server died in statistics always a single serveur it sees.
Use Fedora Core 1 wxGTK-gl-2.4.2-5.1.fc1.rf wxGTK-xrc-2.4.2-5.1.fc1.rf wxGTK-stc-2.4.2-5.1.fc1.rf wxGTK-devel-2.4.2-5.1.fc1.rf wxGTK-2.4.2-5.1.fc1.rf wxBase-2.4.2-1

  ?( 8o ;( X(

[ken]

This problem used to plague the Mac version of aMule.  The problem in that case was a bug affecting how aMule was determining the address of the servers.  Each time aMule tried to ping a server, it would fail.  Eventually, the fail count got high enough that aMule deleted the server from the list.

So, you should check for problems communicating to the servers.  Server pings are done with UDP.  So, check that aMule's UDP port at TCP+3 is opened in your firewall and forwarded by your NAT router.

[eddolix]

udp        0      0 0.0.0.0:4672            0.0.0.0:*                           28274/amule

Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2005-05-24 15:15 CEST
Interesting ports on hosxxx-xxx.pooxxx.interbusiness.it (xx.xx.xxx.xx):
PORT     STATE  SERVICE
4672/udp closed rfa
 
Nmap finished: 1 IP address (1 host up) scanned in 0.513 seconds

I believe that I am aMule not to open door UDP 4672. 8o ;( ?( X(

[ken]

I'm sorry.  I don't think I understand you.  What do you mean by "I believe that I am aMule not to open door UDP 4672"?

It appears that you are showing that aMule is listening on udp port 4672, which is correct.  It also appears that nmap is showing that it can't reach port 4672 from another host.  Is that right?

It looks like you may have a firewall or NAT device that isn't configured correctly.

[jared1999]

Originally posted by deltaHF
check: preferences / server / remove dead servers ..

It is set to remove dead servers after 2 retries, but the problem is that all servers are removed, even live ones. All ports are forwarded and accessible, so connectivity should not be a problem. And as mentioned, this only happens on rare occasion.

Originally posted by ken
Each time aMule tried to ping a server, it would fail. Eventually, the fail count got high enough that aMule deleted the server from the list.

This is exactly what seems to happen, though I can't be sure since I'm not able to reproduce it. All I've seen is a suddenly empty server list, with new servers being proclaimed dead and then deleted as they come in.
Was there a way to reproduce the problem in the Mac version?

[ken]

Originally posted by jared1999
Was there a way to reproduce the problem in the Mac version?

It was not only reproducible but unavoidable on the Mac until the bug was found and fixed.  All server pings always failed and the fail count just inexorably increased until the servers were deleted.

To watch this problem happen, set aMule to remove servers only after a few hundred retries.  You'll see those failure counts increase over time.  If the problem is intermittent, then the fail counts will return to 0 when pings succeed.

I don't know what would cause this problem to be intermittent.  Perhaps your network is congested and UDP packets are getting dropped.  Maybe very high CPU load would prevent aMule from processing received UDP packets fast enough.  Maybe your ISP is doing something weird.  Is your firewall keeping state for UDP communications?  Maybe its tables are filling up.  Similarly, maybe your router is confused.

Lots of "maybe"s.  ?(

[Kry]

Originally posted by jared1999
 All ports are forwarded and accessible, so connectivity should not be a problem.

Uh... no, you did show that's not true. nmap says the port is NOT accessible, so you should look for the reason you're filtering it on your side

[stefanero]

Kry, its 2 poeple posting here with that problem

[Kry]

Hummm... ok. Anyway