aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Cannot start amuled - now with current CVS code  (Read 1750 times)

orinoco

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 14
Cannot start amuled - now with current CVS code
« on: March 10, 2006, 09:55:47 PM »

I compiled aMuled from CVS 10-03-2006. Configure options:

debian:~/amule-cvs# ./configure --enable-amulecmd --enable-webserver --disable-monolithic --enable-amule-daemon --enable-debug --disable-optimize --disable-amule-gui

After running first time there was:

======================================================================================================
temp@debian:~$ amuled --only-chuck-norris-would-stop-me
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
BĹÄ
   D: Informacje  --- Po raz pierwszy uruchomiĹeĹMule CVS ---

Ta wersja jest wersjÄ
 testowÄ
, aktualizowanÄ
 codziennie i
nie dajemy gwarancji, Ĺźe to nie zniszczy niczego, spali twojego domu,
lub zabije twego psa. Ale *powinna* mimowszystko dziaĹaÄ poprawnie.

WiÄcej informacji, pomoc i nowe wydania znajdziesz na naszej stronie,
http://www.aMule.org, lub na naszym kanele IRC #aMule irc.freenode.net.

Nie krÄpuj siÄ, zgĹaszaj jakiekolwiek bĹÄdy na http://forum.amule.org
Loading temp files from /home/temp/.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/temp/.aMule/Incoming shared

(null)

Now, exiting main app...
aMule OnExit: Terminating core.
aMule shutdown completed.
temp@debian:~$
======================================================================================================


Amuled as you saw exits without any reason! So I started amuled second time. And amuled exits without any reason second time!


======================================================================================================
temp@debian:~$ amuled --only-chuck-norris-would-stop-me
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Loading temp files from /home/temp/.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/temp/.aMule/Incoming shared

(null)

Now, exiting main app...
aMule OnExit: Terminating core.
aMule shutdown completed.
temp@debian:~$
======================================================================================================

So I started amuled with "-o" switch to see all logs:


======================================================================================================
temp@debian:~$ amuled -o --only-chuck-norris-would-stop-me
amuled: OnInit - starting timer
Logging to stdout enabled
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
(null)2006-03-10 20:49:12: Otwieram plik server.met: /home/temp/.aMule/server.met
2006-03-10 20:49:12: 0 serwerów znaleziono w server.met
Loading temp files from /home/temp/.aMule/Temp.

All PartFiles Loaded.
(null)(null)2006-03-10 20:49:12: MuleUDPSocket: Created Server UDP-Socket at port 4665
ListenSocket: Ok.
2006-03-10 20:49:12: MuleUDPSocket: Created Client UDP-Socket at port 4672

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/temp/.aMule/Incoming shared
(null)(null)(null)2006-03-10 20:49:12: Wczytaj 0 kontaktów Kad
2006-03-10 20:49:12: Loading IP-filters 'ipfilter.dat' and 'ipfilter_static.dat'.
(null)(null)2006-03-10 20:49:12: ThreadScheduler: Completed task 'Load IPFilter', 1 tasks remaining.
2006-03-10 20:49:12: ThreadScheduler: Completed task 'AICH Syncronizing', 0 tasks remaining.
2006-03-10 20:49:12: General: CamuleDaemonApp::OnRun()
(null)
(null)

2006-03-10 20:49:12: MuleUDPSocket: Shutting down Client UDP-Socket
Now, exiting main app...
aMule OnExit: Terminating core.
2006-03-10 20:49:12: MuleUDPSocket: Shutting down Server UDP-Socket
aMule shutdown completed.
temp@debian:~$
======================================================================================================

And now I suspected crash, so I did real backtrace - but now error was found:

======================================================================================================
(gdb) ha SIGPIPE nostop noprint pass
Signal        Stop      Print   Pass to program Description
SIGPIPE       No        No      Yes             Broken pipe
(gdb) ha SIG32 nostop noprint pass
Signal        Stop      Print   Pass to program Description
SIG32         No        No      Yes             Real-time event 32
(gdb) ha SIG33 nostop noprint pass
Signal        Stop      Print   Pass to program Description
SIG33         No        No      Yes             Real-time event 33
(gdb) ha SIG34 nostop noprint pass
Signal        Stop      Print   Pass to program Description
SIG34         No        No      Yes             Real-time event 34
(gdb) run --only-chuck-norris-would-stop-me
Starting program: /usr/local/bin/amuled --only-chuck-norris-would-stop-me
[Thread debugging using libthread_db enabled]
[New Thread -1213362048 (LWP 6484)]
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
[New Thread -1213731920 (LWP 6490)]
Loading temp files from /home/temp/.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/temp/.aMule/Incoming shared
[New Thread -1222120528 (LWP 6491)]
[New Thread -1230509136 (LWP 6492)]

(null)

[Thread -1222120528 (zombie) exited]
[Thread -1213731920 (zombie) exited]
[Thread -1230509136 (zombie) exited]
Now, exiting main app...
aMule OnExit: Terminating core.
aMule shutdown completed.

Program exited normally.
(gdb) bt
No stack.
(gdb) bt full
No stack.
(gdb) thread apply all bt
(gdb)
======================================================================================================

So, what is the problem? Why amuled is exiting? This problem is with all (stable/cvs) versions of amule using all (2.6.x/2.7) version of wxwidgets.

How can I run amuled to avoid exiting? OS: Debian Sarge.

PS.: I could not install amuled from debian packages, because debian packages REQUIRES to install all wxwidgets (not only wxbase) and full wxwidgets packages reuirex X server installed. I have got only console debian, without any X and I don't want to install X - I would like to simply run amuled. Why amuled is exiting after start?
Logged

orinoco

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 14
Re: Cannot start amuled - now with current CVS code
« Reply #1 on: March 10, 2006, 11:25:13 PM »

OK, I forgot to enable external connections :) Now everything works, thanks :)
Logged