Hello,
Since some days I'm not getting any further workunit from any boinc project.
I got Boinc 5.2.13 on Win2k Pro and subscribed the following projects:
BBC Climate Change Experiment
rosetta@home
boincsimap
climateprediction.net
Einstein @home
LHC@home
QMC@home
SETI@home
SZTAKI Desktop Grid

I try updating these projects and/or rebooting, scheduler requests (when I update) succeed, but no new workunit is downloaded.
The only project running now is climateprediction.net, since it doesn't often require new workunits to work on.

Any idea about what the problem is?

Thanks darkpella

---

Are you completely out of work on all of those projects? You have divided your machine's attention into a lot of directions. Given the various deadlines for the various projects, your machine was probably in "earliest-deadline-first" mode earlier in the week. You will see a message to that effect in your messages tab.

What this means is that the BOINC manager's best guess is that your machine can't handle any more work right now. It needs to get some of the older WUs completed before bringing down more work, or it may miss some of the deadlines.

As long as you have work to crunch on, this is normal, and will resolve itself over the next few days as WUs are completed.

What tends to happen is that the machine goes to earliest-deadline-first and then basically ignores Climate (i.e. the deadline that's furthest away). Sometimes for days. You've told BOINC what you want the resource share to be for each project, and it keeps track of the time it has borrowed from Climate to meet earlier deadlines of other projects. So, now BOINC has decided it's going to spend some time catching up on climate work so that it does, overall, get the resource share you've defined. During that time, it doesn't need any WUs from other projects, because it's not planning to allocate any time to them anyway. Once you get a day or so of crunch in on climate, BOINC will come up for air and seek work from other projects again.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

Are you completely out of work on all of those projects? You have divided your machine's attention into a lot of directions. Given the various deadlines for the various projects, your machine was probably in "earliest-deadline-first" mode earlier in the week. You will see a message to that effect in your messages tab.

What this means is that the BOINC manager's best guess is that your machine can't handle any more work right now. It needs to get some of the older WUs completed before bringing down more work, or it may miss some of the deadlines.

As long as you have work to crunch on, this is normal, and will resolve itself over the next few days as WUs are completed.

What tends to happen is that the machine goes to earliest-deadline-first and then basically ignores Climate (i.e. the deadline that's furthest away). Sometimes for days. You've told BOINC what you want the resource share to be for each project, and it keeps track of the time it has borrowed from Climate to meet earlier deadlines of other projects. So, now BOINC has decided it's going to spend some time catching up on climate work so that it does, overall, get the resource share you've defined. During that time, it doesn't need any WUs from other projects, because it's not planning to allocate any time to them anyway. Once you get a day or so of crunch in on climate, BOINC will come up for air and seek work from other projects again.

---

It looks like I am experiencing a similar problem, but my situation is slightly different. I have been running Rosetta@Home for many months, but recently had a hard drive failure. After a couple of days elapsed, I was up and running again with the latest version of BOINC. After 1 day of operation I stopped getting jobs because the system says that I am over-committed. The system is calculating that I am only running BOINC ~3% of the time, therefore any job will not finish within the deadline. This conclusion is incorrect. My PC is running BOINC 99%+ of the available time. I'm typically executing 8 hour jobs, and the system recognizes that the average turnaround time is currently 0.37 days. From my perspective, the system is using a flawed equation to calculate the system availability. Under the circumstances, I'm going to try executing smaller jobs until the calculated system availability improves.

---