aMule Forum
English => aMule Help => Topic started by: luquino on November 21, 2006, 06:36:12 PM
-
I'm using 2.1.3 CVS version, current snapshot 2006-11-20., on ubuntu dapper.
Each time I connect to a server amule freezes for about 90 sec. and the cpu goes to 100%.
Is it normal?
Thanks a lot.
-
Nobody can answer?
-
No, it is not normal.
-
Ok, it is not normal.... and?
There is something I can check?
-
Let's start with the usual things:
Version of wx? aMule? (Still the above CVS?)
What's the output of aMule when you open it in a terminal?
-
Sorry for delay, I wasn't able to connect in the last week for technical problems.
Here the output of amule starting in a terminal:
--------------------------------------------------
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /media/hdc1/downloads/aMule/scaricando.
All PartFiles Loaded.
ListenSocket: Ok.
External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
--------------------------------------------------
I omitted the list of empty dirs found. I suppose that the zeroes in the IP addresses in the above 3 lines are involved in the problem, but I don't know how.
In the log window of amule this is the version found:
2006-12-08 17:03:51: - This is aMule CVS using wxGTK2 v2.6.3 (Snapshot: Fri Dec 8 07:01:52 CET 2006) based on eMule
2006-12-08 17:03:51: Running on Linux 2.6.15-27-386 i686
-
Hi luquino!
The zeros are no problem, they mean 'every ip.
To phrase my question differently: What's the terminal output, when you connect to a server and cpu-load increases?
-
Hi wuischke!
Sorry for misunderstanding :(
Well I tried it right now, but there is no output at all on the terminal during connection to a server.
-
Never mind, there's no need to apologize,
Mh, is there any strange output in the log? I hoped for some nice error messages in the terminal which could easily explain...:(
-
No, unfortunately I have no strange report in the log, here what it says after the freeze period:
2006-12-08 17:49:31: Servers: Trying to connect
2006-12-08 17:49:31: Connecting to DonkeyServer No3 (62.241.53.17 - 62.241.53.17:4242)
2006-12-08 17:49:31: Connected to DonkeyServer No3 (62.241.53.17:4242)
2006-12-08 17:49:32: Servers: Connected
If the report log is well synchronized with the events it looks like that the freeze period is before the connection to the server, the merely connection is fast.
Mmmmhhh.... that's strange
-
I' ve been thinking on this trick......
Maybe in the freeze period it tries to access some unavailable resource? Can u teach me how to use the debug mode to understand what happens? (if it can help, obviously)
-
Well, you should compile aMule adding '--enable-debug --disable-optimize' to the configure command.
Then install gdb (See http://www.amule.org/wiki/index.php/Backtraces for more information) and start aMule the following way:
gdb amule
(gdb) run -eveniflfroencomplainsthiswillstay
Now there should be more information on what aMule's doing during the 'freeze'. This information will hopefully help solving the problem.
-
I use the precompiled version from here:
deb http://www.vollstreckernet.de/debian/ stable amule wx
My system is ubuntu dapper 6.06.1.
That version is already compiled for debug?
edit:
I already have gdb installed
-
Some new details.
I tried tyo connect some more times in order to understand something new, I found that the freeze period is not always before connecting to the server, sometimes before the connection some other times after the connection. But also now I'm listening a stream radio and always at the moment I double click the server to connect the radio mute for a while, less than the freeze period, but significant.
-
Maybe it's because you use the debian packages, which may not be 100% compatible. Please install aMule 2.1.3 from dapper-backports and tell us if it works here.
-
I removed the amule from wollstreckernet, and installed the one from dapper backport, this is the result:
luca@luca:~$ amule
amule: Symbol `_ZTI7wxSizer' has different size in shared object, consider re-linking
Fatal Error: Mismatch between the program and library build versions detected.
The library used 2.6 (no debug,Unicode,compiler with C++ ABI 102,wx containers,compatible with 2.4),
and your program used 2.6 (no debug,Unicode,compiler with C++ ABI 1002,wx containers,compatible with 2.4).
Aborted
Probably the problem is Wx library, I have installed 2.6.3.2-2. But not from ubuntu repos, because for dapper there isn't that version of wx. The only avalaible is 2.6.1 and with that version on my linux box amule crashes every 15 minutes.
-
Could you please install it nevertheless, just to test whether there's the same problem with freezing when connecting to a server?
-
Ok... with the dapper backports version of amule the performance of the program is even worst then the other version. The freeze period is longer (more or less the double). And I can' t understand why it has to rehash the 10 % of my shared files.....
A question: I have a large amount of shared files, is it a possible cause of the freeze?
-
How much is large? Anyway: Yes, it may very well cause the freeze, as it is transmitting all your shared files information to the server. But to cause a noticeable freeze it should be a really high number like about 1000 shared files.
BTW: You can install vollstrecker's packages again, it's not caused by the packages.
-
Ok. I tried to unshare all the files and the problem disappears. Definitevely is the amount of shared files. Very strange because they are exactly the same that I was using in eMule and there I never had this problem....
I thank you so much for the time you spent with me.
Cheers.