There's no more work available at the moment due to the distributed.net keymaster hardware failure. Our local cache was just also depleted, which lasted for about two days. So let's finish what we have and then move on to backup projects (yes, they are always good idea to have) while we wait for the distributed.net staff to repair keymaster. Rest assured, they are working hard to get the keymaster back up. As soon as that happens, we'll get fresh work out for our hungry systems to crunch.

For more details and latest developments, please read http://blogs.distributed.net/. Thanks for your patience!

There's no more work available at the moment due to the distributed.net keymaster hardware failure. Our local cache was just also depleted, which lasted for about two days. So let's finish what we have and then move on to backup projects (yes, they are always good idea to have) while we wait for the distributed.net staff to repair keymaster. Rest assured, they are working hard to get the keymaster back up. As soon as that happens, we'll get fresh work out for our hungry systems to crunch.

For more details and latest developments, please read http://blogs.distributed.net/. Thanks for your patience!

It's been a week, can we get an update?

I believe Teemu is dependent on the folks on distributed net -- and they have not released any updated information in 10 days...

I don't know enough about the backend stuff..
I have been receiving sporadic work units,
but now does seem to have dried up since yesterday.
Last one I got yesterday at 15:55

Moo! gets their work from distributed.net. Since distributed.net has an issue currently and cannot create work, new work is unavailable for Moo!. Rework is still being pushed out, as there are about 2300 units still being crunched and if any of those come back as inconclusive, not returned in time, and/or other errors, then those units get sent to another person. Watching the numbers the past few days I suspect this will mostly dry up in less than a week (except for the few stragglers that sit in queue someplace until they expire).

The admin here has no more real information than is posted on distributed.net's site. This is not the only project affected by this. Yoyo's Cruncher OGR is also.

As Teemu has stated, find another backup project until things are back to order. Even after distributed get going again, it may take a while for work to be generated over here, because work is generated for their own project, plus others. Filling all those work request will take time.

Thanks for the explanation, now I see how I probably got some WU's

It's been a week, can we get an update?

Dnet volunteer staff was working on the keymaster hardware issue and they managed to get it back alive, at least temporarily pending further hardware replacements. Sounds like there was at least a fried memory module that brought keymaster down.

I'm just starting the work generators to get fresh work out there. Also I'm bumping our buffer levels a bit. :)

Looks like others answered the other questions raised here, thanks for those!

-w