why am i unable to get more wu's?

---

why am i unable to get more wu's?

We will need more information than this. Are you attached to multiple projects? If yes than Boinc may be repaying debt to other projects as per your resource share, before allowing more DL from this project or you could already have too much work on hand to meet due dates.
Stop and restart Boinc and post the Messages tab log might tell up was is going on. Also, copy the messages you get when you try to update the project.

---

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470

You need to ask that question on the projects website not here.....

---

BOINC Wiki

i'm attached to mulitple project's. i tried updating all of the project's i'm running here's what it say's in the message tab:

3/22/2006 1:42:45 PM||request_reschedule_cpus: project op
3/22/2006 1:42:47 PM|cpdn seasonal|Sending scheduler request to http://climateapps3.atm.ox.ac.uk/hadam3_cgi/cgi
3/22/2006 1:42:47 PM|cpdn seasonal|Reason: Requested by user
3/22/2006 1:42:47 PM|cpdn seasonal|Note: not requesting new work or reporting results
3/22/2006 1:42:47 PM||request_reschedule_cpus: project op
3/22/2006 1:42:48 PM||request_reschedule_cpus: project op
3/22/2006 1:42:50 PM||request_reschedule_cpus: project op
3/22/2006 1:42:51 PM||request_reschedule_cpus: project op
3/22/2006 1:42:52 PM|cpdn seasonal|Scheduler request to http://climateapps3.atm.ox.ac.uk/hadam3_cgi/cgi succeeded
3/22/2006 1:42:54 PM||request_reschedule_cpus: project op
3/22/2006 1:42:56 PM||request_reschedule_cpus: project op
3/22/2006 1:42:57 PM|rosetta@home|Sending scheduler request to http://boinc.bakerlab.org/rosetta_cgi/cgi
3/22/2006 1:42:57 PM|rosetta@home|Reason: Requested by user
3/22/2006 1:42:57 PM|rosetta@home|Note: not requesting new work or reporting results
3/22/2006 1:42:59 PM||request_reschedule_cpus: project op
3/22/2006 1:43:02 PM|rosetta@home|Scheduler request to http://boinc.bakerlab.org/rosetta_cgi/cgi succeeded
3/22/2006 1:43:07 PM|boincsimap|Sending scheduler request to http://boinc.bio.wzw.tum.de/boincsimap_cgi/cgi
3/22/2006 1:43:07 PM|boincsimap|Reason: Requested by user
3/22/2006 1:43:07 PM|boincsimap|Note: not requesting new work or reporting results
3/22/2006 1:43:12 PM|boincsimap|Scheduler request to http://boinc.bio.wzw.tum.de/boincsimap_cgi/cgi succeeded
3/22/2006 1:43:18 PM|climateprediction.net|Sending scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi
3/22/2006 1:43:18 PM|climateprediction.net|Reason: Requested by user
3/22/2006 1:43:18 PM|climateprediction.net|Note: not requesting new work or reporting results
3/22/2006 1:43:23 PM|climateprediction.net|Scheduler request to http://climateapps2.oucs.ox.ac.uk/cpdnboinc_cgi/cgi succeeded
3/22/2006 1:43:28 PM|Einstein@Home|Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
3/22/2006 1:43:28 PM|Einstein@Home|Reason: Requested by user
3/22/2006 1:43:28 PM|Einstein@Home|Note: not requesting new work or reporting results
3/22/2006 1:43:33 PM|Einstein@Home|Scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi succeeded
3/22/2006 1:43:38 PM|Predictor @ Home|Sending scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi
3/22/2006 1:43:38 PM|Predictor @ Home|Reason: Requested by user
3/22/2006 1:43:38 PM|Predictor @ Home|Note: not requesting new work or reporting results
3/22/2006 1:43:43 PM|Predictor @ Home|Scheduler request to http://predictor.scripps.edu/predictor_cgi/cgi succeeded
3/22/2006 1:43:48 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
3/22/2006 1:43:48 PM|SETI@home|Reason: Requested by user
3/22/2006 1:43:48 PM|SETI@home|Note: not requesting new work or reporting results
3/22/2006 1:43:55 PM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
3/22/2006 1:43:58 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
3/22/2006 1:43:58 PM|SETI@home|No schedulers responded
3/22/2006 1:44:04 PM|SZTAKI Desktop Grid|Sending scheduler request to http://szdg.lpds.sztaki.hu/szdg/cgi-bin/scheduler
3/22/2006 1:44:04 PM|SZTAKI Desktop Grid|Reason: Requested by user
3/22/2006 1:44:04 PM|SZTAKI Desktop Grid|Note: not requesting new work or reporting results
3/22/2006 1:44:09 PM|SZTAKI Desktop Grid|Scheduler request to http://szdg.lpds.sztaki.hu/szdg/cgi-bin/scheduler succeeded
3/22/2006 1:44:59 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
3/22/2006 1:44:59 PM|SETI@home|Reason: Requested by user
3/22/2006 1:44:59 PM|SETI@home|Note: not requesting new work or reporting results
3/22/2006 1:45:06 PM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
3/22/2006 1:45:09 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
3/22/2006 1:45:09 PM|SETI@home|No schedulers responded

---

The only project not responding is SETI
And it's wednesday, the day SETI shuts down for it's weekly maintenance.

With the number of projects you have attached, it is normal for some of them to not DL more WUs. Boinc is very good at following your resource share as well as making sure that everything is crunched on time. This means that there are periods of time when it favors some projects over others and doesn't DL new WU. In the long run it all evens out.

With my 9 currently active projects and a very small cache it is not unusual for 2 or more projects to be without work on my computer. They eventually all DL work and get the % share of my computer CPU time that a assigned them.

You can read all about the Work Scheduler and the Work-Fetch Policy in the unofficial guide Paul. D. Buck's BOINC Wiki, now managed by Christopher Malton and Rytis Slatkevičius. It is the most comprehensive source of information on all things BOINC.

---

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470

thank you.

---