Please, help me. I can not get new tasks from rosetta, even if I trying refresh frequently. There is messages returned:

10.6.2006 14:07:57||Suspending work fetch because computer is overcommitted.
10.6.2006 14:09:13|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
10.6.2006 14:09:13|rosetta@home|Reason: Requested by user
10.6.2006 14:09:13|rosetta@home|(not requesting new work or reporting completed tasks)
10.6.2006 14:09:18|rosetta@home|Scheduler request succeeded

How may I tell it I want new tasks?

---

Have you looked at your results recently? There are a lot of errors in them, excactly one work unit finished correctly, the other eight errored out at the same point of time. Your credits do however show that you have previously gotten some work done.

Did you change anything (new installed or updated software) at the time when the errors started? Maybe that is worth a look before you try to receive new work.

[edit] And you're only granted a maximum of 86 WUs/day; that means your quota is already reduced by 14 WUs that probably errored out (which makes another six on top of the eight shown in your profile). So your PC is definitely having problems at this moment, at least with Rosetta. It would not be wise to download new work until you know what kind of problems that are. From your own point of view it may just error out and consume your internet bandwidth without doing any good to anyone.[edit]

---

"I know that you believe you understand what you think I said, but I'm not sure you realize that what you heard is not what I meant." R.M. Nixon

All of your error work unit results are shown as having been "Aborted by User". If you abort the work unit it will not run to sucessfull completion.

BOINC is designed to run without any help from the user. If you abort the workunits, it will not reload new work for some period of time after that.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

---

"Suspending work fetch because computer is overcommitted"

This means : You have more work in your buffers than you can handle within the deadline of the WUs.

Reducing your cache size to maybe 1 or 2 days should fix the problem after a while - not immediately though as it has to crunch away the already downloaded stuff first.


p.s.: cache size = "connect to network about every ... days" in the global preferences