aMule Forum
English => en_Bugs => Topic started by: Fiesch on June 25, 2006, 05:15:07 PM
-
Hi.
got this bug after merging two of my linux boxes into a hdd server.
I created an idential p2p user as on the original system (where aMule kept running like a charm (aside from the web interface crashing from time to time) and moved all of the relevant files over, trying to run with gentoo-init-scripts yielded nothing (not even logfile output), running it as the p2p user gives this error report:
~/aMule $ amuled
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Invalid category found, skipping
aMule Version: aMuled 2.1.3 using wxGTK2 v2.6.3 (Unicoded)
Terminated after throwing an instance of 'CInvalidStateEx'
what(): CRunTimeException::CInvalidStateException: CFile: Cannot get length of closed file.
backtrace:
[2] ?? in amuled [0x80645bd]
[3] wxEntry(int&, wchar_t**) in /usr/lib/libwx_baseu-2.6.so.0[0xb7d9c64d]
[4] wxEntry(int&, char**) in /usr/lib/libwx_baseu-2.6.so.0[0xb7d9c6f6]
[5] __gxx_personality_v0 in amuled[0x8053fce]
[6] __libc_start_main in /lib/libc.so.6[0xb7ae83c3]
[7] wxAppConsole::Initialize(int&, wchar_t**) in amuled[0x8053ee1]
Abgebrochen
a wild guess would be that sth went wrong copying the files but i honestly can't think of a specific thing that might have happened there....
anyway the amuled crashing with an exception seems to be a bug, maybe i just created a weird scenario by accident nobody tried before.
-
Yes you did. Can you get a proper backtrace?
-
(gdb) run
Starting program: /usr/bin/amuled
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 26667)]
amuled: OnInit - starting timer
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
Invalid category found, skipping
aMule Version: aMuled 2.1.3 using wxGTK2 v2.6.3 (Unicoded)
Terminated after throwing an instance of 'CInvalidStateEx'
what(): CRunTimeException::CInvalidStateException: CFile: Cannot get length of closed file.
backtrace:
[2] CamuleApp::OnUnhandledException() in amule.cpp:1993
[3] wxEntry(int&, wchar_t**) in /usr/lib/libwx_baseu-2.6.so.0[0xb7d4964d]
[4] wxEntry(int&, char**) in /usr/lib/libwx_baseu-2.6.so.0[0xb7d496f6]
[5] __gxx_personality_v0 in amuled.cpp:132
[6] __libc_start_main in /lib/libc.so.6[0xb7a953c3]
[7] wxAppConsole::Initialize(int&, wchar_t**) in :0
Program received signal SIGABRT, Aborted.
[Switching to Thread 16384 (LWP 26667)]
0xb7aa89d1 in kill () from /lib/libc.so.6
That's all i could fiddle out of it.. lemme know if you need more info than that
-
last lines on ~/.aMule/logfile ?
-
ah.. first time since the merge that sth is actually in there...
2006-06-25 20:14:11: CFile: Error when opening file (/home/p2p/.aMule/clients.met.BAK): Keine Berechtigung
(translates to insufficent rights)
looks like the groupids got messed up when moving the files..
still that shouldn't crash amuled...
-
Nope. can you change it and see if it stops crashing?
-
yup does, have it up and running again.. btw amulegui stays in mem if you try to connect to a non-existent amuled
-
k, gonna look into permisions xheck. thanks.