Print

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

[BeFalou]

I sent the ethereal log to lfroen a few hours ago, but you're faster coding than ethereal capturing ^_^

Thank you very much.

[BeFalou]

Still happening with 20050325, it's been running for a day and is almost reaching my limit.

[Mr Faber]

Reaching of the limit is normal if you have many sources but it shouldn't happend every second

cu
Mr Faber

[BeFalou]

Is this supposed to be solved? It is still happening here, anyone else?

[yoyoio]

BeFalou, me too

I've changed my settings to 1000 conn. and 200 sources/file (only 1 file downloading), and after a couple of days the limit is reached. And it happends every second...

With this settings normal amule works very fine.

BTW, Does the udp port still need to be disabled?

Thanks

[lfroen]

With this settings normal amule works very fine.

Reaching connection limit is ok (that's what limit is for). If those connections are "ESTABLISHED" and you have up/down streams, I would say it's ok.

BeFalou: i see nothing unusual in trace you sent me.

[BeFalou]

Reaching the limit from time to time is okay but not all the time, it works fine for a day or so, although connections keep growing, and then amuled gets slower. I don't know what would happen after 2 days or more because I often change to current cvs.

Thing is, if this is normal, why is not happening with aMule? Seems to be more efficient managing connections than amuled.

Regards.

[lfroen]

Thing is, if this is normal, why is not happening with aMule? Seems to be more efficient managing connections than amuled.

point is right. they must behave almost same. Can you say what's a status of connections? How match is "EXTABLISHED", "CLOSE_WAIT" etc. You can see it with "netstat -nap | grep amuled"

[BeFalou]

Originally posted by BeFalou
Here you have what netstat says about connections:

Code: [Select]

# netstat -putan | grep amuled | wc -l
330

# netstat -putan | grep amuled | grep ESTABLISHED | wc -l
326

# netstat -putan | grep amuled | grep CLOSE_WAIT | wc -l
2This time is taking longer to reach the limit but it is very close. Now I'm gonna try with ethereal.

I already posted it :]

[yoyoio]

Sorry, the first post is wrong. Only uploading the problem happens as well.

I think I found out some interesting relationship between ESTABLISHED connections and total failed upload sessions. I've been taking values for ESTABLISHED connections from amuled  and number of total failed upload sessions since a few hours.

failed-upload:established:established - failed  

260 300  40
269 320  51
283 334  51
317 370  63
340 370  30
348 395  47

So, established = failed + ~50 , perhaps it's only a coincidence

Uptime: 1 Days 21 hours (only uploading)

863 619 -244

So, the behavior has changed and it was only a coincidence, or linux is closing old connections.

BeFalou, is the same for you?.

I'll put something to download later to see what happens.


Regards

[BeFalou]

amuled uptime: 21h, it's not reaching my limit yet, I`ll update this when it does.

failed-upload:established:established - failed

55 276 221

EDIT: After 1D 22h, (my limit is 400)

161 401 360

[yoyoio]

Now

Established 986 (My limit is 1000)

Estadísticas
   Uptime: 3 Days 00 hours
   Transferencia
      Session UL:DL Ratio (Total): Not available
      Subidas
         Uploaded Data (Session (Total)): 9,98 GB (55,62 GB)
         Total Overhead (Packets): 166,21 MB (2,36M)
         File Request Overhead (Packets): 73,74 MB (847K)
         Source Exchange Overhead (Packets): 15,39 MB (38K)
         Server Overhead (Packets): 134 KB (31K)
         Subidas activas: 17
         Subidas en espera: 4000
         Total de subidas satisfactorias: 10409
         Total de subidas erróneas: 1720
         Average upload time: 5:40 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): 98,31 MB (2,35M)
         File Request Overhead (Packets): 33,05 MB (1,55M)
         Source Exchange Overhead (Packets): 953 KB (61K)
         Server Overhead (Packets): 3 KB (35)
         Fuentes encontradas: 0
         Descargas activas (partes): 0

[stefanero]

no download at all?!  8o
in 3days???

[yoyoio]

That's because I didn't put anything to download

I'm testing the problem with active connections.

Now, running 3 days 1hour and amuled is starting to drop clients from queue because there's no room for new connections.

Estadísticas
   Uptime: 3 Days 01 hours
   Transferencia
      Session UL:DL Ratio (Total): Not available
      Subidas
         Uploaded Data (Session (Total)): 10,12 GB (55,76 GB)
         Total Overhead (Packets): 167,70 MB (2,38M)
         File Request Overhead (Packets): 74,39 MB (854K)
         Source Exchange Overhead (Packets): 15,50 MB (38K)
         Server Overhead (Packets): 136 KB (31K)
         Subidas activas: 17
         Subidas en espera: 3862
         Total de subidas satisfactorias: 10580
         Total de subidas erróneas: 1750
         Average upload time: 5:39 mins
.......
......
Conexión
      Velocidad media descarga (Sesión): 0,00 kB/s
      Velocidad media subida (Sesión): 40,16 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 01 hours
      Connected To Server Since: 3 Days 01 hours
      Active Connections (estimate): 997
      Max Connection Limit Reached: 1673 : 2005-04-11 23:28:59
      Average Connections (estimate): 999,437317
      Peak Connections (estimate): 1003.
....
....
   Archivos compartidos
      Nº de archivos compartidos: 267
      Total size of Shared Files: 101,06 GB
      Average filesize: 387,60 MB

So, there's something wrong with amuled.

[lfroen]

yoyoio: ok, connection limit is reached. No dload 'cause there's nothing in queue. But upload ? I don't see it in stats. Or you telling that there's no upload as well ?