All of World Community Grid went off the air to include the Facebook app at around 22:00 CET (20:00 UTC).

Am newbie to BOINC. First project signed up for was WCG. Got into their home site once but not since. Not encouraging start to being part of this enterprise. Have Detached from WGC now & will try some other project instead. Irrelevant that BOINC & software works fine if projects you try & commit to can't keep their home field in order & this is I B M we're talking here

[ed: made BOINC caps]

Did you see the date of the message you quoted? That's almost a fortnight ago!

I didn't have any difficulties reaching their homepage just now.

Perhaps you should have asked for help before detaching.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

And please, if you do ask for help, do it outside of this thread. Forums enough around here. :-)

ClimatePrediction.Net should be back up & running. With the latest server code.

ClimatePrediction.net News and Announcements Milo Thurston Project administrator posted the following:

We've completed most of the work on the server that caused the recent outage on this board. If you encounter any further problems related to this, please post here

Thank you for your patience whilst we've been carrying out this essential work.

Yet another bad weekend in GPU processing land:

MilkyWay -- validator offline, no new work
Collatz -- ISP outage (again)
DNetC -- servers offline
GPUGrid -- lack of available work

MW -- problem started on Friday - might well last until the end of the weekend.

Collatz -- problem started this morning -- the only ongoing issue that Collatz has is ISP reliability -- which is a biggie and one not fixable at the project level.

DNetC -- problem surfaced after MW and Collatz -- I wonder if in part there is a GPU project loading issue -- with so few ATI GPU supporting projects, when two go offline for one reason or another, it seems the third follows.

Don't forget Seti which is mostly out of work. Not really a project outage, but close. ;-)

I got a strange message in BOINC when I updated SETI. I had two completed WU and nothing SETI to run. When I did the Update:

6/5/2010 10:34:58 AM SETI@home update requested by user
6/5/2010 10:35:02 AM SETI@home Sending scheduler request: Requested by user.
6/5/2010 10:35:02 AM SETI@home Reporting 2 completed tasks, not requesting new tasks
6/5/2010 10:35:03 AM SETI@home Scheduler request completed
6/5/2010 11:17:23 AM SETI@home Sending scheduler request: To fetch work.
6/5/2010 11:17:23 AM SETI@home Requesting new tasks
6/5/2010 11:17:25 AM SETI@home Scheduler request completed: got 0 new tasks
6/5/2010 11:17:25 AM SETI@home Message from server: (Project has no jobs available)

As you see, at 10:34, it reported, at my request, but did not request new tasks. At 11:17, on its own, it requested work, w/o success, as noted elsewhere here. What I find puzzling is that at 10:35, BOINC did not request new tasks. Is requesting new tasks not something done for a manual update? Did BOINC wait until 11:17, when it would normally have switched over from Rosetta to SETI to make the request? I just now forced an update on Rosetta and it reported 1 completed task and did not request new tasks, so that's probably it.

Please keep this thread free of questions about how BOINC works and post only about project outages. There's a whole forum outside this thread, where you can post a completely new thread with your question about why BOINC isn't showing the back-off time.

SETI@home - from their front web page - Our database is temporarily offline. Many website functions are not available. Please try again later.

Seti has a note up on the front page saying all downloads are stopped due to a bug in the new Fermi GPU science app. They error out and can validate against another fermi result putting bad results in the DB. Until the bug is fixed no new WU.

ClimatePredicton.net Project down for maintenance.

Collatz has been encountering some issues of late. Seems they are not ISP issues but server issues of some form or another (speculative guess on my part - with increased numbers of clients, the server hardware might be pushed).

Also, it seems to me that the project (which is a one person show) may be entering the 'admin ennui' phase that projects, particularly low resource projects often get after the start up new project adrenaline boost wears off. Collatz has been running for over nine months, so Slicker is to be appreciated for the length of time before he got to the 'ennui point'.

SETI has run out of raw Data this morning. The crew is in we may see new data soon

Pre-warning for an Einstein@Home outage:

David Hammer wrote:

Einstein@Home will be down for 20 hours on June 13 from 0300 to 2300 UTC. The entire University of Wisconsin - Milwaukee network will be down for upgrades at this time.

Further pre-warning for Einstein@Home:

Bernd Machenschalk wrote:

To get a clear shutdown instead of a connection failure we'll shut down the ABP part of the project already Saturday night and start it again Monday morning (CET). ABP uploads should be possible during that time, though. That means e.g. no ABP validation for a slightly longer period than the UWM network outage lasts.

BM

Seti and their website have gone AWOL.

Seti@Home is down for the count. Their forums are available, but most of the rest is down due to software upgrade problems. This will continue during the night, until the guys are back in the office today. Expect more maintenance outage time later on.

Collatz has gone AWOL again -- it isn't at all clear that the issues are ISP issues, though that might be part of the problem. It seems the outages are simply too frequent to be 'single cause' issues.

DNETC@HOME - Can't access web site or upload WU's

---