Folding Forum

Never seen this before.

I had 6701 (Run 91, Clone 22, Gen 12) assigned to two linux machines
repeatedly, then immediately fail with a CoreStatus 0 (0)
(one machine 32 times in a row, the other over 100 times in a row)

Typically, a WU will fail several times in a row, then get a different
one assigned. Not this time. Even deleting queue.dat and the
work director contents did not help. I was issued the same WU.

I do not normally use a proxy, the client work stations connect directly.

The odd thing is, I configured them both to use a proxy on a
different internet service provider, restarted the clients, and
was immediately assigned a new WU.

According to viewtopic.php?f=24&p=149786#p149786 big WUs have been turned off on Linux. I would think that if you're reassigned WUs from this project before a new version of FahCore_a3 is released, something is wrong. I'll bet that the shutdown is related to the problem that you're reporting.

6701 is not bigadv

You're right, it's not. I have not figured out an easy way to tell the difference. How do you do it?

In any case, other people have had trouble with this WU so I'm reporting it as a Bad WU.

bruce wrote:You're right, it's not. I have not figured out an easy way to tell the difference. How do you do it?

All of the bigadv projects so far have been numbered 268x.

bruce wrote:How do you do it?

Remember all those posts complaining about the SMP WU from Hell? 6701.