aMule Forum
English => Backtraces => Topic started by: djtm on February 05, 2005, 10:49:47 AM
-
amuled crashed.
the lines below mean "operation not permitted" and "couldn't create backup"
22:36:25: Error: Kann Berechtigungen für Datei '/home/djtm/Tempz/002.part.met.bak' nicht festlegen (error 1: Die Operation ist nicht erlaubt)
22:36:25: Error: Info: Konnte den Backup für '/home/djtm/Tempz/002.part.met' nicht erstellen
(error 1: Die Operation ist nicht erlaubt)
CClientReqSocketHandler: thread -1410335824 for 0x8ac2628 exited
CClientReqSocketHandler: thread -1552942160 for 0x88ada28 exited
22:36:49: Error: Kann Berechtigungen für Datei '/home/djtm/Tempz/006.part.met.backup' nicht festlegen (error 1: Die Operation ist nicht erlaubt)
22:36:49: Error: Info: Konnte den Backup für '/home/djtm/Tempz/006.part.met' nicht erstellen
(error 1: Die Operation ist nicht erlaubt)
22:36:49: Error: Kann Berechtigungen für Datei '/home/djtm/Tempz/006.part.met.bak' nicht festlegen (error 1: Die Operation ist nicht erlaubt)
22:36:49: Error: Info: Konnte den Backup für '/home/djtm/Tempz/006.part.met' nicht erstellen
(error 1: Die Operation ist nicht erlaubt)
--------------------------------------------------------------------------------
Oops, aMule crashed!
Hey, stop crying! You wanted the edge, and now you fell down?!
Please, post the following lines, on the aMule Crashes forum on: http://forum.amule.org/board.php?boardid=67&sid=/
You should also try to generate a real backtrace of this error, please read:
http://www.amule.org/wiki/index.php/Backtraces
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
aMule version is: CVS using wxGTK2 v2.5.3 (Unicoded) (Snapshot: Wed Feb 2 07:01:04 CET 2005)
- CamuleApp::OnFatalException() in amuled [0x812cd62]
[1] wxFatalSignalHandler in /usr/lib/libwx_baseu-2.5.so.3
[0xb7f5b5e8]
[2] ?? in [0xffffe420]
[3] CDownloadQueue::GetDownloadClientByIP(unsigned int) in amuled [0x80a7b7c]
[4] CClientUDPSocket::ProcessPacket(char*, unsigned short, unsigned char, unsigned int, unsigned short) in amuled [0x80994ff]
[5] CClientUDPSocket::OnReceive(int) in amuled [0x8098c65]
[6] CClientUDPSocket::Entry() in amuled [0x8099c19]
[7] wxThreadInternal::PthreadStart(wxThread*) in /usr/lib/libwx_baseu-2.5.so.3[0xb7f51bfb]
[8] wxPthreadStart in /usr/lib/libwx_baseu-2.5.so.3[0xb7f51acf]
[9] ?? in /lib/tls/libpthread.so.0 [0xb7fc8b63]
[10] __clone in /lib/tls/libc.so.6[0xb7b31c4a]
--------------------------------------------------------------------------------
Abgebrochen (core dumped)
-
1) lack of diskspace?
2) fs remounted read-only because of failure? check kernel logs
-
the permissions seam wrong, but of course amule should not crash....
but as always this backtrace is not really helpfull ;)
we need gdb backtraces, and amule compiled with enable-debug...so when this is reproducible, please provide a gdb backtrace :)
thnx,
if you need help, check http://wiki.amule.org
stefanero
-
I'm sure the space is not the problem(20+GB free, fat32), however amuled seems to crash every couple hours.
Gladly I have a script running that makes this situation unproblematic.
I will post more backtraces and gdb backtraces as I get a chance.
-
well for amule-daemon you should make some things sure
1st. max connections is lower then 1024
2nd. disabled udp-socket in prefs, there is still an error in there, which makes it crash
stefanero
-
oh, okay. ill do that too then. good to know...
b.t.w. are core dumps as good as a gdb backtrace?
because it automatically generates core dumps. (core.*)
-
no ;)
gdb rules :) so please if you provide backtraces we LOVE ;) gdb backtraces...
-
what i meant is whether bt full from a coredump is as good as from run-in-gdb
A.
gdb run amuled
*crash*
bt full
B.
amuled
*crash*
gdm /usr/local/bin/amuled core.12345
bt full
is there a difference as far as what they do.
because the second is of course much better to run amule without supervision on my server...
-
djtm,
Most of the time, the results are the same, but sometimes only A produces something. It depends on the crash.
Cheers!
-
By the way: the problem seems to have been:
A. the path was not directly given, but I gave aMule a link from a ext3 partition to a fat32 one, which aMule coulnd't detect.
B. the compiler flags included --ffast-math, which caused a crash around every 8 hours.
When compiling with safe flags (-04 -march=athlon) the problem disappeared.
Sorry for wasting your time!
-
Nah, it is never a waste of time. You are wellcome! :)