aMule Forum

English => en_Bugs => Topic started by: alvaroprudente on July 29, 2004, 12:53:34 AM

Title: only low-ID's (not firewalled!!!)
Post by: alvaroprudente on July 29, 2004, 12:53:34 AM

Fedora-Core 2 (rpm)
After switching from aMule RC3 to RC5 i do only get low-id's.
and don't argue with the firewall or ports... the signal comes definitely through the firewall as it did come through in RC3 and I didn't change anything.
I switched back to the FC release RC4a (and although I use FC2 and not FC) this release works anyway and I get again high ID's without changing anything ind the conf...

So I guess that something with the aMule-FC2-RC5 is wrong

Cheers

Title: Re: only low-ID's (not firewalled!!!)
Post by: phoenix on July 29, 2004, 01:26:52 AM

alvaroprudente,

Can you test a recent tarball?

http://amule.hirnriss.net/cvs/aMule-cvs-20040728.tar.bz2

Cheers!

Title: Re: only low-ID's (not firewalled!!!)
Post by: deltaHF on July 29, 2004, 01:32:35 AM

try rm -f .eMule

Title: Re: only low-ID's (not firewalled!!!)
Post by: alvaroprudente on July 29, 2004, 11:41:17 AM

@phoenix: will try... (p.s.: do I have to run the make, ... or is it enough to simply overwrite the older files?)

@delta HF: what should it help ro remove the folder .eMule with "rm -f .eMule" ? (BTW: I have only a folder called .aMule)

General P.S: Obviously a restart of aMule solved the problem. But actually it is quite boring to restart it every 8-12 hours...

Title: Re: only low-ID's (not firewalled!!!)
Post by: bootstrap on July 29, 2004, 03:18:55 PM

The problem seems to persist since cvs from 20040724.
Until today i tested a lot of tarballs/rpms and all show the same behaviour:
most connection attempts time out - others result in low id.

For now there seems to be no workaround. I'm using cvs from 20040723 where everything works as usual.

I tested that on different systems in different networks to be sure, and everytime i change to cvs-20040723 i instantly get connected with high id.

Most interesting is, that sometimes - without any change in amule prefs or network setup, aMule connects flawlessly. But that's only in about 2% of all connection attempts ...
I used cvs-20040728 for a day without problems - while the same rpm was not able to connect even one server on a different system. Today cvs20040728 is unable to connect to any server on my system as well.
I tested cvs-20040729 - same problem - fallback to cvs-20040723 and it instantly connected with high id.

Title: Re: only low-ID's (not firewalled!!!)
Post by: Jacobo221 on July 29, 2004, 03:23:21 PM

about the question to phoenix, yes, you'll have to rtun make and all that stuff. follow the compilation guides in http://wiki.amule.org
about the qyuestion to deltaHF, removing ~/.eMule is known to be a way to sometimes solve the lowid bug. ANd surely you have it. You have the ~/.aMule directory and the ~/.eMule file. check it ;)

Greetings!

Title: Re: only low-ID's (not firewalled!!!)
Post by: bootstrap on July 29, 2004, 03:44:37 PM

Further investigation of this issue showed up a solution.

Stop aMule - move your ~/.eMule to a safe place and restart aMule. Connect to a server. At this point don't start wondering - your settings are gone, but everything is fine - just follow this instructions...
Stop aMule again and restore your original .eMule file (which contains your settings like name/ports and more).

After this procedure our tests show that aMule starts connecting servers without problems.

Title: Re: only low-ID's (not firewalled!!!)
Post by: alvaroprudente on July 30, 2004, 04:01:01 PM

seems really to work this fix... very very strange...

will have to test if this solution helps forever or just for every new start og the app...

cheers

Title: Re: only low-ID's (not firewalled!!!)
Post by: bootstrap on July 31, 2004, 12:12:50 PM

I forgot to mention that you will have to do this every time you restart aMule - at least i have to do that...

Title: Re: only low-ID's (not firewalled!!!)
Post by: alvaroprudente on August 01, 2004, 02:51:42 PM

I just deleted the content of this post, as I thought that a replacing of the old eMule file through the newer one would be a solution, but unfortunately this was not repeatable and the error of low-id's reappears...

cheers

Alvaro

Title: Re: only low-ID's (not firewalled!!!)
Post by: deltaHF on August 02, 2004, 10:54:22 PM

plz downgrade to rc4a .. we are looking for the pb

Title: Re: only low-ID's (not firewalled!!!)
Post by: alvaroprudente on August 06, 2004, 11:34:29 AM

at the moment (I didn't test it yet very deeply) I can tell, that using CVS from the 3rd of August the problem des not reappear and a aMule restart gives immediately highID's
(But as I said: I didn't test it yet very intense, I just noticed that the last three times I started aMule I immediately got HighID's)

Title: Re: only low-ID's (not firewalled!!!)
Post by: Xaignar on August 06, 2004, 12:23:12 PM

Any help with this problem is appreciated. ;)
What about never CVS builds? LowID or HighID?

Title: Re: only low-ID's (not firewalled!!!)
Post by: alvaroprudente on August 10, 2004, 09:23:21 PM

I confirm that with version from 3rd august aMule gave only high id's.

I just installed version from 10th august and immediately I git a high ID, so I suppose that the problem is solved...

Actually I didn't test versions between.

Can anybody else confirm that aMule v newer than 0803 gets immediately High ID's?

Cheers

Alvaro

Title: Re: only low-ID's (not firewalled!!!)
Post by: Xaignar on August 10, 2004, 09:30:03 PM

Phoenix seems to have fix the bug. :D
So no worries.