Sorry, but unfortunately uploader.oerc is still not ready; it is being much slower than I expected.
I will, of course, bring it back on line as soon as I am able.

I had all four climate prediction jobs terminate unexpectedly and had to start new ones.

Even so I have the same problem with uploading. I have 6 x hadam3p queuing up for upload for over a week...

Any ideas on when the server will be back on-line?

Bill H

Bill

Where are the 6 tasks "queueing up"?
Are they zip files in the Transfers page?
You seem to have 4 tasks in progress and all others have been uploaded.
No doubt these are the ones you have just downloaded after the unexpectedly terminating tasks.

Keith

Bill

Are you looking at the "Pending Credits"?

It has been mentioned many times that CPDN does not use or amend the Pending Credits, and they should not be displayed by BOINC Manager when running CPDN, and deleting that display is an amendment that is overdue.

Keith

I've got 4 zips waiting in transfers in my Linux-setup and another 4 in my Win 7-setup, all backing off and reporting the project servers are down when trying to upload. Trickles report without a problem. The Win 7-setup has its deadline in 15 days.

---

I understand this has been discussed before, but I believe I am having a similar issue. Unfortunately, because the famous models that have completed will not upload, the finished hadam3p models and trickels are getting stuck in the queue and can't upload either (If there are only Hadam3p models present, they upload fine as the FAMOUS ones are not stuck in front of them.

This has led to having a major backlog of models on several of my machines. I am hoping the models will be able to upload normally soon, but I am considering aborting the finished models if much more time goes by without them going through.


This is a screenshot showing my upload Transfer page in the BOINC manager



Current tasks:



Any ideas on if/when uploading functionality would be restored, or any possible solutions on my end?

Note: this is not a localized problem on one machine. Every single PC I've checked that I have running models is not able to upload FAMOUS at this time. [/url]

The upload server for FAMOUS models, Kraken, was getting full some time ago, and data was in the process of being transferred, when the OeRC department at the University of Oxford changed their IP addresses. This change was long planned, but the timing was unexpected on "our" part. Among the servers affected was Kraken, so no more data transferring was possible until the IP issue was resolved.

As there are no programmers with the project at present, as mentioned in several other places, problems are being dealt with after hours by Milo, and by another software engineer who is trying to look after cpdn until the new programmers arrive which will be some time in February.

As to when models will once again be uploading, the best guess is that this will occur "sometime in the future". Hopefully the 'near' future.

---

Backups: Here

Update:

Milo found that the firewall for Kraken hadn't been updated after the change of IP.
This has now been fixed.

---

Backups: Here

Good news, everyone! For the first time in many days, my famous models are uploading! Thanks everyone at CPDN who helped to fix the problem.

Now I wish I hadn't cancelled several finished famous models that were "clogging the tubes" so to speak.

Lets just hope the server doesn't get hit too hard from the surge of people now trying to upload models...

Hi,
I have a problem with uploading some of the *. zip files. These files are from the old WUs, and also from the newer. For example, for one of the PC it is more than 30 files from 12 WUs.
This problem affects only CPDN project.
Repeated transfers some files take up to several hours, but still without success. Overall it is a 5 PCs that are connected through a proxy server. This problem has persisted for several months. To improve the transmission does not help either in setting file cc_config:
- <cc_config>
- <options>
<http_1_0> 1 </ http_1_0>
</ options>
</ cc_config>

Other PC, attached outside the proxy, the problem with uploading files do not.

Can someone help?

---

It's possible that a different cc_config option will help. See this post by Thyme Lawn on our php board for info.

This problem has persisted for several months.

After 3 months BOINC gives up and aborts the work units, so then you won't have a problem. :)

PS
Kraken, the file server for the zip files from FAMOUS models, is down at the moment, as per the post in News and Announcements.

---

Backups: Here

I tried, but unsuccessfully

---

Is there some problem with the servers? Server status shows all are up and running, but, hadam3p_pnw_ze5s_1975_1_006958472_0 can’t upload zip.13. Is kraken.oerc overloaded again?

---

Kraken has been uploading fine for me. Don't know about the other upload servers.

Uploader1 is down and is now the destination for PNW #13 zip files. (Three loiter on one of my machines.)

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

My machines are unable to upload since almost 2 weeks now. Do we still have to reset the upload deadline as described here, or has this limit of 14 days been increased in BOINC?

---

If you are using BOINC Manager 6.10.58, which you are, then the deadline for uploading is very long - 90 days or something similar.

All but the #13s (as expected) are uploading fine for me.

Chuck

---

Things have been much less traumatic since the Boinc upload timeout limit was increased from 2 weeks to 90 days. Remember when Milo had 3 upload servers out of action within days of each other and then just days before the deadline a replacement he ordered was delivered to the wrong address?

Chuck, what does your avatar show? Is that a shop?

---

Cpdn news

Just wondering, are the lost credits (I reverted back to where I was around 2/21) going to be found in the restore efforts?

Also, I for one am hoping that a large chunk of the massive data store you folks have was moved to near line storage so that it doesn't have to be backed up with your back up routines. With the multiple TB of data you were trying to backup every day, the backup routine was starting to get like a counterinsurgency operation -- 'sir, we had to destroy the village to save it'.

---