The permanent http error is only happening to a few people, so is most likely a problem with their computer.

Well, taking a look on the wu's I've downloaded, while I've not had any download-errors myself the current results are:
90 wu's downloaded, of these:
38 error-free (atleast for now).
39 wu's with download-errors.
21 wu's with computing-errors.
48 total download-errors.
27 total computing-errors.
3 wu's errored-out due to too many errors.

43% of the wu's having download-errors is in my opinion too high, so even if only a "few" users has problems they're managing to generate lots of errors. Since atleast some of these users seems to have no problems crunching other BOINC-projects, it's a little strange if where's a problem with their computers.

Now I've not checked every download-error, but atleast the checked on was from users running BOINC-version 7.2.39 or 7.2.42. If this indicates either a problem with current BOINC-clients or CPDN's server-setup I've no idea about, it can also just be all errors didn't check is from different BOINC-versions.

BTW, appart for all the download-errors, 23% of wu's generating atleast one computing-errors seems on the high side to me.

There was a nasty bug in v7.2.39 which could be causing the download errors. v7.2.42 is a bug-fix - maybe the ones you're seeing with download errors and v7.2.42 have upgraded the client in the meantime? Can you check whether the individual failed tasks were attempted under v7.2.39, whatever client they're running now?

My boinc version is 7.2.39 and I'm getting massive download errors after 7 successful downloads. And to make it more difficult: I've not had any download-errors on beta, so it could be a mistake in the new batch or server.

---

When the ones I got the download errors with tried to download it was with 7.2.39
Following advice on the download errors thread, I suspended computation, exited BOINC then rebooted before restarting BOINC. I was then able to download three tasks. Since then, realising that there was a more recent version I have upgraded. I don't know if exiting boinc and rebooting works in every case however.

Thanks Les. I have decided to let the CM finish. It�s now up to 58% with 240 hours to go. It will be interesting to finish this one (if I can) since it has already failed 4 times.

---

I upgraded to 7.2.42. Hopefully this will solve the problem.

There was a nasty bug in v7.2.39 which could be causing the download errors.

Haven't been keeping-up with client-changes recently so wasn't aware of this.

v7.2.42 is a bug-fix - maybe the ones you're seeing with download errors and v7.2.42 have upgraded the client in the meantime? Can you check whether the individual failed tasks were attempted under v7.2.39, whatever client they're running now?

Did only find one of my wu's having someone reporting as v7.2.42 with download-error, it's host 1289490 and a quick look reveals 7 errors at the same time. Interestingly enough they're reported as "error" and not "download error". Also, it's only 6 minutes between being assigned and reported as error, so clearly someone manually hitting "update". While it's possible they did swap BOINC-client during these 6 minutes before reporting the errors, this info isn't available anywhere so...

Success! Either the reboot or the upgrade to 7.22.42 cleared the problem and I was able to download 9 hadam3p�s.

Somewhere along the way I also downloaded a reissue of a slightly used hadcm3n. And guess what, it is also a _4 on its last go round. I think that my computer is becoming the Elephants graveyard, where old WU�s go to die.

---

I like that. ;-)

In my experience on computer 1027409 going back several months, hadam3p_eu downloads invariably fail with permanent http error, while (e.g.,) pnw region wu's download and run correctly -- past numerous restarts, reboots and several BOINC version updates. Clearly I'm one of the treasured few.

I plan to reset the project in a day or so when my current hadcm3n_obpu task completes.

---

Best wishes:)

9 downloads are successfull after a reboot.

---

...I plan to reset the project in a day or so when my current hadcm3n_obpu task completes.

I doubt that a project reset has the same effect as a BOINC client restart. If there is an outdated IP cached, it will probably survive the reset, whereas a client restart always re-evaluates all IPs.

3 _eu_ models completred this morning - 71hours each. Next 3 going.

A few specs. about your machine would help. OS, type and speed of processor and amount of memory would make the time measurement more useful as a guide to others.

---

Nothing really special compared to some others. W7 Enterprise O/S, CPU i5-760 (2.8Ghz) 4Gb RAM. Does have the benefit of a fast internet though - 4.2Mb/sec d/load, 2.9Mb/sec u/load.

In my experience on computer 1027409 going back several months, hadam3p_eu downloads invariably fail with permanent http error, while (e.g.,) pnw region wu's download and run correctly -- past numerous restarts, reboots and several BOINC version updates. Clearly I'm one of the treasured few.

I plan to reset the project in a day or so when my current hadcm3n_obpu task completes.

Follow-up:
After project reset, four hadam3p_eu tasks downloaded successfully & are crunching :-D

B/w

Just ben looking through my results for the _eu_ units and noticed that four of mine had been previously issued to computer 1146043 and all had failed with a computing error at more or less the same point in the program. Even though it's not my machine does the owner need to look at? Maybe it just crashed.

Looking at server status this morning, not only are there more tasks in progress than I have seen for a long time but there are even more waiting to be sent!

I recently bought a Mac computer but I thought I would keep the old Windows machine running, doing nothing but climateprediction tasks. I also installed BOINC and climateprediction on the new Mac.

Now I see on the event log "Project has no tasks available".

Are there, in fact, no tasks being sent out out at the moment, or have I done something incompatible?

The place to look is the server status page. At the moment, there are no tasks 'ready to send'.

Tasks tend to be released in batches here: after each release, there is a glut available for a short while, but once people have collected them all, there's a dry period.

Other BOINC projects have a more steady-state supply of (usually) much shorter-running tasks. You could run some of those while you're waiting for the next batch release - just keep looking in at the SSP once in a while, to see what's available.

Thank you Richard