Quote:
Originally posted by 4th gen@16 March 2004 - 17:22
Twice now since I've been using F@H, it's crashed taking hours of CPU time with it. The first time I lost about 71% of a work unit, due to a communications error with the server:
"[06:21:45] Completed 355000 out of 500000 steps (71)
[06:33:02] CoreStatus = 1 (1)
[06:33:02] Client-core communications error: ERROR 0x1
[06:33:02] Deleting current work unit & continuing...
[06:33:22] - Preparing to get new work unit...
[06:33:24] + Attempting to get work packet
[06:33:24] - Connecting to assignment server
[06:33:27] + Could not connect to Assignment Server
[06:33:27] + Could not connect to Assignment Server 2
[06:33:27] + Couldn't get work instructions.
[06:33:27] - Error: Attempt #1 to get work failed, and no other work to do.
Waiting before retry."
Which prompted me to stop using it. I retried it the other day, got one WU completed. My PC crashed again today, and no surprise, F@H lost its WU again:
"[16:33:30] Completed 480000 out of 500000 steps (96)"
:(
The first bit (up to [06:33:02]) indicates some sort of file system error, not a communication error. Basically it could not write the results to the disk, presumably because it thought the file was corrupt. Rather than send bad results back to the source it deleted them.