aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: amuled stays in memory even after shutting it down  (Read 2258 times)

GrayFox.i0n

  • Full Member
  • ***
  • Karma: 2
  • Offline Offline
  • Posts: 139
amuled stays in memory even after shutting it down
« on: July 10, 2008, 10:39:17 PM »
After a hard day of testing, i logged into the machine that has amuled running......
My way to stop amuled is: First, i enter amulecmd, and once inside the prompt, i type: shutdown...

Amule webserver stops working and i receive the message "Ok, exiting aMulecmd..." and then i return to the bash shell...
What is my surprise when i enter "htop" command and i discover that amuled -f is still running, and if i try to launch amuled again, i get this messages:

Checking if there is an instance already running...
There is an instance of aMule already running
Raising current running instance.

But there is no network activity, and amule seems to be completely hanged up....

¿Need a backtrace?

Cheers! :D
Logged

deva1984

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 1
Re: amuled stays in memory even after shutting it down
« Reply #1 on: July 29, 2008, 06:01:07 PM »
I have met the similar problem.
Amule will crash when it is running, then if I restart amule, i get these:
Initialising aMule
Checking if there is an instance already running...
There is an instance of aMule already running
Raising current running instance.

But as if i typer " ps ax | grep amule", there is no amule processe found.
And i also checked ~/.aMule, there is no "muleLock" file there.
Logged