aMule Bug Tracker - aMule | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0000897 | aMule | Servers | public | 2006-05-21 11:39 | 2006-05-22 15:48 |
Reporter | essaion | ||||
Assigned To | Kry | ||||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Platform | OS | OS Version | |||
Product Version | 2.1.1 | ||||
Target Version | Fixed in Version | SVN | |||
Fixed in Revision | |||||
Operating System | Debian Sarge 3.1r2 up-to-date (or should be) | ||||
Summary | 0000897: AICH-Hasher complains about known2.met during startup | ||||
Description | Hi 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, -- essaion | ||||
Steps To Reproduce | |||||
Additional Information | amule 2.1.1 using wxGTK2 v2.6.2 (Unicoded) Linux 2.6.10-grsec i686 | ||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
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 |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|