Project: 2665 (Run 3, Clone 708, Gen 9) [Long 1-4]

[MoneyGuyBK]

One of my teammates has had an issue with this particular WU.
He has been Folding constantly now for over 3 months with no issues.
I had him delete the Work and Qeue folders and logs... he finally received a different WU which seems to crunch as it should.
Just FYI, and I Qute below:

Friends, I am having troubles with my SMP client. The WU gets to 1% and says:

Code: Select all

[16:06:49] *------------------------------*
[16:06:49] Folding@Home Gromacs SMP Core
[16:06:49] Version 1.76 (February 23, 2008)
[16:06:49] 
[16:06:49] Preparing to commence simulation
[16:06:49] - Ensuring status. Please wait.
[16:06:55] - Starting from initial work packet
[16:06:56] 
[16:06:56] Project: 2665 (Run 3, Clone 708, Gen 9)
[16:06:56] 
[16:06:56] Assembly optimizations on if available.
[16:06:56] Entering M.D.
[16:07:19] 5 percent)
[16:07:19] - Starting from initial work packet
[16:07:19] 
[16:07:19] Project: 2665 (Run 3, Clone 708, Gen 9)
[16:07:19] 
[16:07:20] Entering M.D.
[16:07:30] Rejecting checkpoint
[16:07:32] Protein: HGG in water
[16:07:32] Writing local files
[16:07:42] Extra SSE boost OK.
[16:07:43] Writing local files
[16:07:43] Completed 0 out of 250000 steps  (0 percent)
[16:29:39] Writing local files
[16:29:39] Completed 2500 out of 250000 steps  (1 percent)
[16:36:36] Warning:  long 1-4 interactions
[16:36:40] a_01.sas
[16:36:40] - Failed to delete work/wudata_01.goe
[16:36:40] Warning:  check for stray files
[16:36:40] s
[16:36:40] - Failed to delete work/wudata_01.goe
[16:36:40] Warning:  check for stray files
[16:36:40] data_01.sas
[16:36:40] - Failed to delete work/wudata_01.goe
[16:36:40] Warning:  check for stray files
[16:36:40] 
[16:36:40] Folding@home Core Shutdown: EARLY_UNIT_END
[16:36:40] Finalizing output

I have tried deleting the queue.dat file and the entire work folder, same thing over and over again.

Any ideas?

Thanks a lot,
Rafa.


Original messgae here:
http://forums.rampantspeculation.com/vi ... 2192#12192




Peace

[bruce]

Thanks for the report. We seem to have a rash of reports of the same problem this morning. Such errors have been reported before but the frequency has been low and no fixes are available yet. Sometimes a Long 1-4 Interaction message leads to an error and sometimes it does not.

We're in the process of collecting more data so the development folks can figure out how to get past this condition without discarding the WU.