I now have two tasks with download problems --- HTTP error

The first started on 22nd
wah2_eas50_n1aw_201212_12_567_011011995_1

Tue 23 May 10:06:30 2017 climateprediction.net
Temporarily failed download of wah2_data_8.24_i686-apple-darwin.zip: HTTP error

Still trying to download

The second tried to download today 27th
wah2_cam50_iyfu_193012_12_574_011032453_1

Sat 27 May 02:32:38 2017 climateprediction.net
Temporarily failed download of wah2_8.24_i686-apple-darwin: HTTP error
Backing off 3 hr 52 min 17 sec on download of wah2_8.24_i686-apple-darwin

Still trying to download

Any one else with this problem ?

Mac El Capitan

I have successfully downloaded a task from the same batch as the second one you list yesterday eat 17:34 UTC so if general problem that narrows down the time scale a bit. However as the only tasks available at the moment seem to be retreads indicated by the _1 or _2 at the end of the task name it may take a while to get some more info on this.

The task wah2_cam50_iyfu_193012_12_574_011032453_1 failed first time around due to a missing library on a Linux box, I haven't checked the other one.

The other possibility is that it is only a problem on the Apple OS with the requisite files not being where they should be on the server.

I now have a third task with the same problem.

Sun 28 May 21:12:59 2017 climateprediction.net Started download of wah2rm3m2t_um_8.24_i686-apple-darwin.zip
Sun 28 May 21:13:00 2017 Project communication failed: attempting access to reference site
Sun 28 May 21:13:00 2017 climateprediction.net Temporarily failed download of wah2rm3m2t_um_8.24_i686-apple-darwin.zip: HTTP error
Sun 28 May 21:13:00 2017 climateprediction.net Backing off 1 hr 20 min 58 sec on download of wah2rm3m2t_um_8.24_i686-apple-darwin.zip
Sun 28 May 21:13:01 2017 Internet access OK - project servers may be temporarily down.

My system, the client, has submitted an HTTP request message to the server requesting a new task. This has must have been accepted since my system now has the information to request a download. (That's how it appears to work)

So since my system, the client, has successfully communicated with one of the CPDN servers with an HTTP request and received a response message, it doesn't appear to be a client end problem, as far as I can see.

If the location of the requisite files is in error, again, I would have said it can't be a client end error.

Since an HTTP session is a sequence of network request-response transactions, then in this case the client has made a request based on prior information contained in an earlier response, which then throws an error at the client end owing to the location identifier not being recognised.

All a bit strange.

Well, looking in the Task list under my computer, I find I have a total of 12 tasks registered as 'in progress'.
Five are reissues, other seven are new issues. These seven include the three which are are currently showing up on my BOINC management screen.

Nine of the total were tasks that I received before the system glitches and which continued to hang (not downloading) after the system was up and running again, which led me to aborting them.

Anyone any ideas? Will the system admin guys eventually delete the references to the aborted tasks?

Based on previous experience, it may take a year or more before references to the tasks go if you do nothing.

Best chance is I think, wait till you are out of work, then detach and re-attach to the project. Unless anyone with a more detailed knowledge of BOINC server side activities has a better idea?