"Computing allowed"
1] while computer is in use
2] while processor usage is less than 0 percent

I'll change "Only after computer has been idle for" to 0 minutes, it was on 3.00mins.
{not entirely sure what this latter setting actually means or really remember why it was on 3.00}

So was there any definitive fix for this problem? I've got it too.

I found it impossible to install boinc in its own partition, as I've done since CPDN merged with boinc. Installation was also impossible as a 'service' unless all three options were accepted, including 'screensaver.'

It WAS tested and the results posted in that extinct thread.
I think that the person in question unpacked the zip/tar them self on arrival and before it had a chance to start, and manually checked the url.

cwhyl

This was discussed extensively on the old php board 2-3 years back when it first started happening. It was also tested a fair bit.

The files were/are OK on the server.
They're OK when they arrive zipped up on the user's computer.
At some point after unzipping and moving to their various locations, the data in the client_state.xml file shows up corrupted, in a couple of different ways.

So it's most likely a subtle bug in BOINC for a particular variety of Linux.

Make sure you have "leave applications in memory when suspended" OFF.

However... I think you have something like 2 weeks before the upload fails. So you can simply sit back & hopefully the project might make this same change at Rutherford.

It's all caused by a long period timer somewhere in the BOINC server code.
When the timer reaches the maximum value for that variable type, it overflows to zero, and BOINC thinks that it's a new data set, so it tries to issue it.

Just got another of these PNW tasks, (a re-issue) where some of the files didn't download and a permanent HTTP error ensued. What I can't remember is whether or not I need to delete the folder with the model or whether BOINC will do it given time?

(BOINC was designed on the assumption that two different computers processing a task would produce results that are identical, bit for bit. If this were true a simple comparison of results would be a useful check for correct data transmission. But climate models break that assumption.)

You have exploded an urban myth!

The time limit for uploading files from any project was extended. I can't remember whether the limit is now two or three months, but in any case it's far longer than we need.

But, but, but... each file is still only allowed 100 upload attempts, after which it expires. That's the BOINC rule. 100 is plenty but please don't use up the files' lives by repeatedly pressing the Retry now button in the Transfers tab. The files come to no harm while they wait.

For the "killer trickle" to be sent to the correct target, that target, i.e. climate model, needs to return a trickle_up file for the server to find it.
As has been said, this is unlikely to happen, so they CAN'T be killed from the server.

Uploads can stack up indefinitely and not be lost, true?

Or so I thought,
I have just been through a copy of clientstate.xml without finding a misspelling of handler. I am still getting the message Project file upload handler is missing.
I have tracked down the zip file in question in the .xml file but am afraid it makes little sense to me, other than that the file is not transferring which I could tell by looking @ the transfers tab.

I am quite happy for someone to point out something in the portion of the file which is bleeding obvious, even if not to me.

<upload_url>http://uploader1.atm.ox.ac.uk/cpdn_cgi/file_upload_handler</upload_url>
</file>
<file>
<name>hadam3p_eu_8h04_2000_1_007687181_0_4.zip</name>
<nbytes>13743083.000000</nbytes>
<max_nbytes>150000000.000000</max_nbytes>
<md5_cksum>41130e8681805ab6432ca43cea075478</md5_cksum>
<status>1</status>
<upload_url>http://uploader1.atm.ox.ac.uk/cpdn_cgi/file_upload_handler</upload_url>
<persistent_file_xfer>
<num_retries>14</num_retries>
<first_request_time>1327526537.473585</first_request_time>
<next_request_time>1328311850.488157</next_request_time>
<time_so_far>295.883478</time_so_far>
<last_bytes_xferred>0.000000</last_bytes_xferred>
<is_upload>1</is_upload>
</persistent_file_xfer>

Dave

My recommendation was based on what we have seen on cpdn. A Core i7 920 (hardly a high end processor) can beat a higher priced Phenom II X6 1100T in total throughput of models.

I don't think that the server version is sufficiently up to date for the "no gpu" code.

CC_config can apparently be set on user's computers to do the same thing.