Difference between revisions of "AMule problems-it"

Revision as of 18:10, 28 April 2007

Quando faccio partire aMule mi esce il messaggio "aMule already running: exiting". Posso farlo partire lo stesso?

Il messaggio è molto chiaro: aMule sta già girando. Ma questo non si riferisce al sistema, significa che tu (il tuo account utente) sta già facendo girare aMule.

Potrebbe sembrare che non ci sia nessuna istanza di aMule in esecuzione, se c'è stato un crash. Ma qualche volta succede che qualche processo non si chiuda totalmente, rimanendo in uno stato chiamato zombi o defunto. Per scoprire se questo è il tuo problema, esegui in un terminale ps u | grep amule e se compare qualche messaggio (a parte quello di grep stesso), allora qualche processo di aMule sta girando a tuo nome. Per ucciderlo, chiudilo normalmente (se puoi) oppure fallo con kill -9 <aMile PID> oppure con killall -9 amule oppure prova ad uscire e rientrare (che nella maggior parte dei casi chiuderà tutti i processi di aMule a meno che tu l'abbia avviato con nohup o simili).

Se sei sicuro che nessun processo di aMule stia girando, controlla se esiste un file muleLock nella tua cartella ~/.aMule e cancellalo per ripristinare il funzionamento normale di aMule.

Se nessuna delle soluzioni è adatta per te, puoi eseguire un'altra istanza di aMule come altro utente (se puoi entrare con un altro nome utente, chiaramente). Leggi [FAQ_aMule#Can_I_run_two_aMule_instances_at_the_same_time?|Can I run two aMule instances at the same time?]].

aMule parte ma non compare la schermata, anche se funziona. Cosa sta succedendo?

Questo succede di solito quando imposti il tipo di integrazione nel vassoio di sistema a Minimizza nel vassoio (da Preferenze -> Generale). Questo fa partire aMule minimizzato.

Per recuperare la schermata di aMule, modifica ~/.aMule/amule.conf e cerca StartupMinimized=1 Cambia questa riga a StartupMinimized=0. Questo script farà il lavoro per te:

sed s/StartupMinimized=1/StartupMinimized=0/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf

Quando farai partire aMule la prossima volta imposta la giusta integrazione nel vassoio dalle Preferenze, per riuscire a minimizzare aMule senza che venga nascosto.

Se per qualche motivo questo metodo non funziona, prova a cambiare l'integrazione nel vassoio manualmente, togliendo la crocetta dall'opzione Abilita icona vassoio. Per farlo, apri ~/.aMule/amule.conf e imposta il valore di DesktopMode= a 4. Questo script farà il lavoro per te:

sed s/DesktopMode=[0-9]/DesktopMode=4/ ~/.aMule/amule.conf > ~/.aMule/amule.conf.temp && mv -f ~/.aMule/amule.conf.temp ~/.aMule/amule.conf

NOTA: Nelle versioni di aMule precedenti a 2.0.0rc4, imposta a 1 invece di 4 perché il file delle preferenze è stato cambiato.

aMule parte ma non si connette/si comporta in modo strano/si blocca ogni pochi secondi/ecc...?

Le versioni di aMule fino alla 2.0.0-rc3 non devono essere linkate ai wxWidgets 2.5.x e neanche al GTK2, anche se qualche distribuzione lo fa. Assicurati che non sia il tuo caso. In caso di incertezza, spedisci il tuo backtrace a aMule's Backtraces forum oppure vai sul canale IRC di aMule #amule at irc.freenode.net

Dove sono i miei file scaricati?

Di default, aMule memorizza i file completati in ~/.aMule/Incoming ma siccome la cartella ~/.aMule è nascosta (inizia con un punto), il tuo file manager potrebbe non visualizzarla. Assicurati di impostare il file manager a visualizzare le cartelle nascoste.

Di default i file in corso di scaricamento sono in ~/.aMule/Temp, per cui anche in questo caso per vederli occorre impostare il file manager.

Perché aMule richiede così tante risorse CPU all'avvio?

aMule sta calcolando gli hash dei nuovi file che ha trovato nelle cartelle condivise.

Se aMule occupa sempre molta CPU anche quando nessun nuovo file è stato aggiunto o modificato nelle cartelle condivise, allora c'è qualcosa che non va.

Nelle versioni di aMule precedenti la 2.0.0-rc3 questo succedeva quando la cartella Temp, Incoming o qualsiasi cartella condivisa era in una partizione FAT32. Ora questo non succede più.

Inoltre nelle versioni di aMule precedenti la 2.0.0-rc4, i filesystem con codifica UTF-8 (per esempio con SUSE 9.1) potrebbero presentare problemi quando qualche file o cartella condivisa contiene un carattere speciale. Se questo è il tuo problema, c'è un rimedio (grazie nachbarnebenan): dopo che aMule ha calcolato gli hash dei file condivisi (cioè quando smette di occupare la CPU) chiudi aMule e codifica ~/.aMule/known.met in UTF-8 (lo puoi fare con recode con il seguente comando: recode u8 ~/.aMule/known.met). Questo va fatto ogni volta che un file viene aggiunto o modificato nelle cartelle condivise. Forse è meglio aggiornare aMule all'ultima versione.

Se niente finora ti ha aiutato, è successo qualcosa al file known.met , forse qualche programma esterno o qualche altro utente lo ha rovinato. E' meglio cancellarlo, far partire aMule e lasciare che ricalcoli tutti gli hash dei file.

Adesso aMule parte, ma mi dice "Nessun server valido nella lista dei server"

Hai abilitato l'opzione "Connetti automaticamente solo ai server statici". Cancella questa opzione oppure metti qualche server nella lista statica.

Per togliere l'opzione, vai a Preferenze -> Server -> Connetti automaticamente solo ai server statici

Per aggiungere un server alla lista statica, vai alla finestra Server e fai clic destro sul server che vuoi aggiungere alla lista. Poi scegli "Aggiungi alla lista statica" e ripeti il procedimento per tutti i server che vuoi mettere nella lista statica.

Perché ogni tanto all'improvviso aMule ha pochi/nessun server nella lista?

Hai probabilmente abilitato le opzioni Preferenze -> Server -> Rimuovi i server dopo X tentativi Preferenze -> Connessione -> Riconnetti dopo perdita connessione

Se è così, hai probabilmente perso la connessione di rete (Internet o LAN) per un periodo di tempo, per cui aMule ha perso la connessione al server ED2K ed ha cercato di connettersi ad altri server fino a quando sono stati tutti cancellati dalla lista (dopo X tentativi ciascuno).

Per risolvere il problema, disabilita l'opzione "Rimuovi i server dopo X tentativi". Disabilitare questa opzione è sicuro nella maggior parte dei casi. Probabilmente non vorrai disabilitare l'altra opzione "Riconnetti dopo perdita" per cui lasciala abilitata.

aMule si connette al server, ma ottiene sempre un ID basso. Perché? Posso farci qualcosa?

Possono esserci tre ragioni:

• Qualche porta necessaria è chiusa nel tuo firewall. Leggi questo e controlla qui se le porte sono aperte.
• Il server è molto occupato o forse mal configurato, per cui ti da un Low-ID. Non puoi fare nient'altro che cercare di riconnetterti o cercare un altro server.
• Alcuni ISP proibiscono l'uso di applicazioni P2P come aMule, non permettendo il traffico tramite le usuali porte P2P. In questi casi, configura aMule per usare qualche altra porta. Sarebbe ancora meglio se fosse una porta usata di solito per qualche altro servizio. Con qualche ISP ha funzionato sulla porta TCP 25600.

aMule si è interrotto mentre completava un file e ora non lo completa mai (anche se è scaricato al 100%). Come lo completo?

Questa è facile: Chiudi aMule. Adesso vai nella cartella Temp (di solito ~/.aMule/Temp) e scrivi questo comando:

touch ./*

Poi fai ripartire aMule e lascialo completare i file.

I just lost a download. Is there any way 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).
Two things may have happened. Either *.part.met files were deleted, or *.part files were deleted.

If *.part files have disappeared, the only solution is to restart the downloads from the beginning (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.

If *.part.met files have disappeared 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:

for file in *.part.met.bak; do mv -f "$file" "${file%.bak}; done

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:

Either, use MetFileRegenerator (Java needed) to reconstruct the *.part.met files.

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 were downloading 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 mysteriously disappeared. 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 suddenly 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 until you click OK, Cancel, or whatever you have to click.

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).

However, on some releases it has happened that after restarting aMule, some files dissapear from the Shared Folders window although 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 will 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.

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 shouldn't worry about them.

What should I do if I lose my cryptkey.dat file?

Losing this files means you lose all of your credits. Sorry. Since you'll need to start building credits up again, you'll need to delete ~/.aMule/preferences.dat or you'll not be able to collect credits on clients who have previously identified you (prior to losing cryptkey.dat).

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 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 bandwidth 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.

So, the maximum speed allowed per slot is BandwidthLimit/3.

Please do NOT confuse Bandwidth limit with Bandwidth Capacity. Read 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.

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.

Example:

• 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 there are no more 2KBps left, since the limit is 7 KBps, but there is still 1 KBps left in the bandwidth before reaching the Bandwidth Limit. So, it will allow another slot to upload to a client and, instead of giving that last slot a 1 KBps bandwidth connection (and leave the rest with a 2 KBps bandwidth connection), 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:

• From 0KBps to 3KBps:
• DownloadLimit can't be more than UploadLimit*3
• From 4KBps to 9KBps:
• DownloadLimit can't be more than UploadLimit*4
• UploadLimit values over 9KBps:
• There's no DownloadLimit limitation.

Be careful when setting 0KBps as Upload Limit. It might not mean what you think it is. Read I set Upload Limit to 0KBps, but aMule is still transferring. What did I do wrong? to make sure you understand it's meaning.

I set Upload Limit to 0KBps, but aMule is still transferring. What did I do wrong?

Setting Upload limit to 0KBps will not stop transfers, instead, 0 value means unlimited, so, it's right the opposite 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.

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).

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 editing 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):

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?

In most aMule versions setting the progress bar style to the most right on Preferences -> "GUI tweaks" is the way to have the progress bar have the best 3D effect. But in versions 2.0.0-rc4 to 2.0.0-rc6 the best 3D effect is given when the style bar is set to the middle. Setting it to the most right would 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 part of a file.

Why can't I preview a file?

First of all you must know that aMule only allows to preview video files.

To be able to preview a file aMule requires two things:

• The file must have a known video extension in its filename
• You must have downloaded the first 256KBs of the file

Anyway, sometimes it happens that the file is previewable though aMule doesn't allow you. In that case, go to the Temp directory and preview them manually, if you can and wish.

Why isn't aMule's Preview working at all with MPlayer?

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.:

xterm -T "aMule 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.

Please read 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. although this is already checked while downloading (by checking the chunk's hash values), once the file is completely 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 on the icon of the directory you want to recursively select.
• On aMule 1.x and up to 2.0.0-rc3 (included), while clicking on the directory, hold the CTRL key.

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, 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.

aMule will detect the completed chunks and the corrupted ones, and will only download the chunks which got corrupted.

What should I be aware of when using NFS mounts with aMule?

When using NFS mounts with aMule, make sure you unmount those NFS mounts (the ones from the computer being shut down) from the computer running aMule because, otherwise, aMule will simply hang until those mounts are back up again. How to notice this? If you leave aMule running at night, and on the next day you go to the stats and see straight lines for Download/Upload/Connections stats (non-zero) and after mounting those NFS mounts, those straight lines drop to zero resuming normal behaviour, that is a sign. Plus, after unmouting the NFS mounts from any computer being shut down, reload aMule's shared files.

I noticed all this from my frustrating experience of countless days with no downloads at night ;) ... --PedroAlgarvio 00:25, 15 Jun 2005 (CEST)

Downloaded files don't get the permissions I set in Preferences. Why?

aMule must follow the permissions it is allowed to set by umask. umask sets the permissions which applications should not be allowed to assign files.

Therefore, if you set, for example, file permissions to 664 in aMule's Preferences, and umask's value (check it by running umask) is 022, aMule will create files with permissions 644 (that is, 664 - 022 = 644).

aMule fails to create files/shows file descriptor errors. What's going on?

This should never happen. If it happens chances are you have the resources limits very low, so aMule is denied to create/open new files. Run ulimit -a to check your resources limits. Read man ulimit to learn how to set the limits as you want them, and remember that this has to be set on every system restart (probably your distribution provides a configuration file which sets this automatically).