I've just upgraded my BOINC client from 4.25 to 4.43 and im having a little trouble. All of the work units and account settings etc have stayed intact, but the Climate Prediction project has been replaced by Einstein. By this i mean that whilst CPDN has retained its entry on the projects page and kept its work units, its name is now Einstein@Home. When updating the project, BOINC tries to contact the Einstein servers, which throw an error: invalid account key - obviously the account key has stayed intact whilst the project has not. Hopefully someone will be able to help?

---

An update:
I've disovered that the CPDN unit, currently attributed to the Einstein project is happily crunching properly, and the show graphics button shows the correct CPDN graphics.
It seems that the problem is that the name and scheduler address for CPDN have simply been replaced by those of Einstein. Is this easily fixable, or is a dettatch/re-attatch necessary (i dont really want to have to do this, with CPDN having such large units, and being near to the end of one)

---

If you're happy to edit files you can stop BOINC and edit client_state.xml in the BOINC directory (take a copy first just in case).

You need to search for the string <b>EinsteinAtHome_cgi</b>. You should find at least 2 occurrences. The one you need to change is inside the project block for climateprediction.net, where you need to change the <b>scheduler_url</b> line to

<b>&lt;scheduler_url&gt;http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi&lt;/scheduler_url&gt;</b>

Save the file, restart BOINC and the CPDN project update should work.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Thank-you very much. I made the edit: it seemed that there were two entried, one with the correct url and one just above it with the Einstein url. It seems that the first entry was taking precedence over the first.

After starting BOINC again, i updated climatepredition.net, and got the following messages:

24/05/2005 17:28:52|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
24/05/2005 17:29:13|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi failed
24/05/2005 17:29:13|climateprediction.net|No schedulers responded
24/05/2005 17:29:13|climateprediction.net|Deferring communication with project for 1 minutes and 0 seconds

Which i assume is due to a problem at the server end and not with my setup. When the update retried, i got the next set of messages:

24/05/2005 17:30:14|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
24/05/2005 17:30:15|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
24/05/2005 17:30:36|climateprediction.net|Master file fetch failed
24/05/2005 17:30:36|climateprediction.net|Deferring communication with project for 1 minutes and 0 seconds

I don't really know what this means - is it a problem at my end or the server? Is something still not quite right?

---

Each project has a master_url setting which tells BOINC where the master.html file for the project is. This file contains the list of schedulers that requests can be sent to.

It's likely that the master file fetch failure is temporary, but you could check that the CPDN project block in client_state.xml still has

<b>&lt;master_url&gt;http://climateprediction.net/&lt;/master_url&gt;</b>

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer