I completed a model today and the computer get two right after that. If you are having problems getting work and have one running it appears that the server code will reset your quota when one gets turned in. That looked good after weeks of not being able to get a 2nd model.

---

Keep on crunching Pizza@Home

Hi,

I have recently begun to have problems with CPDN. The tasks appear to be ending prematurely, as indicated by these messages from the log:

Tue 20 Jul 04:59:39 2010 climateprediction.net Resuming task famous_u2sa_1999_200_006636453_3 using famous version 611
Tue 20 Jul 05:19:29 2010 climateprediction.net Sending scheduler request: To send trickle-up message.
Tue 20 Jul 05:19:29 2010 climateprediction.net Not reporting or requesting tasks
Tue 20 Jul 05:19:31 2010 climateprediction.net Scheduler request completed
Tue 20 Jul 05:20:12 2010 climateprediction.net Computation for task famous_u2sa_1999_200_006636453_3 finished
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_1.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_2.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_3.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_4.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_5.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_6.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_7.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_8.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_9.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_10.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_11.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_12.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_13.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_14.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_15.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_16.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_17.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_18.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_19.zip for task famous_u2sa_1999_200_006636453_3 absent
Tue 20 Jul 05:20:12 2010 climateprediction.net Output file famous_u2sa_1999_200_006636453_3_20.zip for task famous_u2sa_1999_200_006636453_3 absent

There is plenty of disk space available, so that isn't the problem. This is then followed by the problem of not being able to get any new tasks.

Tue 20 Jul 05:21:17 2010 climateprediction.net Sending scheduler request: To fetch work.
Tue 20 Jul 05:21:17 2010 climateprediction.net Reporting 1 completed tasks, requesting new tasks
Tue 20 Jul 05:22:22 2010 climateprediction.net Scheduler request failed: HTTP gateway timeout
Tue 20 Jul 05:23:27 2010 climateprediction.net Sending scheduler request: To fetch work.
Tue 20 Jul 05:23:27 2010 climateprediction.net Reporting 1 completed tasks, requesting new tasks
Tue 20 Jul 05:23:35 2010 climateprediction.net Scheduler request completed: got 0 new tasks
Tue 20 Jul 05:23:35 2010 climateprediction.net Message from server: No work sent
Tue 20 Jul 05:23:35 2010 climateprediction.net Message from server: (reached daily quota of 2 tasks)

So I am left crunching only 1 task, when I could be crunching two. The task list for my computer (1030318) shows that I am currently working on 2 tasks, but BOINCManager (6.10.56) only has one. I don't know what happened to WU#6836538.

I will detach from CPDN once my one remaining task completes, then wait a few days and re-attach and see what happens then.

Hi m2a2b2, welcome to the forum

Don't worry about task 6836538 which never made it the whole way into your Boinc manager. Everyone has the occasional phantom task.

Your computer's task list is here. I've looked at the last 3 crashed FAMOUS tasks and clicked on their stderr out + to show the Boinc messages. All 3 message sets include either INVALID THETA or NEGATIVE PRESSURE. This means there was an instability in these models' initial parameter values. The FAMOUS researchers are pushing the envelope with regard to parameter values to see what works and what doesn't. So the crashed models are useful to them.

If you look at the forum News thread at the top of this Number Crunching section you'll see, a few posts before the end, a description of the FAMOUS models where this is mentioned. It's worth subscribing to the News thread (and enabling email notification in your account) to receive an email every time there's an extra News post as that's where we explain what we think members need to know.

Re your computer's so far unsuccessful work fetch. The HTTP gateway timeout will have been due to intermittent connection problems which have been the fault of the server. Milo was going to see what he could do about it today so let's hope everyone sees less of this in future.

Since the server's Boinc version upgrade many computers have been having problems fetching enough new work. I won't go into details, but basically there are defects in this Boinc server version; they affect work fetch.

To try for new models:

* make sure that in the Boinc manager Projects tab CPDN is set to Allow new tasks

* in the Boinc manager Advanced menu select Preferences. In the Network usage tab look at the Additional work buffer. If it says less than 10 days, edit it to 10 and click OK

* the editing to 10 days may cause a flood of work from other projects. If you don't want this, set your other projects to No new tasks before you increase the number of days

* sometimes it helps to suspend all the tasks that are NOT from CPDN, leaving temporarily idle cores. Then in the Projects tab highlight CPDN and click Update. This may work or may not, but when you've seen what happens you can restart the tasks from other projects

Hope that helps.

---

Cpdn news

Hi mo.v,

I tried suspending the other projects, then bumping the buffer to 10 days. No luck. I waited for the current task to complete. It didn't take long, since it ended prematurely. I then detached from the project and re-attached. That took care of the phantom task, but I still can't get anything from the project.

Fri 23 Jul 07:45:11 2010 climateprediction.net Master file download succeeded
Fri 23 Jul 07:45:17 2010 climateprediction.net Sending scheduler request: Project initialization.
Fri 23 Jul 07:45:17 2010 climateprediction.net Requesting new tasks
Fri 23 Jul 07:45:20 2010 climateprediction.net Scheduler request completed: got 0 new tasks
Fri 23 Jul 07:45:20 2010 climateprediction.net Message from server: No work sent
Fri 23 Jul 07:45:20 2010 climateprediction.net Message from server: (reached daily quota of 1 tasks)

Is there anything else I can do from my end?

It looks like things have finally sorted themselves out for me after getting one more failure:

Fri 23 Jul 19:03:21 2010 climateprediction.net Message from server: Server can't open database

After waiting one more hour, I now have two tasks that I can merrily crunch.

Me too,

greetings


Bonsai911

---

26.07.2010 16:54:22 climateprediction.net work fetch resumed by user
26.07.2010 16:54:27 climateprediction.net update requested by user
26.07.2010 16:54:30 climateprediction.net Sending scheduler request: Requested by user.
26.07.2010 16:54:30 climateprediction.net Requesting new tasks for CPU and GPU
26.07.2010 16:54:35 climateprediction.net Scheduler request completed: got 0 new tasks
26.07.2010 16:54:35 climateprediction.net Message from server: No work sent
26.07.2010 16:54:35 climateprediction.net Message from server: (reached daily quota of 4 tasks)

Me too,

greetings


Bonsai911

---

See my post on this further down this thread, here.

Best advice at present:
Ignore whatever is in Daily quota; that's a left over from the old server code.
If you have problems getting new work, set your Maintain enough work for an additional to the max of 10 days. (Possibly won't work immediately if you're already having problems.)
DON'T abort extra work that you get! That (those) models count against your "daily" quota.
Wait patiently until you get some models.

---

Backups: Here

DON'T abort extra work that you get! That (those) models count against your "daily" quota.

Question: When these models crash (as they are wont to do), does that also count against your daily quota?

Yep!

---

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

Back to square 1. The two tasks that I managed to get two days ago are now done, so I am back to having no CPDN tasks to crunch. I think my daily quota should be 8 (2 processors * 4 WU per day), but I can't even get 1. I did set my buffer to 10 days, but that doesn't do anything for me.

I think my daily quota should be 8 (2 processors * 4 WU per day)

It's now something like: 2 processors * 4 WU per day * number of applications

The only cure is patience. And letting your computer contact the project servers constantly.

---

Backups: Here

It's now something like: 2 processors * 4 WU per day * number of applications

This depends on if CPDN has upgraded their scheduling-server again or not, since the code at start of June didn't scale by #cpu's...

Hmm, doing a quick test, I quickly hit:

28.07.2010 15:19:59 | climateprediction.net | Scheduler request completed: got 0 new tasks
28.07.2010 15:19:59 | climateprediction.net | [sched_op] Server version 611
28.07.2010 15:19:59 | climateprediction.net | Message from project server: No work sent
28.07.2010 15:19:59 | climateprediction.net | Message from project server: (reached daily quota of 3 tasks)
28.07.2010 15:19:59 | climateprediction.net | Project requested delay of 38229 seconds
28.07.2010 15:19:59 | climateprediction.net | [sched_op] Deferring communication for 10 hr 37 min 9 sec
28.07.2010 15:19:59 | climateprediction.net | [sched_op] Reason: requested by project


This small log-snippet tells two things, CPDN haven't applied the change restoring scaling by #cpu's from 15.06, since if they had the minimum possible quota would be 8 for my computer. Also, the very long "Project requested delay of" 10 hours, 37 minutes and 9 secounds cleary shows CPDN still uses the old code of deferring computers when hitting daily quota until midnight server-time + randomly 1 hour. This code was removed 02. June 2010.

While CPDN haven't done a full server-upgrade with more resent code than 02.06.2010, hopefully they've atleast applied the other bug-fixes to the quota-system. If not, no wonder it's a total mess, since the quota-code as of 01. June included many bugs fixed in later code.


But anyway, until CPDN upgrades their scheduling-server, the max quota is:
4 WU per day * number of applications.
Since currently only Famous is available, this means max quota is 4 WU's per day, regardless of this being a shiny new 12-"core" i7-980 or an old single-core cpu.

The quota formula is not being applied in my case.

I have not had a single work unit for over a week now and am getting the following:
28/07/2010 19:45:20 climateprediction.net update requested by user
28/07/2010 19:45:22 climateprediction.net Sending scheduler request: Requested by user.
28/07/2010 19:45:22 climateprediction.net Requesting new tasks
28/07/2010 19:45:37 climateprediction.net Scheduler request completed: got 0 new tasks
28/07/2010 19:45:37 climateprediction.net Message from server: No work sent
28/07/2010 19:45:37 climateprediction.net Message from server: (reached daily quota of 2 tasks)

---

Warped

Have your read my posts here and here about this matter?

---

Backups: Here

I've now copied my 2 posts to a new post, and made it a sticky.
See: Why can't I get more work? near the top of Number crunching.

Thanks Les.

I left the machine to try overnight and it got one just after midnight.

Patience is a virtue!

Milo has done a new version compile of a couple of daemons to do with downloading, so please see if you can get new work now.