News:

Members can see all forum boards and posts. Non members can only see a few boards.  If you have forgotten your password use this link to change it.
https://forum.boinc-australia.net/index.php?action=reminder

Main Menu

Site/ servers down ??

Started by veebee, November 24, 2011, 08:09:48 AM

Previous topic - Next topic

veebee

Is it just me/ my connection, or is the MW site down and no work getting through ??

I ran out of work sometime early yesterday... causing a terrible score for the da (for these two machines).

Does anyone know of a proxy we can access it by ?

Dingo

No the web site is down as well and I do not know if there is a proxy.  I guess you will have to crunch another GPU project for a while.  biggrin


Radioactive@home graph
Have a look at the BOINC@AUSTRALIA Facebook Page and join and also the Twitter Page.

Proud Founder and member of BOINC@AUSTRALIA

My Luck Prime 1,056,356 digits.
Have a look at my  Web Cam of Parliament House Ottawa, CANADA

Dataman



JugNut

Excellent, nothing beats seeing the results of your efforts..

Cheers ..JN..


 - Participated in AA's 27 - 55 & Team Challenge # 1.
My team (Boinc@Australia) stat's
My personal stat's


     Crunching today for a better tomorrow...

Dataman

Apology for recent bad batches of workunits
Hi Everyone,

Just wanted to send out an apology for all the problematic workunits being sent out lately. This was mostly my fault -- we have quite a few new students using MilkyWay@Home for their research -- and the code to start up new searches wasn't doing a very good job of ensuring the quality of the input files they were submitting to it.

We didn't have much problem with this in the past as it was mostly just me and Matt Newby submitting jobs and we knew what we were doing, but the client applications are rather finicky about extra whitespace and things like that in the input files, and this was causing a lot of the crashing workunits.

I'm in the process of updating the search submission code to be a lot more robust and catch these errors before sending things out, so hopefully this won't be as much of an issue in the future (hopefully not an issue at all!).

So I again I want to apologize for the lack of robustness in some of my code that was causing the crashes in the last few days. We're looking into the issue that's causing the las bit of errors that seem to be happening out there (it looks like there's some error in the client code that is causing NANs with certain input parameters, which results in the client reporting an error for the workunit). So I hope we can get that cleared up soon as well.

Happy crunching!
--Travis14 Oct 2012 | 22:11:37 UTC ยท Comment