Folding Forum

[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 0 out of 250000 steps (0%)
[08:29:14] Writing local files
[08:29:14] Completed 2500 out of 250000 steps (1%)
[08:38:52] Writing local files
---------------------------------------------------
[19:18:18] Completed 177500 out of 250000 steps (71%)
[19:28:38] Writing local files
[19:28:38] Completed 180000 out of 250000 steps (72%)
[19:32:27] CoreStatus = 0 (0)
[19:32:27] Client-core communications error: ERROR 0x0
[19:32:27] Deleting current work unit & continuing...
[19:33:04] - Preparing to get new work unit...
[19:33:04] + Attempting to get work packet
[19:33:04] - Connecting to assignment server
[19:33:05] - Successful: assigned to (171.64.65.62).
[19:33:05] + News From Folding@Home: Welcome to Folding@Home
[19:33:05] Loaded queue successfully.
[19:33:07] + Closed connections
[19:33:12]
[19:33:12] + Processing work unit
[19:33:12] Core required: FahCore_78.exe
[19:33:12] Core found.
[19:33:12] Working on Unit 06 [March 25 19:33:12]
[19:33:12] + Working ...
[19:33:12]
[19:33:12] *------------------------------*
[19:33:12] Folding@Home Gromacs Core
[19:33:12] Version 1.90 (March 8, 2006)
[19:33:12]
[19:33:12] Preparing to commence simulation
[19:33:12] - Looking at optimizations...
[19:33:12] - Created dyn
[19:33:12] - Files status OK
[19:33:13] - Expanded 627772 -> 3099441 (decompressed 493.7 percent)
[19:33:13] - Starting from initial work packet
[19:33:13]
[19:33:13] Project: 6507 (Run 7, Clone 321, Gen 8)
[19:33:13]
[19:33:13] Assembly optimizations on if available.
[19:33:13] Entering M.D.
[19:33:19] Protein: 1CFC_B_8 in water
[19:33:19]
[19:33:19] Writing local files
[19:33:19] Extra SSE boost OK.
[19:33:19] Writing local files
[19:33:19] Completed 0 out of 250000 steps (0%)

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.

Following the error, no valid results were found so the Client had no choice but to Delete the current WU and continue.

When a WU is downloaded the server keeps a record of which client is working on the WU. When the result is returned, the uploaded WU replaces that record and it is no longer checked out to you. When the client requests a download, the server checks to see if you already have a WU that's being processed. If it finds one, it assumes the WU failed to donload so it re-sends the same WU;

What I see in your log looks quite normal, except for the original error 0x0.

bruce wrote: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 was not killed. What I posted is what the run did on its own.