Project: 2675 (Run 1, Clone 251, Gen 36) CoreStatus = 1 (1)

[parkut]

This particular WU yielded a CoreStatus = 1 (1) immediately on startup. It failed six (6) times, and then moved on to a different WU, which is processing normally

model name : Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
cpu MHz : 2394.000
cache size : 4096 KB
Memory: 1.95 GB physical, 1.94 GB virtual
...
Client Version 6.24beta
Core: FahCore_a2.exe
Core Version 2.07 (Sun Apr 19 14:51:09 PDT 2009)

Code: Select all

[06:32:43] Project: 2675 (Run 1, Clone 251, Gen 36)
[06:32:43] 
[06:32:43] Entering M.D.
[06:32:52] Completed 0 out of 250000 steps  (0%)
[06:32:56] CoreStatus = 1 (1)
[06:32:56] Sending work to server
[06:32:56] Project: 2675 (Run 1, Clone 251, Gen 36)
[06:32:56] - Error: Could not get length of results file work/wuresults_04.dat
[06:32:56] - Error: Could not read unit 04 file. Removing from queue.
[06:32:56] Trying to send all finished work units
[06:32:56] + No unsent completed units remaining.

[toTOW]

No body has been able to return results for this WU yet ...

[susato]

This one is fouling people up two weeks later, as per a report in my home-team's forum.
Looks like this one has been flying under the radar for more than a month.
The previous generation was returned on April 10. Neighboring clones of the same gen were returned in March and April.

This WU is a lemon - I'm marking it bad.
I wonder if there's some automated way of identifying a bad WU when it doesn't create error reports in the db.