I have 2 files in limbo awaiting the problems (read in News and Announcements) to be corrected. I cant really suspends Boinc network activity as my other projects wu's are completed very often. I've suspended CPDN so as to not cause more hammering off the "non existent" server but what do I do about these 2 that are trying to upload other than terminating boincs network activity?

... but what do I do about these 2 that are trying to upload ...

Not a lot really. Pray, keep your fingers crossed, worry a bit. :)

The real problem is 14 days after BOINC first attempts to upload; this is when it will give up and abort the file(s).

There was a way to extend this time, but I'm not sure if it will still work, as it involves editing client_state.xml, and the structure of this has changed.
I stopped all of my nearly finished models before they reached the end, so I can't check myself.
Could you please have a look at that file, (perhaps make a copy of it and look at that), and try to find persistent. The file string will be <persistent_file_xfer>, and is inside a <file_info> section.
If it's there, please copy all of it, including the <file_info> lines at the start and finish, and paste it here.

Since there are still few servers running,would it be possible to make redirect to those running,so uploads could go there until resolution of situation?

OK, good.
Thanks Rick.

I was concerned about the location in relation to the signed area.
If it was inside that, it would mean that it couldn't be altered. But it can.

So, I think the thing now is to wait for Tuesday, to see what happens at Oxford.

I'm going to hide your reply to keep the signed part hidden. Just in case. :)

Klimax

Yes, that's a possibility. It worked last time, back in 2005.

Klimax

Yes, that's a possibility. It worked last time, back in 2005.

Didn't know that it was already used,but it did not suprise me.

OK, good.
Thanks Rick.

I was concerned about the location in relation to the signed area.
If it was inside that, it would mean that it couldn't be altered. But it can.

So, I think the thing now is to wait for Tuesday, to see what happens at Oxford.

I'm going to hide your reply to keep the signed part hidden. Just in case. :)

Ok thanks. Not sure what or that signed area is ... or what it does ... or ...

Ill assume you know best. lol

Will wait for Tuesday and let you know what happens.

---

Rick

Unable to upload:
07.06.2009 14:37:00 climateprediction.net Temporarily failed upload of hadam3p_n8ek_1959_2_006159382_2_3.zip: connect() failed
07.06.2009 14:37:00 climateprediction.net Backing off 3 hr 10 min 10 sec on upload of hadam3p_n8ek_1959_2_006159382_2_3.zip
07.06.2009 14:37:02 Internet access OK - project servers may be temporarily down.
07.06.2009 15:10:13 climateprediction.net Started upload of hadam3p_n8ek_1959_2_006159382_2_2.zip
07.06.2009 15:10:15 climateprediction.net [error] Error reported by file upload server: Server is out of disk space
07.06.2009 15:10:15 climateprediction.net Temporarily failed upload of hadam3p_n8ek_1959_2_006159382_2_2.zip: transient upload error
07.06.2009 15:10:15 climateprediction.net Backing off 1 hr 36 min 34 sec on upload of hadam3p_n8ek_1959_2_006159382_2_2.zip
07.06.2009 15:13:00 climateprediction.net Started upload of hadam3p_n8cn_1997_2_006159313_2_2.zip
07.06.2009 15:13:01 climateprediction.net [error] Error reported by file upload server: Server is out of disk space
07.06.2009 15:13:01 climateprediction.net Temporarily failed upload of hadam3p_n8cn_1997_2_006159313_2_2.zip: transient upload error
07.06.2009 15:13:01 climateprediction.net Backing off 3 hr 56 min 58 sec on upload of hadam3p_n8cn_1997_2_006159313_2_2.zip

What about the deadline? Did i waste some hours?

Unless you've been trying to upload for days, you're nowhere near the 14 day deadline yet.

---

Backups: Here

What about the deadline? Did i waste some hours?

Im not sure the deadline matters to much. From what I understand Boinc will continue to try to upload for 14 days before giving up on the unit.

In the News and Announcements Thread it states;

"we've had another server (uploader1.atm) suffer a power supply failure and another (uploader.oerc) is short on space as well. I've already taken steps to rectify all these problems but it's likely to be quite slow and I expect at least a week before I can receive any new servers and Tuesday until a replacement power supply arrives."

If all gets fixed within that 14 day window we should all be able to upload our files.

Correct me if Im wrong on that anyone.

Edit: Beat me to it Les

---

Rick

Have the same problem with one Wu... transient upload error

<persistent_file_xfer>
<num_retries>17</num_retries>
<first_request_time>1244389189.966999</first_request_time>
<next_request_time>1244414613.637652</next_request_time>
<time_so_far>81.078375</time_so_far>
<last_bytes_xferred>0.000000</last_bytes_xferred>
</persistent_file_xfer>

I guess, if I edit <time_so_far> to zero, it'll be okay for more than 14 days...

Or maybe its better to copy <next_time_request> to <first_time_request> ???

Cheers...

---

My NEW BOINC-Site

Why people joined BOINC Synergy...

I too am having transient upload errors on 2 zip files, as follows, but TRICKLES are still being successfully made:-

Sun 7 Jun 23:30:00 2009 Resuming network activity
Sun 7 Jun 23:30:00 2009 climateprediction.net Sending scheduler request: To send trickle-up message.
Sun 7 Jun 23:30:00 2009 climateprediction.net Not reporting or requesting tasks
Sun 7 Jun 23:30:01 2009 climateprediction.net Started upload of hadsm3fub_kdk1_005982356_5_2.zip
Sun 7 Jun 23:30:01 2009 climateprediction.net Started upload of hadsm3mh_kqqk_006023920_4_1.zip
Sun 7 Jun 23:30:02 2009 Project communication failed: attempting access to reference site
Sun 7 Jun 23:30:02 2009 climateprediction.net [error] Error reported by file upload server: Server is out of disk space
Sun 7 Jun 23:30:02 2009 climateprediction.net Temporarily failed upload of hadsm3fub_kdk1_005982356_5_2.zip: connect() failed
Sun 7 Jun 23:30:02 2009 climateprediction.net Backing off 1 min 0 sec on upload of hadsm3fub_kdk1_005982356_5_2.zip
Sun 7 Jun 23:30:02 2009 climateprediction.net Temporarily failed upload of hadsm3mh_kqqk_006023920_4_1.zip: transient upload error
Sun 7 Jun 23:30:02 2009 climateprediction.net Backing off 1 min 0 sec on upload of hadsm3mh_kqqk_006023920_4_1.zip
Sun 7 Jun 23:30:04 2009 Internet access OK - project servers may be temporarily down.
Sun 7 Jun 23:30:05 2009 climateprediction.net Scheduler request completed: got 0 new tasks
Sun 7 Jun 23:31:03 2009 climateprediction.net Started upload of hadsm3fub_kdk1_005982356_5_2.zip
Sun 7 Jun 23:31:03 2009 climateprediction.net Started upload of hadsm3mh_kqqk_006023920_4_1.zip
Sun 7 Jun 23:31:04 2009 Project communication failed: attempting access to reference site
Sun 7 Jun 23:31:04 2009 climateprediction.net [error] Error reported by file upload server: Server is out of disk space
Sun 7 Jun 23:31:04 2009 climateprediction.net Temporarily failed upload of hadsm3fub_kdk1_005982356_5_2.zip: connect() failed
Sun 7 Jun 23:31:04 2009 climateprediction.net Backing off 1 min 0 sec on upload of hadsm3fub_kdk1_005982356_5_2.zip
Sun 7 Jun 23:31:04 2009 climateprediction.net Temporarily failed upload of hadsm3mh_kqqk_006023920_4_1.zip: transient upload error
Sun 7 Jun 23:31:04 2009 climateprediction.net Backing off 1 min 0 sec on upload of hadsm3mh_kqqk_006023920_4_1.zip
Sun 7 Jun 23:31:05 2009 Internet access OK - project servers may be temporarily down.
......
......
Mon 8 Jun 00:34:35 2009 climateprediction.net Backing off 48 min 56 sec on upload of hadsm3mh_kqqk_006023920_4_1.zip
Mon 8 Jun 00:36:47 2009 climateprediction.net Started upload of hadsm3fub_kdk1_005982356_5_2.zip
Mon 8 Jun 00:36:50 2009 Project communication failed: attempting access to reference site
Mon 8 Jun 00:36:51 2009 climateprediction.net Temporarily failed upload of hadsm3fub_kdk1_005982356_5_2.zip: connect() failed
Mon 8 Jun 00:36:51 2009 climateprediction.net Backing off 1 hr 49 min 34 sec on upload of hadsm3fub_kdk1_005982356_5_2.zip
Mon 8 Jun 00:36:52 2009 Internet access OK - project servers may be temporarily down.
Mon 8 Jun 01:00:00 2009 Suspending network activity - time of day

No doubt there will be no problem until we get near the 14 day limit and then we have to suspend all network activity?
THANKS to you all at 'head office' for all the good work there with limited facilities.

Keith

(P.S. Since making this message, I have decided to SUSPEND ALL NETWORK ACTIVITY until further news is heard about extra disk space becoming available as the DISK SPACE FOR TRICKLES IS ALSO LIMITED.)

The original instructions were as follows:

1. stop BOINC.
2. edit the client_state.xml file in your BOINC directory, taking a copy beforehand in case anything goes wrong. If the result name waiting to be uploaded is abcd_123456789 you need to search for that string in the file.
3. the search should find 6 occurrences inside <file_info> sections. Ignore the first one.
4. the other 5 should contain persistent file transfer blocks enclosed between <persistent_file_xfer> and </persistent_file_xfer> tags. Delete those tags and everything they enclose.
5. restart BOINC and you will now have another 2 weeks to complete the upload.

Note that the 6 in step 3, and the 5 in step 4, applied to the slab models, which was all that we had in 2005.

I'd suggest a full backup before trying this. :)

Yes, that's a possibility. It worked last time, back in 2005.

Les,

Not sure if you're referring to what I suspect (might be restating the obvious, in which case, apologies) - some while back (probably was 2005) in the early days of the project there was a process for manually uploading the zip files so the project admins could ensure no results were lost. They would then manually set the individuals stats to show "task completed" whilst ensuring full credit was given for the work done.

Having said that, file sizes for some of the more recent applications seem to be significantly larger and, with more people crunching more for the project, I wonder whether that would still be an option.

For example, I have four runs actually or nearly finished and, of the two for which I'd saved out the eight resulting zip files (long memory suggested there might be a problem before I read this thread), the combined file size was pushing 50MB (and will double for the remaining two applications nearly/actually completed today).

Not sure what I'm trying to impart (other than sharing an old experience) but I do wonder whether an interim, manual upload process would be practical (assuming, of course, there's somewhere to store the results)?

Cheers
Dave

---

Hi everybody with files that won't upload.

Until now every time there's been a file upload problem the programmers in Oxford have solved the server disk space issue before the BOINC 14-day limit. We know that Milo is already doing everything he can. I am confident that he will succeed again.

Yes, there's a manual upload tool but we generally only use it for particular beta testing files that Tolu needs to study. The manual tool unfortunately gives the programmers (and there are only two of them!) extra work.

The files waiting in the BOINC Transfers tab, whether already partially uploaded or not, are a nuisance and a worry. It's no use trying to make them upload because they can't and won't.

So the advice in the recent News thread posts remains valid. There's a link to it in my signature.

* If possible suspend models in the Tasks tab before they complete.

* Keep BOINC network activity suspended as much as possible to prevent repeated failed file upload attempts by BOINC.

* Subscribe to the News thread by clicking the button at the top of the thread to receive an email whenever we add a new announcement.

---

Cpdn news

Until now every time there's been a file upload problem the programmers in Oxford have solved the server disk space issue before the BOINC 14-day limit. We know that Milo is already doing everything he can. I am confident that he will succeed again.

Thanks, Mo.
The current situation is that there is apparently some money that I can spend, and I have a quote for a suitable server, but before I can send the order I require a signature on a form. When I will be able to get that is at present unknown. Usually, orders for servers take about a week once sent.

Unfortunately, switching uploads to other systems isn't a possibility at the moment as there isn't enough space anywhere.

Ideally I would like to have new servers in place before we run out of space, but managing to secure money in time to do so is very difficult.

Thanks, Mo.
The current situation is that there is apparently some money that I can spend, and I have a quote for a suitable server, but before I can send the order I require a signature on a form. When I will be able to get that is at present unknown. Usually, orders for servers take about a week once sent.

Unfortunately, switching uploads to other systems isn't a possibility at the moment as there isn't enough space anywhere.

Ideally I would like to have new servers in place before we run out of space, but managing to secure money in time to do so is very difficult.

Thanks for the Update.

I appreciate the work you guys do and can imagine the bureaucratic layers that must be gone through in order get the job done.

Happy Paper pushing until the "real work" can continue

---

Rick

* If possible suspend models in the Tasks tab before they complete.

Unfortunately, I am reading this recommendation to late - since 6 June my hosts finished 3 tasks: 2 HADAM3P and 1 HADSM3, and now I have 3 limbo-uploads.
That is too bad... :o(

---

The advice to suspend models before they complete was a just recommendation. Lots of members are in the same position as you. If you now suspend BOINC network activity as much as possible you will avoid most of the messages about the servers being down. That's also a recommendation and not obligatory!

Some people who don't look at their models or their BOINC or the forums have probably received a large number of these BOINC messages about the servers but still don't realise there's a problem.

---

Cpdn news

The advice to suspend models before they complete was a just recommendation.

Yes, a recommendation, but very good. :-) For "to be in a safe position".