If you update to Rosetta and your message looks like below, where I've colored red

5/19/2007 10:33:19 PM||request_reschedule_cpus: project op
5/19/2007 10:33:24 PM|rosetta@home|Sending scheduler request to https://boinc.bakerlab.org/rosetta_cgi/cgi
5/19/2007 10:33:24 PM|rosetta@home|Reason: Requested by user
5/19/2007 10:33:24 PM|rosetta@home|Note: not requesting new work or reporting results

it means that your BOINC Manager has decided that it does not need any Rosetta work at the moment to fulfill it's crunching plans for the near future.

BOINC tracks the amount of time spent crunching each project and tracks how this compares to your desired resource shares (as shown in the Projects tab of the advanced view). When no work is available for one project, and it is unable to crunch for that project, it does work for your other project(s). But when this occurs, BOINC keeps track of a "debt". The project that is crunching is incurring a debt to the one that has no work. When work becomes available on the other project, then BOINC will crunch a lot of it to make up the debt.

For example, if you run SETI and Rosetta and have a resource share of 2/3rds to SETI and 1/3rd to Rosetta, and you have been crunching only Rosetta for a week, due to SETI outage... you will need to crunch nothing but SETI for about 2 weeks to get back in to balance. i.e. to pay back the debt. After that time, BOINC will resume a mixture of work for each project and begin requesting Rosetta work again.

If you have more then two projects, the concepts are the same. Although with a mixture of deadlines and runtimes, it will be more complex to predict exactly when things will come back in to balance. Just rest assured that BOINC is keeping track of it all, and trying to keep the resource shares and other configuration parameters you have specified.

As always, if you would LIKE you crunch more Rosetta, you can increase your resource allocation in your Rosetta Preferences. But you will still have the "debt" to pay back to SETI first, if you increase your Rosetta share, the debt will be balanced sooner then otherwise.

---

Rosetta Informational Moderator: Mod.Zilla

bump

---

Rosetta Moderator: Mod.Sense

I don't know if it was down or not. I'm happily crunching WUs on the 25th of May...

If you're a moderator and live in the U.S., why not call Baker Lab to see if there is a situation and then post an announcement if there is a temporary outage?

---

My point of this thread was to explain there are 20,000 tasks queued up and being downloaded all the time on Rosetta. But there are many users out there with no Rosetta work right now, and at the "not requesting new work" message is your cue to see that the issue is not with the project, but rather with your local environment, relative debt levels etc.

---

Rosetta Moderator: Mod.Sense

there is something strange going on atm. I've seen two of my computers, both of which run Rosetta 100%, showing the (not requesting new work or reporting results) message, even though they've been very low on work and had results to report.

---

KSMarksPsych wrote
You can use this little web app to check your debts if you don't want to open the file locally.

Nice working link.
Anders n

---

A tool for resetting LTD

http://home.austin.rr.com/skipsjunk/info/boincdv.html

don't forget to read the readme.txt

Anders n

---

Hi from Spain!
I simple question... Why...?

03/06/2007 17:29:06||Fetching configuration file from https://boinc.bakerlab.org/rosetta/get_project_config.php
03/06/2007 17:29:21|rosetta@home|Sending scheduler request: Requested by user
03/06/2007 17:29:21|rosetta@home|(not requesting new work or reporting completed tasks)
03/06/2007 17:29:53|rosetta@home|Scheduler RPC succeeded [server version 509]
03/06/2007 17:29:53|rosetta@home|Deferring communication for 4 min 2 sec
03/06/2007 17:29:53|rosetta@home|Reason: requested by project

four days ago!!!

Regards! Nice day!

---

Kejo, I've moved your post to this thread. I believe you will find your question is already answered below, but please review and if not, let us know more about how you are using BOINC on your computer.

---

Rosetta Moderator: Mod.Sense

Since there is no way for the user community to contact the moderators reliably, I have established this sticky. Hopefully this will reduce the number of new threads started solely for the purpose of attracting the attention of the moderation team to a problem or complaint.

This is a place for the user community to contact the moderators to provide feed back, ask for explanations for any moderator actions, request moderator actions, or get assistance that may require a moderator.

Feel free to post here, but note that after the issue is address the posts will be moved to an archive thread located here.

So think of this as a work queue for the moderation team. If the question is in this sticky and a moderator has not responded it has not yet been addressed.

I have not received any work for a couple of weeks. Is there a problem on my machine or what do I have to do to rectify this condition.

Thank yoou in advance.

---

Moved Jstrcich here from moderator contact thread. Asked they review the contents of this thread and post any relevant details based on the info. here.

---

Rosetta Moderator: Mod.Sense

Mod.Sense, Jstrcich doesn't seem to be running Seti...

Jstrcich, can you post the messages from the messages tab in boinc manager (advanced view)?

cheers
Danny

---

It got done with the last work a couple days ago and now as not downloaded any new ones. How do I force it to download again?

---

[edit]As you're running more than one project it might be that boinc is repaying a debt to another project...[/edit]

try 'update' on the first tab in BoincManager's Advanced View. If that doesn't get you anywhere then try 'Retry Communications' under the Advanced menu.

Also, can you post the most recent page or so of your 'messages' tab?

---

bump

---

Rosetta Moderator: Mod.Sense

Haven't gotten any updates/Work in 2 weeks,

8/21/2007 7:13:55 AM|rosetta@home|Sending scheduler request: Requested by user
8/21/2007 7:13:55 AM|rosetta@home|(not requesting new work or reporting completed tasks)
8/21/2007 7:14:00 AM|rosetta@home|Scheduler RPC succeeded [server version 509]
8/21/2007 7:14:00 AM|rosetta@home|Deferring communication for 4 min 2 sec
8/21/2007 7:14:00 AM|rosetta@home|Reason: requested by project

Are we down?
I have no debts or anything pending.

Until you see the message indicating that you are requesting xxx seconds of work, and not receiving any, the source of the problem is on the client side. Even with no debt, it may feel it has enough work from other projects to be busy.

---

Rosetta Moderator: Mod.Sense

Until you see the message indicating that you are requesting xxx seconds of work, and not receiving any, the source of the problem is on the client side. Even with no debt, it may feel it has enough work from other projects to be busy.

Since the Einstein@home work units started taking over 60 hours of cpu time, I now only run SETI and Rosetta. Last week when the SETI project went down due to some server problem, all my computers did was Rosetta. Then SETI comes back after a few days of downtime and the problem of Rosetta not getting any new work began. I guess the B in BOINC being Berkeley should tip us off that SETI has priority over who gets what.

Seems to me if they can't keep their project up and running they shouldn't take it out on other projects.

Anyway, I found that if I just suspend SETI, then I immediately get Rosetta downloads. Then resume SETI and it goes back to sharing according to my preferences.

Since the Einstein@home work units started taking over 60 hours of cpu time, I now only run SETI and Rosetta. Last week when the SETI project went down due to some server problem, all my computers did was Rosetta. Then SETI comes back after a few days of downtime and the problem of Rosetta not getting any new work began. I guess the B in BOINC being Berkeley should tip us off that SETI has priority over who gets what.

It's working exactly as designed, and not some devious scheme by the SETI folks.

Simply stated, while you were only crunching Rosetta last week, you were building up crunching debt owed to SETI. Until that debt is paid off by crunching SETI WUs, it will not download Rosetta WUs to process.

---

Nemesis n. A righteous infliction of retribution manifested by an appropriate agent.

Seems to me if they can't keep their project up and running they shouldn't take it out on other projects.

If the projects in the events you describe had been reversed, the project making up debt would be reversed as well. YOU control how much of your computer time goes to each project through your resource share. During periods when BOINC is unable to get work from a project, it does work on other projects but tracks the time "owed" to the one that is not crunching. This "debt" is later repaid. But it works the same for all BOINC projects. No preference to SETI.

For example, if you run 80% Rosetta and 20% SETI then typically SETI would get 4.8hrs of CPU time (per CPU) each day on average. If the BOINC client is unable to get work for 2 days, then it will likely crunch SETI for 9hrs straight once work becomes available. After that, the debt is made up, and a more normal rotation between projects will occur. But, if your Rosetta work happens to be coming up on a deadline after those two days, then it may continue to crunch Rosetta to meet the deadline. And during that additional time, it will continue to tally up debt for SETI. And during the 9hrs of catch-up time, 20% of the 9hrs should go to SETI as well, so you see it is always a moving target with many objectives trying to be met.

As always, expect your resource share to be enforced over the course of 100 hours, not 100 minutes. And you will find BOINC really does a good job scheduling your machine to meet your objectives.

---

Rosetta Moderator: Mod.Sense