View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000897aMuleServerspublic2006-05-21 11:392006-05-22 15:48
Assigned ToKry 
PlatformOSOS Version
Product Version2.1.1 
Target VersionFixed in VersionSVN 
Summary0000897: AICH-Hasher complains about known2.met during startup
DescriptionHi there,

I have strange behavior at startup since i upgraded to 2.1.1 (was amule CVS, 2.0.3 if i remember). After amule connected to a server, some messages concerning AICH appear (approximately, since it is translated from french) :

- AICH Thread: the known files masterhashes have been loaded.
- AICH Thread: Starting hash: 'N' files found.
- AICH Thread: Hash of file 'Whatever1.file', 3 more files
- SHAHashSet: Error: /home/myuser/.aMule/known2.met (bold)
- AICH-Hasher: Failed to save AICH Hashset! (bold)
- AICH Thread: Hash of file 'Whatever2.file', 2 more files
- SHAHashSet: Error: /home/myuser/.aMule/known2.met (bold)
- AICH-Hasher: Failed to save AICH Hashset! (bold)

... and so on, with two more files. BTW, those files are medium-sized, about 10 MB.

Following messages are :
- AICH Thread : hash finished
- AICH Thread : finished
- SHAHashSet: Error: /home/myuser/.aMule/known2.met (bold)
- Hasher: Warning, failed to save AICH hashset for file: Whatever0.file (bold)
- Hasher: hash finished for file : Whatever0.file
- Hasher: no more files in queue, ending thread
- Hasher: a thread is dead

Whatever0.file weights about 350 MB.
Following this first hash step, a syncronization thread starts, and AICH thread tries a second time to hash every 5 files mentionned above, with no more success (?) since it complains about known2.met.

known2.met had permissions 775, i changed them to 777, but the errors remain (not surprinsingly). Googling a few, i found a page mentionning that known2.met has to be locked by the hasher, and so it seems to me this file can't be locked ?

Plase let me know if i can do anything to help on this (apart coding, of course)

Thanks for your attention,

Additional Informationamule 2.1.1 using wxGTK2 v2.6.2 (Unicoded)
Linux 2.6.10-grsec i686
TagsNo tags attached.
Fixed in Revision
Operating SystemDebian Sarge 3.1r2 up-to-date (or should be)
Attached Files

- Relationships

-  Notes
Kry (manager)
2006-05-21 18:55

tried removing it? And btw, do you ahve disk space?
essaion (reporter)
2006-05-21 20:37

Hi again,

Thanks for your answer Kry.

About removing it, i was guessing what exactly (since i found many answers) was the function of known2.met. I just don't want to lose the "what did i downloaded" history, since some new searches may rise files i already downloaded (ya know, those green-fonted lines, that i really don't want to download again).

The files weights a woopy 138 MB, maybe it is too much to fight for aMule ?

Thanks in advance for any answer !
essaion (reporter)
2006-05-21 20:40

Woops, about your question : "do i have disk space ?"

Yes, my .aMule directory is on the same partition as the "Incoming" one. It may be a bad idea, since the amule crash i also reported when there's no space left may be attributed to that (but i'm not sure, since 2.0.3 wasn't affected by this "no more space" issue).
essaion (reporter)
2006-05-21 20:41

ARRGHHH, will i answer to your question ?

Yes : i have some spae left, something like 2.5 GB. Should be enough, shouldn't it ?
essaion (reporter)
2006-05-22 12:29

It's me again ("argh, no !!" may you thought)

Forget my question concerning known2.met. I finally found the amule page about AICH, and that known2.met actually stores the completed files AICH hashets. I then deleted it and restarted amule : no more errors with that file.

Since there is no clue about what caused the problem (i suspect 138 MB is quite large for that file, maybe amule can't deal with big sizes ?), i suggest moving this issue to "resolved".
Kry (manager)
2006-05-22 15:48

We may never find out...

- Issue History
Date Modified Username Field Change
2006-05-21 11:39 essaion New Issue
2006-05-21 11:39 essaion Operating System => Debian Sarge 3.1r2 up-to-date (or should be)
2006-05-21 18:55 Kry Note Added: 0001983
2006-05-21 20:37 essaion Note Added: 0001984
2006-05-21 20:40 essaion Note Added: 0001985
2006-05-21 20:41 essaion Note Added: 0001986
2006-05-22 12:29 essaion Note Added: 0001989
2006-05-22 15:48 Kry Status new => assigned
2006-05-22 15:48 Kry Assigned To => Kry
2006-05-22 15:48 Kry Status assigned => resolved
2006-05-22 15:48 Kry Fixed in Version => CVS
2006-05-22 15:48 Kry Resolution open => fixed
2006-05-22 15:48 Kry Note Added: 0001990

Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker