aMule Forum
English => aMule crashes => Topic started by: atash_000 on April 03, 2005, 07:22:34 PM
-
hi all agian :((
amuled after about 2/3 days of being up, on the last hours of his/her[!] life had a significant increse in downloading. for instance it was downloading 50kB/s now it is less than 0.9kB/s !
after i tried to connect to edonkey server 1 instead of razorback 2 (which i thought might help my old donkey wake up) just killed the amuled and only left the amuleweb processes running!
for godz sake ! for the donkies running in heaven :D ... can anyone help me figure this out !
i don't know why there is no back trace availabe when i run bt , bt full.
there is something to mention too.
i have disabled udp (as mentioned in wiki) and i have set max connections to 1000 , which is FULL !!!
i am using aMule-CVS-20050331
THANKS in advance ,
AGAIN , if there is SOMETHING wrong with the way i present my problems (crashes!) w/ amule , just let me know to correct them out !
here goes the OOOOOOOOOOPZ!
-----------------------------------
aMule version is: CVS using wxGTK2 v2.5.3 (Snapshot: Thu Mar 31 07:01:23 CEST 2005)
Running on: Linux 2.6.10-ck5 i686
- ?? in /usr/local/bin/amuled [0x80fda49]
[1] ?? in /usr/local/bin/amuled
[0x805e208]
[2] wxFatalSignalHandler in /usr/local/lib/libwx_base-2.5.so.3[0xb7f4fb36]
[3] ?? in /lib/libpthread.so.0 [0xb7f90be5]
[4] ?? in /lib/libc.so.6 [0xb7acd078]
[5] wxSocketBase::_Wait(long, long, int) in /usr/local/lib/libwx_base_net-2.5.so.3[0xb7e43a83]
[6] wxSocketBase::WaitForLost(long, long) in /usr/local/lib/libwx_base_net-2.5.so.3[0xb7e43c04]
[7] ?? in /usr/local/bin/amuled [0x814b051]
[8] wxThreadInternal::PthreadStart(wxThread*) in /usr/local/lib/libwx_base-2.5.so.3[0xb7f464af]
[9] wxPthreadStart in /usr/local/lib/libwx_base-2.5.so.3[0xb7f4637c]
[10] ?? in /lib/libpthread.so.0 [0xb7f8acc4]
[11] __clone in /lib/libc.so.6[0xb7b80037]
--------------------------------------------------------------------------------
Program terminated with signal SIGKILL, Killed.
The program no longer exists.
(gdb) ECSocket::WriteBufferToSocket error The socket is non-blocking and the operation would block
ECSocket::WriteBufferToSocket error The socket is non-blocking and the operation would block
ECSocket::WriteBufferToSocket error The socket is non-blocking and the operation would block
ECSocket::WriteBufferToSocket error The socket is non-blocking and the operation would block
ECSocket::WriteBufferToSocket error The socket is non-blocking and the operation would block
ECSocket::WriteBufferToSocket error The socket is non-blocking and the operation would block
ECSocket::WriteBufferToSocket error The socket is non-blocking and the operation would block
ECSocket::WriteBufferToSocket error The socket is non-blocking and the operation would block
(gdb) bt
No stack.
(gdb) bt full
No stack.
(gdb)
-
I don't see any problem in trace you posted. Mind, that in contrary of amule, daemon uses several threads. So, if it doesn't crashed, you can easy take a wrong one. Also, amule(d) wasn't compiled with debug info.
-
i have compiled with the following options:
./configure --enable-amulecmd --enable-webserver --disable-monolithic --enable-amule-daemon --enable-debug --disable-optimise
something missing !
tnX
-
optionss looks ok, but those not:
[0] ?? in /usr/local/bin/amuled [0x80fda49]
[1] ?? in /usr/local/bin/amuled [0x805e208]
-
don't u think . maybe the so many active connections are making the amuled die ? (1000)
i'm really confused why i should sit and w8 for my amule die !
is there anything else that i can provide to help ?
tnx
-
atash_000,
You are probably not running the program you think you are running. Type
$ which amuled
And post the result here. Maybe you have aMule installed in two different directories?
Cheers!
-
root@baghali:~# which amuled
/usr/local/bin/amuled
root@baghali:~#
that's it !
-
don't u think . maybe the so many active connections are making the amuled die ? (1000)
This is too match. amuled have limit of 1024 of all used sockets, so 1000 of active connection can easy hit this limit.
Now, I don't see any messages from "dying amule". Your trace is from normally running program.
-
Originally posted by atash_000
root@baghali:~# which amuled
/usr/local/bin/amuled
root@baghali:~#
that's it !
Well, there is something strange, how can a program compiled with debug info do not show debug info? ?(
Cheers!
-
Could this be related to this? --> http://forum.amule.org/thread.php?threadid=5545&sid=
And about that, lfroen, did you find the ethereal lo I send you any useful?
-
tnx for ur replies .
i am going to recompile the whole amule to make sure about the debug info.
btw, is there a suggested number of concurent files to be put for download!
i mean can so many of files make amuled die ?!
tnx again/
-
i mean can so many of files make amuled die ?!
You seem to messing up 2 things "num of files in queue" and "num of connections". You can have as many files in queue as you like. But, maximum number of connections in amuled can not exceed 1000. I would recommend to set it about 700.
BeFalou: your trace looks ok. Do you still have this problem ?
-
actualy i am aware of the max num of connections ;) and the number of files downloading ;)
i was just talking about both of them :D
in fact the same problem has not occured again. but i don't remember that i have ever had amuled runing for more than 2 continious days!!
it crashes, or stops functioning ,
anyway this is the two last crashes
i promise i will send better trace backs in future ....
tnx for ur attention
--------------------
CServerSocket: destroying socket 0x86aa3e0
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 98311 (LWP 4189)]
0x401d103c in GSocket::Select () from /usr/local/lib/libwx_base_net-2.5.so.3
(gdb) ECSocket::ReadBufferFromSocket error The socket is non-blocking and the operation would block
ECSocket::WriteBufferToSocket error The socket is non-blocking and the operation would block
ECSocket::WriteBufferToSocket error The socket is non-blocking and the operation would block
ECSocket::WriteBufferToSocket error The socket is non-blocking and the operation would block
ECSocket::WriteBufferToSocket error The socket is non-blocking and the operation would block
(gdb) bt full
#0 0x401d103c in GSocket::Select ()
from /usr/local/lib/libwx_base_net-2.5.so.3
No symbol table info available.
#1 0x401cca83 in wxSocketBase::_Wait ()
from /usr/local/lib/libwx_base_net-2.5.so.3
No symbol table info available.
#2 0x401ccc04 in wxSocketBase::WaitForLost ()
from /usr/local/lib/libwx_base_net-2.5.so.3
No symbol table info available.
#3 0x0814ca01 in CServerSocketHandler::Entry (this=0x86aa538)
at ServerSocket.cpp:140
No locals.
#4 0x401724af in wxThreadInternal::PthreadStart ()
from /usr/local/lib/libwx_base-2.5.so.3
No symbol table info available.
#5 0x4017237c in wxPthreadStart () from /usr/local/lib/libwx_base-2.5.so.3
No symbol table info available.
#6 0x4003154e in pthread_start_thread () from /lib/libpthread.so.0
No symbol table info available.
#7 0x400315df in pthread_start_thread_event () from /lib/libpthread.so.0
No symbol table info available.
#8 0x4051ab8a in clone () from /lib/libc.so.6
No symbol table info available.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
aMule version is: CVS using wxGTK2 v2.5.3 (Snapshot: Thu Mar 31 07:01:23 CEST 2005)
Running on: Linux 2.6.10-ck5 i686
- ?? in amuled [0x80fda49]
[1] ?? in amuled
[0x805e208]
[2] wxFatalSignalHandler in /usr/local/lib/libwx_base-2.5.so.3[0xb7f4eb36]
[3] ?? in /lib/libpthread.so.0 [0xb7f90c85]
[4] ?? in [0xffffe420]
[5] ?? in amuled [0x80eb5db]
[6] ?? in amuled [0x80f3dba]
[7] ?? in amuled [0x80c584b]
[8] ?? in amuled [0x80f3471]
[9] ?? in amuled [0x80c5922]
[10] ?? in amuled [0x806e10a]
[11] ?? in amuled [0x8116cce]
[12] ?? in amuled [0x80980ac]
[13] ?? in amuled [0x805e94f]
[14] ?? in amuled [0x8062eb3]
[15] wxEntry(int&, char**) in /usr/local/lib/libwx_base-2.5.so.3[0xb7eeee41]
[16] ?? in amuled [0x8062a31]
[17] __libc_start_main in /lib/libc.so.6[0xb7ac9469]
[18] ?? in amuled [0x8053521]
--------------------------------------------------------------------------------
Aborted
-
0x401d103c in GSocket::Select () from /usr/local/lib/libwx_base_net-2.5.so.3
That is exactly what I mean: you have too many sockets. Decrease number of connections.
-
tnx ifroen
i decreased the max connections from 1000 to 700
let's see what happens
-
after 3 days, my amule crashed ,
i set my max connections to 700, and i think it was reached for several times ! but is it a good reason for crash!?:D
Do you have any idea?
THANKS IN ADVANCE
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
aMule version is: CVS using wxGTK2 v2.5.3 (Snapshot: Tue Apr 5 07:01:23 CEST 2005)
Running on: Linux 2.6.10-ck5 i686
- ?? in /usr/local/bin/amuled [0x80ffbc1]
[1] ?? in /usr/local/bin/amuled
[0x805e796]
[2] wxFatalSignalHandler in /usr/local/lib/libwx_base-2.5.so.3[0x4017cb36]
[3] ?? in /lib/libpthread.so.0 [0x40037c85]
[4] ?? in [0xffffe420]
[5] ?? in /usr/local/bin/amuled [0x80f37c2]
[6] ?? in /usr/local/bin/amuled [0x80f603f]
[7] ?? in /usr/local/bin/amuled [0x80c794f]
[8] ?? in /usr/local/bin/amuled [0x80f55e9]
[9] ?? in /usr/local/bin/amuled [0x80c7a26]
[10] ?? in /usr/local/bin/amuled [0x806ef88]
[11] ?? in /usr/local/bin/amuled [0x81183da]
[12] ?? in /usr/local/bin/amuled [0x809915c]
[13] ?? in /usr/local/bin/amuled [0x805ef7b]
[14] ?? in /usr/local/bin/amuled [0x8063997]
[15] wxEntry(int&, char**) in /usr/local/lib/libwx_base-2.5.so.3[0x4011ce41]
[16] ?? in /usr/local/bin/amuled [0x8063515]
[17] __libc_start_main in /lib/libc.so.6[0x40477469]
[18] ?? in /usr/local/bin/amuled [0x8053501]
--------------------------------------------------------------------------------
Aborted
-
hi all again,
after 2 days again,
i have no dl !!
my connections are at max. 700
it seems that when amuled reaches the max connections and the connections don't fall down,
the downloading stops !
here is the statistics ..
any idea ?
tnx
aMule vCVS Statistics [http://www.aMule.org]
Statistics
Uptime: 2 Days 00 hours
Transfer
Session UL:DL Ratio (Total): 1 : 4.23
Uploads
Uploaded Data (Session (Total)): 892.49 MB (892.49 MB)
Total Overhead (Packets): 83.65 MB (1.36M)
File Request Overhead (Packets): 23.81 MB (748K)
Source Exchange Overhead (Packets): 14.68 MB (21K)
Server Overhead (Packets): 740 KB (32K)
Current Uploads: 5
Waiting Uploads: 92
Total successful uploads: 3521
Total failed uploads: 356
Average upload time: 2:32 mins
Downloads
Downloaded Data (Session (Total)): 3.69 GB (3.69 GB)
eMule: 3.42 GB
aMule: 67.39 MB
eDonkey: 0 Bytes
eDonkeyHybrid: 57.47 MB
Shareaza: 91.49 MB
MLDonkey: 40.35 MB
(l/x)Mule: 11 KB
Other: 13.92 MB
Total Overhead (Packets): 82.03 MB (1.38M)
File Request Overhead (Packets): 27.91 MB (597K)
Source Exchange Overhead (Packets): 19.12 MB (31K)
Server Overhead (Packets): 421 KB (6K)
Found sources: 6202
Current downloads (chunks): 0
Connection
Average download rate (session): 21.97 kB/s
Average upload rate (session): 5.19 kB/s
Max download rate average (session): 34.74 kB/s
Max download rate (session): 92.31 kB/s
Reconnects: 4
Time since initial transfer: 2 Days 00 hours
Connected to server since: 18:56 mins
Active Connections (estimate): 701
Max Connection Limit Reached: 11150 : 2005-04-18 10:04:58
Average Connections (estimate): 700.736145
Peak Connections (estimate): 726
Clients
Total: 6310 Known: 3734
eMule: 3536 (94.7%)
v0.45b: 1849 (52.3%)
v0.45a: 60 (1.7%)
v0.44d: 598 (16.9%)
v0.44c: 4 (0.1%)
aMule: 28 (0.7%)
Version
v2.0.0: 27 (96.4%)
v1.x: 1 (3.6%)
Operative System
Linux: 7 (25.0%)
Not Received: 21 (75.0%)
lMule/xMule: 0 (0.0%)
eDonkeyHybrid: 96 (2.6%)
v1.0.0: 30 (31.2%)
v0.53.0: 12 (12.5%)
v0.52.0: 3 (3.1%)
v0.50.1: 2 (2.1%)
eDonkey: 0 (0.0%)
cDonkey: 0 (0.0%)
Old MLDonkey: 0 (0.0%)
New MLDonkey: 13 (0.3%)
Shareaza: 54 (1.4%)
lphant: 7 (0.2%)
Compatible: 0 (0.0%)
Unknown: 2576
LowID: 789 (12.50% Total 18.48% Known)
SecIdent On/Off: 3402 (95.45%) : 111 (3.11%)
HasSocket: 275 (4.4%)
Filtered: 0
Servers
Working servers: 87
Failed servers: 1197
Total: 1284
Deleted servers: 0
Users on function servers: 3808477
Files on functioning servers: 425617461
Total users: 4873027
Total files: 653768032
Server occupation: 10.69%
Shared Files
Number of shared files: 80
Collective size of shared files: 37.73 GB
Average file size: 482.98 MB