Print

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

[yoyoio]

There are uploads in my previous posts.

first:

Subidas activas: 17 (uploading)
Subidas en espera: 4000 (clients in upload queue)
Total de subidas satisfactorias: 10409 (uploads ok)
Total de subidas erróneas: 1720 (failed uploads)

second:

Subidas activas: 17
Subidas en espera: 3862
Total de subidas satisfactorias: 10580
Total de subidas erróneas: 1750
Average upload time: 5:39 mins
...
 Velocidad media subida (Sesión): 40,16 kB/s (average upload)
....
Archivos compartidos
Nº de archivos compartidos: 267 (number of shared files)
Total size of Shared Files: 101,06 GB
Average filesize: 387,60 MB

now:
 Uptime: 3 Days 18 hours
......
......
Subidas activas: 14
 Subidas en espera: 1
 Total de subidas satisfactorias: 11735
 Total de subidas erróneas: 2139
 Average upload time: 6:30 mins
...
...
Conexión
      Velocidad media descarga (Sesión): 0,00 kB/s
      Velocidad media subida (Sesión): 41,99 kB/s
....
active Connections (estimate): 1001

So, there is only 1 client in queue, 14 active uploads, (upload speed=50kb/s),but there are 1000 active connections.

[lfroen]

So, there is only 1 client in queue, 14 active uploads, (upload speed=50kb/s),but there are 1000 active connections.

This makes no sense. If you have no (or 1) clients in queue, how do you have 50kbps upload rate on 14 uploads ?

What OS / kernel do you using ?

[yoyoio]

OS: Gentoo on AMD K6-3D
Kernel 2.6.10-gentoo-r6

each upload at 3kb/s

When an upload finish, one more client enter the queue and starts upload (i think so)

aMulecmd$ stats                
 > Connected to Razorback 2 [195.245.244.243:4661] con IDAlta
 > Download:     0 Bytes/sec    
 > Upload:      50 KB/sec      
 > Clients in queue:    0      
 > Total sources:       0      
aMulecmd$    

Full statistics:
aMulecmd$ statistics            
 > Estadísticas                
 >  Uptime: 3 Days 22 hours    
 >  Transferencia
 >   Session UL:DL Ratio (Total): Not available
 >   Subidas
 >    Uploaded Data (Session (Total)): 13,78 GB (59,42 GB)
 >    Total Overhead (Packets): 171,59 MB (2,45M)
 >    File Request Overhead (Packets): 76,11 MB (877K)
 >    Source Exchange Overhead (Packets): 15,65 MB (38K)
 >    Server Overhead (Packets): 164 KB (39K)
 >    Subidas activas: 15
 >    Subidas en espera: 0
 >    Total de subidas satisfactorias: 11873
 >    Total de subidas erróneas: 2142
 >    Average upload time: 6:44 mins
 >   Descargas
 >    Downloaded Data (Session (Total)): 0 Bytes (11,72 GB)
 >     eMule: 0 Bytes
 >     aMule: 0 Bytes
 >     eDonkey: 0 Bytes
 >     eDonkeyHybrid: 0 Bytes
 >     Shareaza: 0 Bytes
 >     MLDonkey: 0 Bytes
 >     (l/x)Mule: 0 Bytes
 >     Other: 0 Bytes
 >    Total Overhead (Packets): 102,52 MB (2,45M)
 >    File Request Overhead (Packets): 34,96 MB (1,62M)
 >    Source Exchange Overhead (Packets): 1008 KB (65K)
 >    Server Overhead (Packets): 3 KB (35)
 >    Fuentes encontradas: 0
 >    Descargas activas (partes): 0
 >  Conexión
 >   Velocidad media descarga (Sesión): 0,00 kB/s
 >   Velocidad media subida (Sesión): 42,32 kB/s
 >   Promedio de descarga máx. (Sesión): 0,00 kB/s
 >   Descarga máxima (Sesión): 0,00 kB/s
 >   Reconexiones: 0
 >   Time Since First Transfer: 3 Days 22 hours
 >   Connected To Server Since: 3 Days 22 hours
 >   Active Connections (estimate): 996
 >   Max Connection Limit Reached: 3140 : 2005-04-12 20:21:09
 >   Average Connections (estimate): 996,003052
 >   Peak Connections (estimate): 1010
 >  Clientes
 >   Total: 397 Known: 397
 >   eMule: 334 (84,1%)
 >     v0.45b: 198 (59,3%)
 >     v0.45a: 3 (0,9%)
 >     v0.44d: 52 (15,6%)
 >     v0.44c: 1 (0,3%)
 >   aMule: 3 (0,8%)
 >    Versión
 >      v2.0.0: 3 (100,0%)
 >    Operative System
 >     Not Received: 3 (100,0%)
 >   lMule/xMule: 0 (0,0%)
 >   eDonkeyHybrid: 5 (1,3%)
 >    v1.0.0: 1 (20,0%)
 >    v0.52.0: 1 (20,0%)
 >    v0.50.1: 1 (20,0%)
 >    v0.10.3: 2 (40,0%)
 >   eDonkey: 0 (0,0%)
 >    v462.8.0: 1 (100,0%)
 >   cDonkey: 0 (0,0%)
 >   MLDonkey Antiguo: 0 (0,0%)
 >   MLDonkey Nuevo: 8 (2,0%)
 >   Shareaza: 45 (11,3%)
 >   lphant: 2 (0,5%)
 >   Compatible: 0 (0,0%)
 >   Desconocido: 0
 >   LowID: 148 (37,28% Total 37,28% Known)
 >   IdentSeg On/Off: 112 (33,23%) : 212 (62,91%)
 >   Filtrado: 0
 >  Servidores
 >   Servidores activos: 31
 >   Servidores caídos: 69
 >   Total: 100
 >   Servidores eliminados: 0
 >   Usuarios en servidores activos: 3087072
 >   Archivos en servidores activos: 351115647
 >   Usuarios totales: 4658227
 >   Archivos totales: 528062359
 >   Ocupación de Servidores: 18,62%
 >  Archivos compartidos
 >   Nº de archivos compartidos: 267
 >   Total size of Shared Files: 101,06 GB
 >   Average filesize: 387,60 MB

[lfroen]

I will try to reproduce it at home and debug it in deep.

[BeFalou]

Hey,

Did you find anything new about this? This is the most annoying thing in amuled right now as I have to restart it every two days or so. If you need any more info just ask for it.

Oh, and... Congrats for aMule-2.0.0!  

[lfroen]

No. I could not reproduce it. So the only way is to debug it at YOUR machine with your condition. Please confirm the following:
1. You did not tweaked any tcp/ip kernel settings
2. You do not using bandwidth control (tc command).
3. You do not observing this behavior with "regular" amule.

After that, at the time problem is being observed please provide the following:
1. Result of "netstat -nap | grep amuled"
2. Result of "netstat -i"
3. Result of "/sbin/ifconfig"
4. Run ethereal on your outgoing interface and provide resulting trace for several minutes. Send it as attachment to lfroen@gmail.com .
5. Amule settings.
6. Result of amulecmd -c stats (with english strings if possible).

I will make my best to find a source of this weird problem. Sorry for long list of requests, but I have run out of guesses.

[BeFalou]

I sent you an email with all the info you requested, however, I still have to try with regular aMule.

[Mr Faber]

Mhmm, I think I have the same problem. I have many downloads but that can't be the reason of the constant increment of active connections until the limit is reached.
I use tc but I am not the only one with this problem. Maybe aMuled or the wxLibs does not kill some old connections so after two days the limit gets reached.
By the way thanks for the great aMule 2.0 release. It is very stable.

cu
Mr Faber

[lfroen]

BeFalou, Mr Faber: I would like ask you again to confirm:
1. Problem only in amuled. Regular amule work fine.
2. You do not using tc. If you do, please disable it for testing time. It's complicated thing and can easy break your setup if incorrectly configured.

BeFalou: thanks for detailed info you sent. Now I've noticed that one thing is missing in my request:
* Your network setup
Since your IP is 10.0.0.2 - you must be using private/home lan. Please tell me (or send me) how your setup looks like. What kind of router is it ? Or switch ? Or both ?

Don't get me wrong - I really want to solve this problem. However, it seems that problem happens in specific setup (yours in particular). I'm still trying to figure out what exactly your setup is.

[Mr Faber]

Theoretically tc is disabled because aMule only works fine if it not reaches the upload limit of tc. I always limit the upload of aMule to prevent this special behaviour.
I have a public IP and the ports open so it shouldn't be the problem for me. But with the new CVS amuled 20050504 the connections seems very stable like expected after 14 hours of running. Maybe it changes later. In old versions I have to restart at least after three days because the limit of 500 connections was always reached and the download stucks. But the upload still works .
Except of my first runs of aMule I always use the daemon so I can't confirm it.

cu
Mr Faber

[BeFalou]

Everything MrFaber said is what happens here, but for me 14h is not too much, after 1 day or more is when the limit is reached.

@lfroen: I sent you my network setup.

[lfroen]

BeFalou: I still want to know whether it is amuled specific problem, and amule works fine.

[Mr Faber]

Ok, if I have the connection problem again or have to restart I will compile amule instead of amuled and check it.

cu
Mr Faber

[BeFalou]

I had to install wxGTK and amule monolithic so it took me longer to test it. After 6h30min my active connections are 83 right now and the graph seems to be very pretty stable.

[BeFalou]

Definitely it is not happening with regular amule. Uptime: 18h5min, amuled would have ~300 connections by now.