Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[sirius]

Hi, got a quite recent CVS build, should be the equivalent to a 2.0.2 amule.

This uild fixed the problem that amuled would not download anything (but amule would), but now it's blocking my machine after a while.

It's running on a Gentoo machine as amule daemon and quickly gains more and more cpu load the longer it runs .... starting with aprox. 10% ... after a few hours up to 50% and then after aprox a day up to 100% load.

But I have no idea on where the problem would be ....

This is some info, maybe it helps:

oh, by the way, the amuled log is empty and syslog too, so no info there.

Code: [Select]

# amuled -v
amuled: OnInit - starting timer
aMule Daemon CVS using wxGTK2 v2.6.0 (Snapshot: Fri Jun  3 07:01:24 CEST 2005) (OS: Linux)

#top
top - 01:31:44 up 2 days, 22:57,  4 users,  load average: 1.07, 1.05, 0.97
Tasks:  97 total,   2 running,  93 sleeping,   0 stopped,   2 zombie
Cpu(s): 31.3% us, 67.7% sy,  0.0% ni,  0.0% id,  0.7% wa,  0.0% hi,  0.3% si
Mem:    514588k total,   508916k used,     5672k free,    38220k buffers
Swap:   257032k total,        0k used,   257032k free,   265788k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
[B]14844 p2p       22   0  108m  87m 7364 R 98.4 17.4 739:50.86 amuled[/B]
 2429 root      15   0  1404  504  436 S  0.3  0.1  12:26.29 lircd
23440 root      16   0 10572 8892 2080 S  0.3  1.7   9:55.75 Xvnc

aMulecmd$ stats
 > Verbunden zu Razorback 2 [195.245.244.243:4661] mit hoher ID
 > Download:     62 KB/sec
 > Upload:      30 KB/sec
 > Clients in Warteschlange:    2940
 > Gesamte Quellen:     8879

aMulecmd$ statistics
 > Statistics
 >  Uptime: 22:12 hours
 >  Transfer
 >   Session UL:DL Ratio (Total): 1 : 1.70
 >   Uploads
 >    Uploaded Data (Session (Total)): 2.20 GB (14.32 GB)
 >    Total Overhead (Packets): 66.70 MB (1.47M)
 >    File Request Overhead (Packets): 29.43 MB (882K)
 >    Source Exchange Overhead (Packets): 2.28 MB (6K)
 >    Server Overhead (Packets): 652 KB (47K)
 >    Kad Overhead (Packets): 0 Bytes (0)
 >    Active Uploads: 5
 >    Waiting Uploads: 2975
 >    Total successful upload sessions: 295
 >    Total failed upload sessions: 35
 >    Average upload time: 23:19 mins
 >   Downloads
 >    Downloaded Data (Session (Total)): 3.74 GB (36.07 GB)
 >     eMule: 3.53 GB
 >     aMule: 53.85 MB
 >     eDonkey: 0 Bytes
 >     eDonkeyHybrid: 39.57 MB
 >     Shareaza: 105.76 MB
 >     MLDonkey: 17.99 MB
 >     (l/x)Mule: 0 Bytes
 >     Other: 0 Bytes
 >    Total Overhead (Packets): 71.57 MB (1.02M)
 >    File Request Overhead (Packets): 26.00 MB (567K)
 >    Source Exchange Overhead (Packets): 18.64 MB (18K)
 >    Server Overhead (Packets): 268 KB (3K)
 >    Found Sources: 8992
 >    Active Downloads (chunks): 10
 >  Connection
 >   Average Downloadrate (Session): 49.07 kB/s
 >   Average Uploadrate (Session): 28.88 kB/s
 >   Max Downloadrate Average (Session): 60.41 kB/s
 >   Max Downloadrate (Session): 201.78 kB/s
 >   Reconnects: 3
 >   Time Since First Transfer: 22:12 hours
 >   Connected To Server Since: 6:48 hours
 >   Active Connections (estimate): 43741
 >   Max Connection Limit Reached: 842001083 : 2005-06-07 01:58:55
 >   Average Connections (estimate): 23192.939453
 >   Peak Connections (estimate): 73454
 >  Clients
 >   Total: 10768 Known: 4854
 >   eMule: 4507 (92.9%)
 >     v0.46a: 1509 (33.5%)
 >     v0.45b: 1020 (22.6%)
 >     v0.45a: 38 (0.8%)
 >     v0.44d: 394 (8.7%)
 >   aMule: 55 (1.1%)
 >    Version
 >      v2.0.0: 53 (96.4%)
 >      v1.x: 1 (1.8%)
 >    Operating System
 >     Linux: 12 (21.8%)
 >     MacOS: 1 (1.8%)
 >     Not Received: 42 (76.4%)
 >   lMule/xMule: 1 (0.0%)
 >   eDonkeyHybrid: 180 (3.7%)
 >    v1.0.0: 18 (10.0%)
 >    v0.53.0: 30 (16.7%)
 >    v0.52.0: 19 (10.6%)
 >    v0.51.2: 1 (0.6%)
 >   eDonkey: 0 (0.0%)
 >   cDonkey: 0 (0.0%)
 >   Old MLDonkey: 0 (0.0%)
 >   New MLDonkey: 27 (0.6%)
 >   Shareaza: 71 (1.5%)
 >   lphant: 13 (0.3%)
 >   Compatible: 0 (0.0%)
 >   Unknown: 5914
 >   LowID: 1066 (9.90% Total 20.21% Known)
 >   SecIdent On/Off: 4432 (97.15%) : 43 (0.94%)
 >   HasSocket: 230 (2.1%)
 >   Filtered: 0
 >  Servers
 >   Working Servers: 100
 >   Failed Servers: 800
 >   Total: 900
 >   Deleted Servers: 0
 >   Users on Working Servers: 3891782
 >   Files on Working Servers: 448985628
 >   Total Users: 5322422
 >   Total Files: 1135390899
 >   Server Occupation: 13.64%
 >  Shared Files
 >   Number of Shared Files: 118
 >   Total size of Shared Files: 44.91 GB
 >   Average filesize: 389.77 MB



[lfroen]

Hmm ... several things: first, pls check that problem is amuleD specific, i.e. amule is ok, but amuled doesn't. Second, can you tell me how many network connections amuled uses ? i.e. output of:
"netstat -nap | grep -c amuled"
Third: try with recent cvs - I've done some optimizations in network code.

[sirius]

Thanks, will get latest cvs and test with amule and amuled, but not today. For now, it currently uses around 300 connections, however after I used amulecmd for my last post, it was gone, so I had to restart, so it's only running a few ours now and no issue so far ....

Will post if problem persists with latest cvs.
Thanks

[setabi]

I have a similar problem with 2.0.2. The CPU usage goes to 100%. Sometimes stays at 100% for few minutes and sometimes up to an hour or more.

[Kry]

2.0.2 and CVS are VERY different. So please, different threads for different version

[stefanero]

well and for 2.0.2 we dont need no more info about amuled running 100% cpu, the network code got completly reworked by lfroen because of THAT!!!
and if you would have read the release 2.0.2 post, you would know that in cvs atm the only way to use the network code, since its not yet in 2.0.2!!

stefanero