the forums at Rosetta have this problem in there number section.... lets hope is a temporary problem and gets fixed in the next 72 hrs.

SETI@home down for maintenance

SETI@home down for maintenance

???
Are you sure? As I see it, only the AP splitters are offline.

The outage notice on the homepage has either been forgotten or intenionally left there.

Gruß,
Gundolf

CPDN main project

Upload server climateapps3.oucs is still down. The server status page can be seen here. The programmers hope to have it running again within a couple of days.

Climateapps3 takes decadal zip files uploaded from HadCM models if the files end in an odd number eg _1 or _3. (HadCM files that end in an even number like _4 go to uploader.oerc which should accept them without problems.) Zip files from some HadAM (but not HadAM3P) models may also be affected.

While climateapps is down it would be a good idea to suspend Boinc network activity as much as possible. In the Boinc Transfers tab please do not press the Retry now button, and certainly not the Abort transfer button which would cause the file to be completely lost. Do not repeatedly suspend and reactivate Boinc network activity; your network connection will be fine.

If you wish you can suspend your HadCM and HadAM models until climateapps3 is running again. This would prevent these models creating more files.

CPDN main project

Milo has restarted climateapps3.oucs so all CPDN servers are now running.

The migration of the database to the new server has been postponed to next week at the earliest ie 10 August or later. This will involve a server shutdown. Please subscribe to a CPDN forum News thread (eg here) and in your account enable emails from the project to receive advance email notification of announcements about this.

Milo says that the combination of Carl's code revision and the new server has resulted in a credit calculation of around only half an hour. But the new scripts can only be activated when the new server starts running. Until then the old scripts will run but only about twice a week. So our credits will only be exported to the stats sites twice a week until the new server is installed.

CPDN main project

Upload server uploader.oerc has been down for several hours. The server status page can be seen here. Its disk has filled up while Milo's been transferring data from one server disk to another.

Uploader.oerc takes decadal zip files uploaded from HadCM models if the files end in an even number eg _2 or _4. (HadCM files that end in an odd number like _1 go to climateapps3 which should accept them without problems.) Zip files numbered _1 from HadAM3P models will also be affected. (HadAM3P files numbered _2 and _3 upload to different servers and should transfer without problems.)

While uploader.oerc is down it would be a good idea to suspend Boinc network activity as much as possible. In the Boinc Transfers tab please do not press the Retry now button, and certainly not the Abort transfer button which would cause the file to be completely lost. Do not repeatedly suspend and reactivate Boinc network activity; your network connection will be fine.

If you wish you could suspend your HadCM and HadAM3P models until uploader.oerc is running again. This would prevent these models creating more files.

CPDN main project

Uploader.oerc is now up and running.

CPDN main project

Milo has announced:

'We are replacing a database server starting this Sunday night around 10PM BST (5PM EDT/2PM PDT), so we will probably be down through Monday morning. This is a much needed upgrade and we appreciate your patience during this outage. The PHP bulletin boards will still be available (as will the main CPDN website), but the CPDN/BOINC database access (credits/trickles/new signups/etc) will not be available.'

I expect that zip file uploads will still be possible, but not trickles. The CPDN-BOINC forum will not be available.

Carl has also posted about the outage here.

CPDN main project

Amended time for start of outage

Milo and Carl are going to shut down the database server earlier than they originally planned. They now say:

We are replacing a database server starting this Sunday 5PM BST (12M EDT/9AM PDT) [16.00 UTC], so we will probably be down through Monday morning. This is a much needed upgrade and we appreciate your patience during this outage. The PHP bulletin boards will still be available (as will this website), but the CPDN/BOINC database access (credits/trickles/new signups/etc) will not be available.

It will not be possible to upload trickles, report completed models, visit our CPDN accounts or model web pages, use the CPDN-Boinc forum or fetch new work. The server status page will be down.

It will be possible to upload models' zip files, look at the Climateprediction website (except the Boinc part) and post on the independent forum.

You can allow your models to continue processing but may wish to suspend Boinc network activity as much as possible during the outage.

Carl has started forum threads about the outage here and here.

CPDN Main Project

Progress thru Processors seems to have taken off big time. Soon after the new server came on-line it was hit by 4,000 new PtP users, all attempting to download 100MB to run their first task. This sudden network load has effectively become a denial of service attack, making the server all but inaccessible. Carl and Tolu are feverishly working to mirror the downloads to reduce the server's network load. They are hoping that normal service will be resumed within a couple of hours.

Einstein is down at the moment. There is no information available as to the likely length of the outage. The only available information so far is a fairly terse email message from Oliver Bock which was posted some 10 hours ago, saying

Apparently our main file server has some issues again.
We're looking into it...

Einstein@home Project

There is a message on the home page that suggests the outage may last for several days :-).

---

Cheers,
Gary.

CPDN Main Project

The new scheduler and database server is now fully functional (at about 10 times the speed of the system it replaced). Work is only available for the HADAM3P application at the moment; work for the other applications is currently being generated to make use of the new mirrored download system and should start appearing soon.

Milo has finally managed to get all of the HADAM3P data he'd stashed away back on to a server where the results website can access it. At some point today he will be taking down uploader1.atm.ox.ac.uk to copy its data off to yet another new server. uploader1 is the destination for one of the HADAM3P result files (_3.zip) and uploading of that file will not be possible while the server is being replaced.

CPDN main project

Uploader1.atm upload server is still down and Milo doesn't think he can activate the new server until Friday. This server takes _3.zip files from HadAM3P models when they complete. These models' _1 and _2 files should upload without problems as they are allocated to different servers. While uploader1.atm is still down here are some suggestions:

- You could suspend Boinc network activity as much possible until the server's running.
- You could suspend your HadAM3Ps before they complete and generate their zip files.
- You could do nothing at all because we do not expect this outage to last much longer.
- Your network connection will be fine. Please do not repeatedly activate and suspend Boinc network activity.
- Do not use the Retry now button in your Boinc Manager Transfers tab. Repeated failed attempts are not good for files.
- Do not abort the file transfers or the models. They are all good!

The actual due dates is: "Finish them as quickly as possible, because the researchers want their results".
The long deadline date is a dummy value to try and prevent BOINC from going into panic mode.

Einstein

Update on their temporary front page:

Fri Aug 14 17:01:20 UTC 2009

The first attempt to fix the filesystem failed and the second attempt is
underway. We will have more news in about 36 hours.

EINSTEIN@HOME -

So are these sparse and vague little messages on the root index page, days apart, the best they can do?

I understand there is probably a lot of work to do, and too few to do it - who are either not paid, not paid enough or doing this at low priority relative to the tasks they are paid for...

But there are folks out here who also take a great interest in the projects - and to have so little information about what is going on just kinda sucks...

What else can we do to help?

this type of crash has happened before and is a issue which they are working on, be patient...


all projects have a bad time every once in a while.

EINSTEIN@HOME -

So are these sparse and vague little messages on the root index page, days apart, the best they can do?

Well lets see, its a weekend and instead of doing family stuff they have to spend it in the lab sending out for sandwiches and pizza. And they should sit composing polished HTML as well?

But there are folks out here who also take a great interest in the projects - and to have so little information about what is going on just kinda sucks...

I remember a lot of moaning at SETI@HOME which prompted this reply:

Matt Lebofsky wrote:

Matt Lebofsky
View profile
More options Jan 25 2001, 12:52 am

3.03 sucks so much because we cleaned up a bunch of sucking code in this version. We found several cases existed in 3.0 where the clients could process entire workunits without ever touching the suck functions. This was an undetected conflict between the science and suck code, and has been fixed in 3.03.
Now we are efficiently maximizing both science and sucking.
You are able to use 3.0 during random phases when I don't have mandatory upgrade messages turned on. I turn these on whenever I feel like it, and turn them off when 3.0 clients in tight loops load down our server. As of time of writing, you cannot download workunits with 3.0, but you may be able to later. Within a week, no matter what, 3.0 will be dead in the water. We can only accept results from suckless clients for so long.

- Matt - SETI@home