P2665 R3 C815 G22 + P3064 R3 C49 G81
Posted: Fri Aug 01, 2008 5:42 pm
Over the past TEN DAYS I have gotten the work unit P2665 R3 C815 G22 TWELVE TIMES on one machine.
Each and every time it wil EUE at step 22. Each time the same
Mind you I didn't get all TWELVE in a row...... NO
Intermixed with those EUEs I also got SIX of P3064 R3 C49 G81
Each and every one of those ended in an EUE like this
This is a stock clocked Core Duo system that has been Folding reliably for quite a while.
Can you please figure out why these work units are so unstable and why, in one case, I was issued the P2665 R3 C815 G22 work unit FOUR times in a row, followed by the equally unstable P3064 R3 C49 G81 once - then another THREE of the P2665 R3 C815 G22. Your server should not be sending the same work unit to the same computer TWELVE times.
Each and every time it wil EUE at step 22. Each time the same
Code: Select all
[06:48:27] Completed 55000 out of 250000 steps (22 percent)
[07:25:42] Warning: long 1-4 interactions
[07:25:42] Gromacs cannot continue further.
[07:25:42] Going to send back what have done.
[07:25:42] logfile size: 51689
[07:25:42] - Writing 52225 bytes of core data to disk...
[07:25:42] ... Done.
[07:27:42]
[07:27:42] Folding@home Core Shutdown: EARLY_UNIT_END
[07:27:42]
[07:27:42] Folding@home Core Shutdown: EARLY_UNIT_END
[07:27:45] CoreStatus = 7B (123)
[07:27:45] Client-core communications error: ERROR 0x7b
[07:27:45] Deleting current work unit & continuing...Intermixed with those EUEs I also got SIX of P3064 R3 C49 G81
Each and every one of those ended in an EUE like this
Code: Select all
[17:20:09] Completed 1050000 out of 5000000 steps (21 percent)
[17:41:16] Gromacs cannot continue further.
[17:41:16] Going to send back what have done.
[17:41:16] logfile size: 36011
[17:41:16] - Writing 36547 bytes of core data to disk...
[17:41:16] ... Done.
[17:41:16] - Failed to delete work/wudata_07.sas
[17:41:16] - Failed to delete work/wudata_07.goe
[17:41:16] Warning: check for stray files
[17:41:16]
[17:41:16] Folding@home Core Shutdown: EARLY_UNIT_END
[17:41:16]
[17:41:16] Folding@home Core Shutdown: EARLY_UNIT_END
[17:41:20] CoreStatus = 7B (123)
[17:41:20] Client-core communications error: ERROR 0x7b
[17:41:20] - Attempting to download new core...
[17:41:20] + Downloading new core: FahCore_a1.exeCan you please figure out why these work units are so unstable and why, in one case, I was issued the P2665 R3 C815 G22 work unit FOUR times in a row, followed by the equally unstable P3064 R3 C49 G81 once - then another THREE of the P2665 R3 C815 G22. Your server should not be sending the same work unit to the same computer TWELVE times.