Print

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

[Chadda]

My amule log is constantly flooded by the same messages:

06/25/04 23:05:57: Not sending SecIdentState Packet, because State is Zero
06/25/04 23:05:58: Not sending SecIdentState Packet, because State is Zero
06/25/04 23:05:58: Client '' (IP:xxx.xxx.xxx.xxx) caused an error: 7. Disconnecting client!
06/25/04 23:05:58: http://emule-project.net: Upload session ended due canceled transfer.
06/25/04 23:05:59: Not sending SecIdentState Packet, because State is Zero
06/25/04 23:05:59: Not sending SecIdentState Packet, because State is Zero
06/25/04 23:06:00: Not sending SecIdentState Packet, because State is Zero


I wonder what this means, or if this affects anything on my down/uploads... As you can see, every second I get one or two messages of this kind... is this normal?

[deltaHF]

amule version ?

[Chadda]

25/04 23:20:12: Not sending SecIdentState Packet, because State is Zero
06/25/04 23:20:12: Not sending SecIdentState Packet, because State is Zero
06/25/04 23:20:13: Client 'mr.noone (IP:xxx.xxx.xxx.xx) caused an error: CUpDownClient::ProcessExtendedInfo: Read after End Of MemFile (corrupted tag?). Disconnecting client!
06/25/04 23:20:13: Not sending SecIdentState Packet, because State is Zero
06/25/04 23:20:15: Not sending SecIdentState Packet, because State is Zero
06/25/04 23:20:15: Not sending SecIdentState Packet, because State is Zero


Another one. CUpDownClient ?

[Chadda]

The .deb cvs one.

But also used to happen with the 2.0.0rc3 and 2... not that fast, but in intervals of 10 seconds or so

[deltaHF]

try to recompile your crypto++

and disable verbose in amule tweaks if its enabled

[Chadda]

I've got my crypto++ from debian repository

Anyways, thank you for replying THIS fast. And sorry for being blind, because I swear, I DIDN'T see the topic talking exactly about the same thing right here in this section  :]







Another thing:
aMule is running well for more than 5 hours without crashing. I thought this was too good to be true, when I just saw amule eating 99% of my cpu (1ghz) after some time running fine.

If I close and restart amule, it runs ok again, consuming less than 30% of the system. Apparently, there is no error messages on console, or any reason that could cause this.

BTW, I also remember, with some older version I think, that if I delete a file which is being shared, amule used to crash whenever a user tries to download the 'fake' share... I never saw this happening on cvs, tough...


Edited: When amule starts consuming up to 99% of the CPU, the download speeds are all messed up. My connection has just 256kb/s of downloading, so my maximum rate would be only 32KB/s, but aMule starts showing 40, 80, even 110KB/s as speed for a single transfer.

[deltaHF]

Originally posted by deltaHF


and disable verbose in amule tweaks if its enabled