Folding Forum

Last part of the log. (Part 3) [22:50:17] Completed 75000 out of 250000 steps (30%) [23:30:07] CoreStatus = 0 (0) [23:30:07] Client-core communications error: ERROR 0x0 [23:30:07] - Attempting to download new core... [23:30:07] + Downloading new core: FahCore_78.exe [23:30:07] + 10240 bytes download...

More of the run log. (Part 2) [03:59:30] + Closed connections [03:59:35] [03:59:35] + Processing work unit [03:59:35] Core required: FahCore_78.exe [03:59:35] Core found. [03:59:35] Working on Unit 06 [January 22 03:59:35] [03:59:35] + Working ... [03:59:35] [03:59:35] *-----------------------------...

This WU is bad. It has repeatedly failed at 30%. Although it ran a total of 21 times before I caught it, it refused to pick another WU and mark this one as bad. Is there any way to check for these units that repeatedly loop and won't cycle to a new work unit? I know you guys like to see the entire, ...

Terminated twice at 58% and would not get a new work unit. [21:28:59] - Preparing to get new work unit... [21:28:59] + Attempting to get work packet [21:28:59] - Connecting to assignment server [21:29:00] - Successful: assigned to (171.64.65.62). [21:29:00] + News From Folding@Home: Welcome to Foldi...

Consistently aborts at 4%. Looped 12 times without picking up a new WU. Was terminated after the 13th iteration. [13:37:48] - Preparing to get new work unit... [13:37:48] + Attempting to get work packet [13:37:48] - Connecting to assignment server [13:37:48] - Successful: assigned to (171.64.65.62)....

Aborts at 29%. Looped 6 times without getting another WU. Run was stopped after the 7th iteration. [02:34:29] - Preparing to get new work unit... [02:34:29] + Attempting to get work packet [02:34:29] - Connecting to assignment server [02:34:30] - Successful: assigned to (171.64.65.62). [02:34:30] + ...

Unit crashes at 11%. It looped 8 more times, crashing at the same point each time, without picking up a new work unit. [18:17:08] - Preparing to get new work unit... [18:17:08] + Attempting to get work packet [18:17:08] - Connecting to assignment server [18:17:08] - Successful: assigned to (171.64.6...

Thanks for the annotations, bruce. I was getting a little blurry after editing the logfile.

Your last post is both a double post and off-topic, both of which are prohibited on this forum. You should get your answer here: viewtopic.php?f=18&t=18492 when there's something to say. Lack of an answer doesn't mean nobody has noticed nor does it mean nothing is being done about it. My intent...

Thanks, bruce. I have one other problem with this client. It still has completed WUs to send but can't, due to connection errors with servers 171.64.65.111 and 171.67.108.17.

This WU has aborted 8 times at 31%, but is still running for the 9th time. It will not pick up a new work unit. Error message is: [00:00:12] Completed 77500 out of 250000 steps (31%) [00:03:41] CoreStatus = 0 (0) [00:03:41] Client-core communications error: ERROR 0x0 [00:03:41] Deleting current work...

Servers in question are:

Status
171.64.65.111 Connect - Reject
171.67.108.17 Connect - DOWN

Any ETA possible on when servers will accept connections?

Client-core communications error: ERROR 0x0 generally means the FahCore died and no error was reported. If you manually kill the FahCore or if there is a hardware error causing it to terminate unexpectedly you can get that error code. Understood. There have been no hardware errors, and the client w...

[08:19:06] Project: 6507 (Run 7, Clone 321, Gen 8) [08:19:06] [08:19:06] Assembly optimizations on if available. [08:19:06] Entering M.D. [08:19:12] Protein: 1CFC_B_8 in water [08:19:12] [08:19:12] Writing local files [08:19:12] Extra SSE boost OK. [08:19:13] Writing local files [08:19:13] Completed...

[15:00:14] Folding@home Core Shutdown: FINISHED_UNIT [15:00:39] CoreStatus = 64 (100) [15:00:39] Sending work to server [15:00:39] - Read packet limit of 540015616... Set to 524286976. [15:00:39] + Attempting to send results [15:00:42] + Results successfully sent [15:00:42] Thank you for your contri...