View source for AMule problems

<center>
<u><h4>[[aMule_Project_FAQ:About|aMule]] common problems</h4></u>

<h2>by ''[[User:Jacobo221|Jacobo221]]''</h2>

'''English''' | [[AMule_problems-es|Español]] | [[AMule_problems-nl|Nederlands]]
</center>

== I get an "aMule already running: exiting" message on the terminal when starting aMule. Will I be able to start it in any way? ==
This message is very clear: aMule is already running. But this doesn't refer to the entire system, but that '''you''' (your user account) is running aMule already.<br>
You might, anyway, think there's no aMule running, since it crashed. But it sometimes happens that some processes aren't completly closed, instead they keep in a status known as ''zombie'' or ''defunct''. To know if this is your problem, run ''ps u | grep amule'' and if it shows any output, then there's some other aMule process running with your account. To kill it, either close it normally (if you can) or kill it with ''kill -9 <aMule-PID>'' or ''killall -9 amule'' or logoff and log in again (which, in most cases should also kill aMule processes, except if you executed aMule with ''nohup'' or something alike).<br>
If non of the above suits you, then you can run another aMule as another user (if you can log in with another account, of course). Read [[FAQ_aMule#Can_I_run_two_aMule_instances_at_the_same_time?|Can I run two aMule instances at the same time?]].

== aMule starts but is never shown, allthough it's working fine. What's going on? ==
This may happen if you set the incorrect type of SysTray in Preferences -> General -> "Systray Integration" and you set aMule to minimize to tray and you set aMule to start minimized. So you really took some time to brake it, didn't you?<br>
To be able to recover aMule's GUI, edit ''~/.eMule'' and search for ''StartupMinimized=1'' and once you find it, change that line to ''StartupMinimized=0''. The following script will do that for you:<br>
''sed s/StartupMinimized=1/StartupMinimized=0/ ~/.eMule > ~/.eMule.temp && mv -f ~/.eMule.temp ~/.eMule''<br>
When you next start aMule set the correct SysTray integration in Preferences so that you can enable "Start minimized" without having aMule being hidden.<br>
If for some reason the above didn't work, try changing manually the Systray integration in your to the default "No systray integration" option. To do so, set the ''DesktopMode='' value in ''~/.eMule'' to ''4''. The following script will do that for you:<br>
''sed s/DesktopMode=[0-9]/DesktopMode=4/ ~/.eMule > ~/.eMule.temp && mv -f ~/.eMule.temp ~/.eMule''<br>
'''NOTE:''' On [[aMule]] versions previous to 2.0.0rc4, you should set it to ''1'' instead of ''4'' since the Preferences storage changed a little.

== aMule starts but is never connecting/behaving very weird/crashing almost every few seconds/etc...? ==
aMule versions up to 2.0.0-rc3 shouldn't be linked against wxWidgets 2.5.x neither GTK2 although some Linux distributions tend to do so. Please make sure your aMule isn't the case. If unsure, paste you backtrace at [http://www.amule.org/amule/board.php?boardid=33 aMule's Backtraces forum] or join aMule's IRC channel #amule at irc.freenode.net

== Where are my downloaded files? ==
By default, aMule stores completed files in ''~/.aMule/Incoming'' but, since ''~/.aMule'' directory is a hidden directory, your file manager might not show it. Make sure you have enabled your file manager to show hidden files.<br>
By default, files being downloaded are placed in ''~/.aMule/Temp'', so again, this is a hidden directory and the file managed must be configured to show hidden files.

== Why is aMule taking so much CPU resources at start-up? ==
This happens because aMule is hashing new files found on the Shared Directories.<br> If aMule is always taking a lot of CPU at startup and no new files have been added or modified in any way in the Shared Directories, then something is wrong.<br>
In aMule versions earlier than 2.0.0-rc3 this used to happen when having the Temp, Incoming or any Shared Directory in a FAT32 partition. Since aMule 2.0.0-rc3 this is not happening any more.<br>
Also, in aMule versions earlier than 2.0.0-rc4 filesystems with UTF-8 encoding (known to happen with SuSE 9.1) could present problems when some file or directory in the Shared Directories path contanied a special character. If this is your problem, there's a walkaround (thanks '''nachbarnebenan'''): after aMule has hashed all shared files (that is, when it stops taking a lot of your CPU's resources), close aMule and enconde ~/.aMule/known.met into UTF-8 encoding (you can do this with the application ''[http://www.gnu.org/directory/recode.html recode]'' by running the following command: ''recode u8 ~/.aMule/known.met''). This should be done whenever a files is added or modified in any Shared Directory. So, best option is to upgrade to latest aMule version.<br>
If non of the above helps you, then something went really wrong on ''known.met'' file, probably some external program or user broke it. Best option is to delete it, start aMule and let aMule rehash all files again.

== So now aMule starts, but why is it displaying this message: "No valid servers to connect in serverlist found"? ==
That's because you enabled the option "Auto connect to servers the static list only". So, disable it or add some server to the static list.<br>
To disable that option, go to Preferences -> Servers -> "Auto connect to servers the static list only"<br>
To add a server to the static list, go to the Servers window and right-click on the server you want to add to the static list. Then select "Add to static" and do this exact process wit all the servers you want to add to the static list.

== aMule connects to server, but it is always given LowID. Why? and, can I do something about it? ==
This can bue due to three reasons:
<ul><li>Some necessary port is not opened in your firewall. Read [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|this]] to get to know what to do and check [http://www.amule.org/testport.php here] if the ports are open.</li>
<li>The server is very busy or maybe badly configured, so it's giving you a [[LowID]]. There's nothing that can be done in this case other than reconnect or connect to some other server.</li>
<li>Some ISP forbid the use of p2p applications, such as aMule, by not allowing traffic through popular p2p ports. In these cases, configure aMule to use some other port. It would be even better if it was some popular port used for some other issue. It's been known that on some ISPs it worked with port TCP 25600.</li></ul>

== [[aMule]] was interrupted while completing a file and it is now never completing it (allthough it's 100% downloaded). How can I complete it? ==
This one is easy: Close [[aMule]]. Now go into the Temp directory (by default, ''~/.aMule/Temp'') and run the following command:

''touch ./*''

Finally, run [[aMule]] and let it complete the files.


== I just lost a download. Is there anyway I can recover it? ==
This is strange to happen, but it might, although in most cases it is the result of some non-aMule-related stuff going weird (or user's fault).<br>
Two things may have happened. Either *.part.met files were deleted, or *.part files were deleted.<br>
If *.part files have dissapeared, the only solution is to reastart the downloads from the beggining (if *.part.met files are still there, aMule will restart the downloads on next start). However this should '''never''' happen unless the user directly deleted them.<br>
If *.part.met files have dissapeared but *.part files are still in the Temp directory, then search if *.part.met.bak are also in the Temp directory. If they are, then just rename ''*.part.met.bak'' files to ''*.part.met'' just by running:<br>
''for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done''<br>
Still, it could happen that, although you have the *.part files, neither *.part.met nor *.part.met.bak files exist any longer. In this case, you would have two ways ways to work out of this:<br>
Either, use [http://www.bigwillystyle42.com/index.php?dest=mfr MetFileRegenerator] (Java needed) to reconstruct the *.part.met files.<br>
Or, search again on aMule for the files you were downloading and rename their part number in the *.part.met files to the ones it used to have. For example, if you ware down loading ''aMule_1.2.6.tar.gz'' and that was being downloaded in Temp directory as ''008.part'', then that file used to have it's corresponding ''008.part.met'' file and, probably, it's ''008.part.met.bak'' file. But this two latter files have misteriously dissapeared. Then search again on aMule for ''aMule_1.2.6.tar.gz'' and start downloading it. Close aMule and you'll have this new download as, for example, ''011.part'' file in the Temp directory. Of course, this download will have it's ''011.part.met'' file. Well, rename ''011.part.met'' to ''008.part.met'' and then delete ''011.part'' (and ''011.part.met.bak'' if it existed). Now start aMule and you will have recovered the download from the point it was before the *.part.met files disapeared.

== Why does aMule suddendly become unresponsive to the mouse although it's not hanged? ==
It sometimes happens that you left a dialog window somewhere hidden in the desktop. aMule is waiting for that window to be closed, so it becomes unresponsive untill you click OK, Cancel, or whatever you have to click.<br>
So, make sure there's no aMule dialog left around in '''any workspace'''.

== Why are some files in my shared folders not shown in the Shared Folders window? ==
This could happen if you added this files after aMule has been started. Press the "Reload" button on Shared Folders window and it should find the new files and hash them (this may take some CPU time).<br>
However, on some releases it has happened that after restarting aMule, some files dissapear from the Shared Folders window alllthough they are in the shared folders. In such cases, the only way to have them back is to delete ''~/.aMule/known.met'' but, of course, on next aMule start, all shared files will have to be rehashed, and that'll take some time most probably.

== I always get a message about addresses.met when I start aMule. What's wrong? ==
This happens when you enable the option Preferences -> Servers -> "Auto-update serverlist at startup" and you have no serverlists' urls in ''addresses.dat''. You can either add some to ''addresses.dat'' by adding them at Preferences -> Servers -> List or just disable Preferences -> Servers -> "Auto-update serverlist at startup" if you don't really need it.<br>

== I sometimes get a message on the log about credits being lost. Should I be worried? ==
No, you don't need to be worried. Credits for a client are deleted after 150 days (more or less 5 months) without "seeing" that client. Also, bad clients might lose their credits too. So those messages are just for debug information, you souldn't worry about them.

== What should I do if I lose my ''cryptkey.dat'' file? ==
Losing that file will automatically make you loose all your credits with it, sorry. IF you will to start collecting credits again from this very moment, delete ''~/.aMule/preferences.dat'' too. If you don't, you'll be unable to collect credits on those [[client]]s which had sometime (before loosing the ''cryptkey.dat file) identified you.

== Why is Upload/Download limit always back to 0 after every restart? ==
This happened on aMule versions previous to 2.0.0-rc4 when you trying to set a Upload or Download limit value higher than the Upload or Download Capacity value. However, since version 2.0.0-rc4 this is fixed (read [[FAQ_aMule#What_is_the_real_point_on_setting_up_Line_Capacities_in_Preferences?_Shouldn't_aMule_only_care_for_the_Bandwidth_Limits?|What is the real point on setting up Line Capacities
in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] to understand why) and shouldn't happen anymore.

== Why is aMule ignoring the bandwith I set per slot? ==
The bandwidth set to each slot can be set in Preferences, but it will be ignored if the bandwidth set per slot doesn't allow at least three connections at the same time.<br>
So, the maximum speed allowed per slot is '''BandwidthLimit/3'''.<br>
Please do '''NOT''' confuse '''Bandwidth limit''' with '''Bandwith Capacity'''. Read [[FAQ_aMule#What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?|What is the real point on setting up Line Capacities in Preferences? Shouldn't aMule only care for the Bandwidth Limits?]] since the meaning of the Bandwidth Capacity setting is not intuitive.<br>
Also, if [[aMule]] detects that, after having set all the slots for uploading, still some bandwidth is left before getting to the Bandwidth Limit, it will allow another slot and divide all the slot bandwidths to so use the same amount of bandwidth.<br>

Example:<br>
Bandwidth Limit: 7 KBps
Slot allocation: 2 KBps
When [[aMule]] sets the slots to some clients to upload to them, after giving out three slots, it will notice that tehre are no more 2KBps left, since the limit is 7 KBps, but there is still 1 KBps left in the bandwicth before reaching the Bandwidth Limit. So, It will allow another slot to upload to a client and, isntead of giving that last slot a 1 KBps bandwidth connection (and leave the rest with a 2 KBps bandwidth connetcion), it will give all four slots a 1.8 KBps bandwidth connection.

== Why can't I set aMule's download limit to more than X? ==
To keep the ED2K network alive, all ED2K clients have an upload/download limits ratio hardcoded which, depending on the upload limit set, is:

<u>From 0KBps to 3KBps:</u><br>
DownloadLimit can't be more than UploadLimit*3<br>
<u>From 4KBps to 9KBps:</u><br>
DownloadLimit can't be more than UploadLimit*4<br>
<u>UploadLimit values over 9KBps:</u><br>
There's <b>no</b> DownloadLimit limitation.

Be carefull when setting 0KBps as Upload Limit . It might not mean what you think it is. Read [[AMule_problems#I_set_Upload_Limit_to_0KBps,_but_aMule_is_still_transfering._What_did_I_do_wrong?|I set Upload Limit to 0KBps, but aMule is still transfering. What did I do wrong?]] to make sure you understand it's meaning.

== I set Upload Limit to 0KBps, but aMule is still transfering. What did I do wrong? ==
Setting Upload limit to 0KBps will not stop transfers, instead, ''0'' value means '''unlimited''', so, it's right the opossite of you're trying to do. There's no way to stop aMule from uploading files, and that's the same on all ED2K clients (eMule, eDonkey, etc). Allowing people not to upload would bring the ED2K network to it's end.<br>
Even if you don't share any directory, the Temp directory will '''always''' be shared, so that files that you are downloading are shared with other clients.

== Why am I getting "Too many connections" messages on the terminal? ==
This happens when you set a very high value at Preferences -> Connections -> "Connection limits" -> "Max connections". If this value is as almost as big as the the amount of connections your system allows you to have, then aMule will fail to establish connections and display those messages (have in mind that other applications may also have some connections established).<br>
On Windows 9x/ME platforms there is a limit of 100 TCP connections so, although you might set aMule to establish more than 100 connections, it will be unable to do so. You can change Windows's TCP connections limit by editting the Windows Register ('''Start -> Run -> regedit.exe''') and setting (you'll most surely have to add the value since in most cases it doesn't exist):<br>
''HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections'' (which is a String type and it's value must be a 32-bit number).

== My progress bars have lost most of their 3D effect and look more ugly now. Can I turn its look back? ==
On old aMule versions (previous to 2.0.0-rc4) setting the progress bar style to the most right on Preferences -> "GUI tweaks" was the way to have the progress bar have the best 3D effect. As of 2.0.0-rc4 the best 3D effect is given when the style bar is set to the middle. Setting it to the most right will give the progress bar a flat look while setting it to the most left will give it a dark look.

== All my downloads suddenly paused and I can't resume them. What's going on? ==

Check if there's any free space in the filesystem where the Temp directory is placed. If there is any at all, check if there's more free space than the minimum free space set at Preferences -> Files -> "Min disk space".

The minimum free space required for [[aMule]] is 9.28MB, since that's what [[aMule]] needs to be able to download a [[FAQ_ed2k#What_is_a_chunk?|part]] of a file.

== Why isn't Preview working at all? ==
Since aMule 2.0.0-rc4 Preview command isn't being run in the same terminal as aMule. As a result, your Preview program may fail to start. This is the case of MPlayer. If you need a terminal to run your Preview player, use some command like ''xterm -e <preview-app>'' i.e.:<br>
''xterm -T "aMule's preview" -iconic -e mplayer -idx''

== After exitting MPlayer on Preview, my aMule keeps locked? ==
Preview used to lock aMule on purpose until aMule reached version 2.0.0-rc4. As a result of this, people using MPlayer suffered from a bug on MPlayer which remains the main process in background when closing the main MPlayer window. The way to walk around this MPlayer bug on aMule versions previous to 2.0.0-rc4 is to exit MPlayer by pressing the '''Q''' key. Any way, it'd be better if you could possibly upgrade aMule to the latest versions.

== Why is ''Transfered'' a smaller number than ''Completed''? ==
It's a common mistake to think it should be bigger or, at least, equal.<br>
Please read [[FAQ_aMule#What_is_the_difference_between_Transfered_and_Completed_in_the_Tranfers_window?|What is the difference between Transfered and Completed in the Tranfers window?]] to know more about this.

== aMule always slows down my computer when it completes a download. Is this a normal behaviour? ==
Yes it is. When aMule completes a download it checks it has not been corrupted. Allthough this is already checked while downloading (by checking the chunk's hash values), once the file is completly downloaded aMule hashes all the chunks to check that the chunks which were previously downloaded weren't somehow corrupted by the user or an external application while the rest of the file was being downloaded.

== Is there any way to recursively select a whole directory and its contents? ==
Yes, there is. And it's simple:
*On [[aMule]] 2.0.0-rc4 or later, right-click the directory you want to recusively select.
*On [[aMule]] 1.x and up to 2.0.0-rc3 (included), while clicking on the directory, hold the CTRL key.<br>
And that's it.

== I downloaded a file and it got corrupted somehow by my hard disk or some external application once completed. Can I avoid redownloading the whole of it? ==
If you still have the [[ed2k_link|ed2k:// link]], start the download again and when a whole chunk (9.28MB) has been downloaded (any chunk), close [[aMule]], rename the corrupted file to the filename the current download has (something like ''002.part''), touch the corrupted file (i.e.: ''touch ~/.aMule/Temp/002.part*'') and restart [[aMule]].<br>
[[aMule]] will detect the completed chunks and the corrupted ones, and will only download the chunks which got corrupted.