aMule problem

[hermouche]

Hy,

I've used aMule for almost 10 days now.
Last time, i couldn't run it, it says:

[red@ibm ~]$ amule
Initialising aMule
Checking if there is an instance already running...
There seems to be an instance of aMule already running
If this is not the case, you may have to remove
the file ~/.aMule/muleLock, to allow aMule to run.
Attempting to raise current running instance.
[red@ibm ~]$

So i checked for the file ~/.aMule/muleLock . It doen't exist, what can i do in orther to get aMule back !!


When i run it in GUI type , nothing happen!!!!
Thanks

red

[Dangermouse]

Personally id remove it and then reinstall it, might help.

[hermouche]

Originally Posted by Dangermouse

Personally id remove it and then reinstall it, might help.

Thanks for the reply Dangermouse,

I've got some files which are at more than 80%, so what happen to them if i reinstall it?

red

[Dangermouse]

Id wait till their finished is, probably the safest answer. even though you have no gui, you should still know when their done, by looking in your amule download folder.
Btw did you set amule to start when you login?

[FriedChips]

okay try this

su
yum install htop

(if you don't already have it)

then press ctrl+alt+F1, login as root, and type htop. Look for the amule process if there is one. Use the sortby User to bring "your" processes to the top cuz it's a pretty long list. If/when you find it hit F9 then select signal kill (#9). Then press ctrl+alt+F7 to get back to you gui and try to launch it again.

[hermouche]

Originally Posted by FriedChips

okay try this

su
yum install htop

(if you don't already have it)

then press ctrl+alt+F1, login as root, and type htop. Look for the amule process if there is one. Use the sortby User to bring "your" processes to the top cuz it's a pretty long list. If/when you find it hit F9 then select signal kill (#9). Then press ctrl+alt+F7 to get back to you gui and try to launch it again.

Thanks a lot DangerMouse for your reply.
Thanks a lot FriedChips, i've already done : ps -ax and nothing was apparent!!!!!! it's almost the same as the top command as you said, anyway, the problem is solved actually.


In fact there was not anymore space in my HDD, that's why they were no response!!!

Another thing according to aMule web site, it says when ever you have such a problem, remove all
" *.dat, *.met, *.ini " files. You should not remove your files from the Temp folder.

Just after you should be able to start aMule again and configure it at your will.

Thanks again;

red

[hermouche]

Originally Posted by FriedChips

okay try this

su
yum install htop

(if you don't already have it)

then press ctrl+alt+F1, login as root, and type htop. Look for the amule process if there is one. Use the sortby User to bring "your" processes to the top cuz it's a pretty long list. If/when you find it hit F9 then select signal kill (#9). Then press ctrl+alt+F7 to get back to you gui and try to launch it again.

Hy again FriedChips,

I thought that the top command came from : procps-3.2.7-16.fc7
Description:
The procps package contains a set of system utilities that provide system information. Procps includes ps, free, skill, pkill, pgrep, snice, tload, top, uptime, vmstat, w, watch and pdwx.

[root@ibm ~]# rpm -qf /usr/bin/top
procps-3.2.7-16.fc7

So you said htop, first time i heard about it.

Ok, Thanks
red