I just upgraded to the latest client today.
After 1st launching I clicked update and noticed this in the message tab:
5/1/2009 12:56:36 PM SETI@home Sending scheduler request: Requested by user.
5/1/2009 12:56:36 PM SETI@home Not reporting or requesting tasks
5/1/2009 12:56:41 PM SETI@home Scheduler request completed: got 0 new tasks

What do I need to do to get it to request tasks ?

BOINC needs the opinion it needs more tasks, if BOINC thinks there's enough work it won't request more.

If the reason is that you want a bigger cache you can set it under your account-page in computing preferences. BOINC will then automatically request more work with the next contact

I run BOINC 6.6.20 on a 4 processor machine. S@H and WCG are both given 50% of resources, with a one-day buffer. So normally it runs 2 of each project simultaneously.

Yesterday morning it was running two AP units when one of them completed and uploaded. It did not request any new S@H units, so continued on the remaining AP units (25%) and WCG (75%). This morning it reported the AP unit uploaded yesterday, but did not request any new work despite the fact that the remaining AP unit had less than five hours to complete. It is continuing to request and run WCG units.

So my question is - why is it not requesting S@H units ?

I don't know how exactly the resource share is calculated, i think cpu-time, and for any reason BOINC thinks you've done more sah and therefore adds WCG work. resource share is not meant for a specific moment it's sharing over long time. so if you've done more sah last week, this week it'll do wcg.

it's possible that you've done wcg on the most loaded cores and therefore has less cpu-time done which is now equalized.

I don't think you have to worry, it'll sorted out by itself

There is a bug in the 6.6.x series that can cause debts to get out of whack. I have been reporting this for weeks including logs of the wfd debug to no avail.

change your cc_config, stop the local client, exit BOINC Manager, restart, change cc_config to not reset debts. wait till the get out of whack again and repeat. Mine needs the kick every two days there abouts.

Note you cannot just re-read the config file, you have to stop and start again or the debts don't reset.

There is a bug in the 6.6.x series that can cause debts to get out of whack. I have been reporting this for weeks including logs of the wfd debug to no avail.

change your cc_config, stop the local client, exit BOINC Manager, restart, change cc_config to not reset debts. wait till the get out of whack again and repeat. Mine needs the kick every two days there abouts.

Note you cannot just re-read the config file, you have to stop and start again or the debts don't reset.

Paul, I seem to have a similar problem. Can you repeat all that, in very simple terms? Where do I find cc_config, and what do I do to it?

---

There is a bug in the 6.6.x series that can cause debts to get out of whack. I have been reporting this for weeks including logs of the wfd debug to no avail.

change your cc_config, stop the local client, exit BOINC Manager, restart, change cc_config to not reset debts. wait till the get out of whack again and repeat. Mine needs the kick every two days there abouts.

Note you cannot just re-read the config file, you have to stop and start again or the debts don't reset.

Paul, I seem to have a similar problem. Can you repeat all that, in very simple terms? Where do I find cc_config, and what do I do to it?

Bill, you create one... it is a text file and you drop it in the appropriate directory.

Sadly, the display strips off the formatting so the version you see is not the pretty one I sent.

MIne looks something like this:

<cc_config>
<log_flags>
<file_xfer>1</file_xfer>
<checkpoint_debug>0</checkpoint_debug>
<cpu_sched_debug>0</cpu_sched_debug>
<sched_op_debug>0</sched_op_debug>
<coproc_debug>0</coproc_debug>
<statefile_debug>0</statefile_debug>
<work_fetch_debug>0</work_fetch_debug>
<rr_simulation>0</rr_simulation>
</log_flags>
<options>
<report_results_immediately>0</report_results_immediately>
<zero_debts>0</zero_debts>
</options>
</cc_config>

And I turn on and off various things. You turn on things with a "1" and off with a zero. SO, you would change the zero debts to a 1, save the file, and stop and restart BOINC.

The easiest way to find the appropriate directory if you are not familiar with the systems is to do a search for "client_state.xml", you may need to turn on search in hidden files and directories to find it.

Copy the text above into notepad and save it as cc_config.xml.

Check the file to be sure NP did not add a .txt extension to the end, if it did, rename it.

The UCB documentation lists all the flags and shows the file format. If you PM me your e-mail, or look mine up and ping me I will be happy to send you a copy of my file.

Note that most of the flags are for debugging information though the top line allows you to turn off the upload messages in the logs to clean them up a little (default is 1, 0 turns off the messages)