Print

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

[Aethereal]

I've lately noticed, looking at amuled log (build from 20060109 sources) an increasing number of lines of this kind:

Code: [Select]

ED2k Client: Client ***** on IP:Port ***.***.**.**:4661 using eMule v0.46c requested file-data at an invalid position - disconnecting
The lines come from different clients IP and *Mule versions so I don't think all of them have an error on their side.
Unfortunately there is no reference anywhere to the file they are requesting data from, so I can't tell if it's always the same file or not.

I suppose there can be different answers:

1 - An error introduced in the CVS with some recent patch/change (very difficult, aMule developers couldn't do such a mistake!)
2 - A .part or .part.met file got corrupted and report incorrect data (but how could I locate it?)
3 - One of the files in my download queue is some sort of fake/mangled file (how can I find that as well?)

I've tried shutting down and restart amuled to see if it was able to "spot" a corrupted .met in the initial check phase, but with no use, and I have no messages of suspicious/incomplete files from the server when I connect...

Anyone have some hints?

Thanks a lot

[Kry]

I would bet on 3. That message was added when Xaignar and I detected such srange requests, but dissapeared on some time. Funny enough, oyu're getting them now.

Might be a hash conflict, 2 files with same hash and different size.


Will have to take a look.