aMule Forum

English => aMule Help => Topic started by: atorobot on August 07, 2008, 11:07:35 PM

Title: Amuled locked by ghost instance
Post by: atorobot on August 07, 2008, 11:07:35 PM

hi guys!
I have the famous problem of  "another instance already running" after a crash by my pc... but... i don't have any mulelock file, or .lock or .pid file locking amuled in "/home/{username}/.aMule/" directory.
It starts whitout problems as root, but i'm not able to let it starts as user.
I'm using Slackware and the pre-compiled 2.2.1 from slacky.eu.
any ideas?
thanks for your effort

Title: Re: Amuled locked by ghost instance
Post by: wuischke on August 08, 2008, 11:22:03 AM

If you move the .aMule directory to .aMule-old, does the problem persist as user?

Title: Re: Amuled locked by ghost instance
Post by: Vollstrecker on August 08, 2008, 12:02:52 PM

For me it's helpful to remove .aMule/ED2KLinks_lock

Title: Re: Amuled locked by ghost instance
Post by: atorobot on August 08, 2008, 12:06:02 PM

yes, the problem is the same.  i even tried to move /home/{user}/.aMule to /home/{user}/amuleold and copy /root/.aMule to /home/{user}/.aMule  (changing group and owner of course)... nothing to do... the same error...
it seems like amule is lookin to a lock file somewhere that i can't find...

i even removed ED2KLinks_lock...

Title: Re: Amuled locked by ghost instance
Post by: wuischke on August 08, 2008, 12:19:09 PM

Are you by chance very low on disk space and use a file system like ext3?