CPDN server problems

[Desti]

http://climateapps2.oucs.ox.ac.uk/cpdnb ... hp?id=5447

I'm afraid there's now a different problem, with one of the Oxford servers. A CPDN HadCM coupled model has been unable to upload a 10-year zip file, getting the boinc manager message 'No space left on device/server'. This does not mean your computer disk is full. The server disk has filled up.

The problem may also affect HadCM trickles and HadSM slab zip uploads and trickles.

It would be a good idea for anyone running a CPDN model to suspend network activity in the Activity menu of boinc manager until the problem is resolved. The model can then safely run.

We realise this is difficult for multi-project crunchers who need to keep network activity enabled. They may prefer to avoid the problem by setting CPDN to No new work (using the button in the Projects tab) and suspending their model in the Tasks tab. Then crunch other projects' tasks until the problem is resolved.

It's best to avoid multiple failed uploads of zip files. These are produced at the beginning of December at the end of each decade (eg 1930, 2040) for HadCM and at the end of each 15-year phase for HadSM slabs.

BBC, CPDN beta and SAP models should not be affected by this problem.

The server status of all ClimatePrediction projects can be checked here:

CPDN
http://climateapps2.oucs.ox.ac.uk/cpdnb ... status.php
BBC
http://bbc.cpdn.org/server_status.php
Beta
http://climateapps1.oucs.ox.ac.uk/beta/ ... status.php
SAP
http://attribution.cpdn.org/server_status.php
____________


Milo confirms that the cpdn server is short of space and says it will take a day or two to fix. At the moment cpdn model trickles are being accepted by the server, but not zip file uploads. This has now been confirmed for all cpdn models, both coupled and slab. Please see the previous post for when your model will create its next zip file.

The best plan of action is to either

* suspend network activity well before you reach a zip file point

* or if you can't suspend network activity, suspend the model instead so it doesn't reach a zip file point while the problem lasts