Moo! Wrapper

About Moo! Wrapper

Moo! Wrapper brings together BOINC volunteer computing network resources and the Distributed.net projects. It allows a BOINC Client to participate in the RC5-72 challenge.

If you want to learn more about Distributed.net Project and Client, please visit their website. Especially, detailed information about the RC5-72 challenge is available.

Note that we have intentionally left Distributed.net OGR-project out of scope since you can already join that project at Yoyo@Home.

Join Moo! Wrapper

Read our rules and policies
This project uses BOINC. If you're already running BOINC, select Attach to Project. If not, download BOINC.
When prompted, enter
http://moowrap.net/
If you're running a command-line or pre-5.0 version of BOINC, create an account first.
If you have any problems, get help here.

Current crunchers

Your account - view stats, modify preferences
Teams - create or join a team
Certificate - print contribution certificate
Applications - versions and supported platforms
Donations - help with our monthly operation costs

Statistics

Community

Other

Languages

News

Transitioner problem solved
It turned out the problem was actually caused by a corrupted index in one of the primary database tables used by BOINC Server. Recreated the table/index and things are looking much better so I've restarted the system. However, transitioner is now going through all the 600k workunits in the DB and only once that is done, the system will start creating new workunits. Until then we are out of work to send. Sorry! I'll keep an eye out to make sure we recover fully.
22 May 2013, 17:05:39 UTC · Comment

Weird BOINC server bug causing problems
It seems transitioner is not transitioning anything since 5h ago so nothing is progressing through our pipe. I've shut down most background tasks to be safe until I can figure out what's going on with BOINC server programs at the moment. Unfortunately, this has to wait until later today.

You don't have to cancel current work units you might have as they will get reported and credited once services are back up. They can even be 1-2 days overdue and still get accepted. However, you might want switch to your backup projects until we have new work ready.

Sorry for the problems and this unexpected extended downtime!
22 May 2013, 5:22:06 UTC · Comment

Work shortage and previous outages
It seems we run out of work to send today for a second time during this week (last incident happened three days ago) and both of them has been because upstream (distributed.net) keymaster has not send us any work to generate into work units for you to crunch on.

Three days ago the keymaster run out of work (they currently have limited alerts for such issues due to a monitoring server failure) until an operator queued more work and today the keymaster was somehow confused and not sending anything until the same operator restarted the service. So work is getting generated and send to you again.

Also, there has been some total outages earlier that has been due to our primary database server crashing. I'm still trying to figure out what's the exact cause of it's crashing under high load but for now my work a rounds has been keeping it up. If all else fails, I'm going to change server hardware to one that's hopefully more reliable.
21 Mar 2013, 18:51:56 UTC · Comment

... more

News is available as an RSS feed RSS