aMule Forum
English => aMule Help => Topic started by: orinoco on March 07, 2006, 02:34:08 PM
-
When I try tu run aMuled I see following thing - how can I prevent aMule from shutdown? Daemon should be still on memory, not exit immediately after start!
debian:~# amuled
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
--------------------------------------------------
Warning! You are running aMule as root.
Doing so is not recommended for security reasons,
and you are advised to run aMule as an normal
user instead.
--------------------------------------------------
Loading temp files from /root/.aMule/Temp.
All PartFiles Loaded.
ListenSocket: Ok.
External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Empty dir /root/.aMule/Incoming shared
(null)
Now, exiting main app...
aMule OnExit: Terminating core.
aMule shutdown completed.
-
Why do you run it as root ?!
-
Ok, log from not doing this as root is quite simmilar :-(
==================================================
amule@debian:~$ amuled
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /home/amule/.aMule/Temp.
All PartFiles Loaded.
ListenSocket: Ok.
External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Empty dir /home/amule/.aMule/Incoming shared
(null)
Now, exiting main app...
aMule OnExit: Terminating core.
aMule shutdown completed.
==================================================
I simply want to start amule daemon and connect to it from Windows remote aMule GUI...
-
you run this with a script? or in console?
1st time you run it?
-
This error appears always - I tried tu run aMuled multiple times. And this log was from console, not from script:
====================================================
amule@debian:~$ amuled
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /home/amule/.aMule/Temp.
All PartFiles Loaded.
ListenSocket: Ok.
External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Empty dir /home/amule/.aMule/Incoming shared
(null)
Now, exiting main app...
aMule OnExit: Terminating core.
aMule shutdown completed.
amule@debian:~$ amuled
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /home/amule/.aMule/Temp.
All PartFiles Loaded.
ListenSocket: Ok.
External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Empty dir /home/amule/.aMule/Incoming shared
(null)
Now, exiting main app...
aMule OnExit: Terminating core.
aMule shutdown completed.
amule@debian:~$
====================================================
If I run aMuled by "amuled -f", aMuled talk:
====================================================
amule@debian:~$ amuled -f
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
amuled: forking to background - see you
amule@debian:~$
====================================================
but no aMuled process is running :/ What is wrong? ".aMule" directory in home directory is always properly generated, etc, but aMuled is immediately exiting. Using Debain Sarge and compiled aMuled and wxwidgets from sources from Debain Backports:
http://backports.org/debian/pool/main/a/amule/amule_2.1.0.orig.tar.gz
http://backports.org/debian/pool/main/w/wxwidgets2.6/wxwidgets2.6_2.6.1.1bpo1.tar.gz
Other versions (not from debian backports, for example original 2.1.0 or from CVS) are simply crashing after startup, I posted detailed REAL BACKTRACE here:
http://forum.amule.org/thread.php?threadid=9322&sid=
-
hey
maybe instead of trying some backports or some strange sources, try our debian-sarge repro first
http://forum.amule.org/thread.php?threadid=8723
lots of people use, it and if you still have a problem there, you install is somewhat brocken, since these pkg are known to work well