Print

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

[wuischke]

A user in a german forum had some problems with aMule 2.1.0 running on sarge. (Afaik thedude0001's packages)

MacLeod:
mein amule wird so alle 2-6 tage beendet, wie mit 'nem kill befehl.
die temp-dateien sind dann auch beschädigt, so das er nach nem neustart einige part.met nicht mehr beschreiben kann. ich muß dann den zugehörigen download abbrechen und neu starten

Rough translation:
My aMule closes every 2 to 6 days, as if it was killed by the kill command.
The temp-files are damaged then, so that he cannot write to some files anymore, I have to cancel and re-start the corresponding download.

It looks similar to the problem Arichy encountered, I proposed to do the same Arichy did to get a stable binary.

Does anyone know wheter there's a general problem with this binaries or does it just occure for some people?

[thedude0001]

Bah, I should start reading more carefully, thought you were talking about *our* german forums and went crazy looking for that thread ^^

Yes, those are my packages. The trouble Arichy had was a little different, it crashed on startup on him. A crash after 2-6 days can happen, though it shouldn't. The thing that concerns me is that his temp files are corrupted afterwards. Best thing to do is give him the hint towards gdb and our backtrace section on wiki and let him produce backtraces (my packages are compiled with debug ^^)

[jere666]

I may have a similar (?) problem since a few days.

After a few minutes, the CPU goes up to 99% , and I get thousands of lines like these ones :
""file_cluster badly computed !!!" on the console of Linux (Ctrl+amt+F1).

I am then forced to kill amule.


UPDATE:
I think I have solved the problem : There was an error on a .part file.
I use a VFAT filesystem for /temp/amule.

I have run the command : dosfsck -a -v /dev/hdd1

/TEMP/temp-amule/003.part
  File size is 311306775 bytes, cluster chain length is > 311308288 bytes.
  Truncating file to 311306775 bytes.

And now it works.