aMule Forum
English => aMule Help => Topic started by: Monoix on November 20, 2014, 06:28:25 PM
-
Just installed aMule after migrating to linux mint. But aMule locks up and gets totally unresponsive after running a few days, and I have to kill the process manually. Any tips on what I should try or check for to see what the problem is?
And just realizing there is a logfile that might hint towards something... I just restarted, so it's over-written now though. Anything else, until I can check that log again?
Mint 17, fresh install, aMule 2.3.1-11 standard install.
-
The previous logfile is saved in logfile.bak. If you have not restarted aMule more than once since the lock-up it may hold useful information.
Is there anything accompanying the lock-up? I mean anything like high CPU-usage (by aMule), extremely high memory usage, or something like that...
-
I noticed the backup file after I made the post here actually, and after that aMule crashed again so I got another logfile too, but they didn't contain any useful information really. Crashes at different standard procedures apparently, one file ending with "ServerUDP: Got server search reply with additional packet.", the other with that some downloaded part was corrupt - messages that both occured many many times before in the logs.
-
I have not found any information on the Linux Mint pages on what patches they have applied to the original aMule source. If you know such a source of information, please let me know.
You may try to create a backtrace of your crash, see How to post useful backtraces (http://forum.amule.org/index.php?topic=4115.0). If that doesn't work, you may have to compile aMule for yourself, but in this case I'd suggest compiling a recent snapshot (http://amule.sourceforge.net/tarballs/), there have been many fixes applied since the 2.3.1 release.