19.6.2007 13:23:08|SETI@home|Sending scheduler request: Requested by user
19.6.2007 13:23:08|SETI@home|(not requesting new work or reporting completed tasks)
19.6.2007 13:23:13|SETI@home|Scheduler RPC succeeded [server version 509]
19.6.2007 13:23:13|SETI@home|Deferring communication for 11 sec
19.6.2007 13:23:13|SETI@home|Reason: requested by project


Still no news :-(

---

19.6.2007 13:23:08|SETI@home|Sending scheduler request: Requested by user
19.6.2007 13:23:08|SETI@home|(not requesting new work or reporting completed tasks)
19.6.2007 13:23:13|SETI@home|Scheduler RPC succeeded [server version 509]
19.6.2007 13:23:13|SETI@home|Deferring communication for 11 sec
19.6.2007 13:23:13|SETI@home|Reason: requested by project


Still no news :-(

Not requesting new work can have several meanings.

1) The project is suspended.
2) The project has been marked for No New Work (or No New Tasks depending on the version of BOINC).
3) The project has enough work on hand to fill its portion of "Connect every X days" (queue).
4) The project has a task that is in deadline trouble (and depending on the version of BOINC, the queue is full.
5) The queue is full and some task on any project is in deadline trouble.
6) The long_term_debt is too low for work fetch from the project.

To distinguish, several pieces of information are needed.
1) Is S@H suspended? Is it marked for NNT?
2) The time_stats section of the client_state.xml.
3) The deadline, CPU time remaining, and project for each task.
4) The long_term_debts for each project from client_state.xml.

---

BOINC WIKI

I'm having the same problem for probably a week or better now:

6/19/2007 4:42:32 PM|SETI@home|Sending scheduler request: Requested by user
6/19/2007 4:42:32 PM|SETI@home|(not requesting new work or reporting completed tasks)
6/19/2007 4:42:37 PM|SETI@home|Scheduler RPC succeeded [server version 509]
6/19/2007 4:42:37 PM|SETI@home|Deferring communication for 11 sec
6/19/2007 4:42:37 PM|SETI@home|Reason: requested by project


Project is not suspended. I have no Tasks related to SETI. It is set to receive work.

Any help would be appreciated.

---

I'm having the same problem for probably a week or better now:

6/19/2007 4:42:32 PM|SETI@home|Sending scheduler request: Requested by user
6/19/2007 4:42:32 PM|SETI@home|(not requesting new work or reporting completed tasks)
6/19/2007 4:42:37 PM|SETI@home|Scheduler RPC succeeded [server version 509]
6/19/2007 4:42:37 PM|SETI@home|Deferring communication for 11 sec
6/19/2007 4:42:37 PM|SETI@home|Reason: requested by project


Project is not suspended. I have no Tasks related to SETI. It is set to receive work.

Any help would be appreciated.

OK, that eliminates some of the possibilities.

What other projects are you running?

What are all of the long_term_debts (from client_state.xml) for all projects?

What does the time_stats section from the client_state.xml file look like?

What are the remaining CPU times for all tasks?

What are the deadlines for all tasks?

What is your connect every X setting?

What is your switch between tasks setting?

---

BOINC WIKI

Try going into the BOINC option => Advanced / Preferences and select "Clear". I had the same prolem, and that resolved the issue.

Robin

---

What other projects are you running?
- Climate Prediction

What are all of the long_term_debts (from client_state.xml) for all projects?
- The only two Long_term_debts in there are "-365101.207648"

What does the time_stats section from the client_state.xml file look like?
- <time_stats>
<on_frac>0.868899</on_frac>
<connected_frac>1.000000</connected_frac>
<active_frac>0.028866</active_frac>
<cpu_efficiency>0.149145</cpu_efficiency>
<last_update>1183035730.750000</last_update>
</time_stats>

What are the remaining CPU times for all tasks?
Climate1 = 2214:45:26
Climate2 = 2216:39:17
(that looks fishy to me... That's what is says under "To Completion"

What are the deadlines for all tasks?
5/15/2008 2:15:48 AM
5/15/2008 6:18:47 PM

What is your connect every X setting?
I'm not sure where i'd find this. It generally connects whenever it wants to. I'm not aware of any restrictions I've given it.

What is your switch between tasks setting?
The resource share is 400 for Seti and switch between is 60 minutes.

I also noticed that "Maintain enough work for an additional" is set to 2 days, is that an ok setting? I've never had this issue with SETI before.

---

What other projects are you running?
- Climate Prediction

What are all of the long_term_debts (from client_state.xml) for all projects?
- The only two Long_term_debts in there are "-365101.207648"

One of the two is positive, and the other is negative. The one that is negative will be unable to ask for work because it is so negative.

What does the time_stats section from the client_state.xml file look like?
- <time_stats>
<on_frac>0.868899</on_frac>
<connected_frac>1.000000</connected_frac>
<active_frac>0.028866</active_frac>
<cpu_efficiency>0.149145</cpu_efficiency>
<last_update>1183035730.750000</last_update>
</time_stats>

Your host has a very low availibily. 0.868899 * 0.028866 * 0.149145 = 0.00374080097915343. This means that BOINC believes that the wall time to complete a task is about 267 times the CPU time.

What are the remaining CPU times for all tasks?
Climate1 = 2214:45:26
Climate2 = 2216:39:17
(that looks fishy to me... That's what is says under "To Completion"

Not to me. CPDN takes a LOOONG time.

2200 * 267 = 587400 hours or 24475 days or 67 years for EACH of the CPDN tasks. This is the reason that BOINC is unwilling to download new work for any project - it believes that the host is already severely overloaded.

What are the deadlines for all tasks?
5/15/2008 2:15:48 AM
5/15/2008 6:18:47 PM

What is your connect every X setting?
I'm not sure where i'd find this. It generally connects whenever it wants to. I'm not aware of any restrictions I've given it.

It can be found on your account page on this web site, or in the newer versions of boinc, it can be found in the client as well. If you have not changed it, it is probably set to 0.1 days which is reasonable.

What is your switch between tasks setting?
The resource share is 400 for Seti and switch between is 60 minutes.

Reasonable as well[/quote]
I also noticed that "Maintain enough work for an additional" is set to 2 days, is that an ok setting? I've never had this issue with SETI before.[/quote]
Depending on the connect every X which is right next to the additional days, 2 days may not be out of line.

The real cause of your problems are the active_frac and the cpu_efficiency. active_frac is the fraction of the time that BOINC is on that it is allowed to process. This value is extremely, and we need to figure out why. Do you have the screen saver running? What is the setting for do work while user is active? The CPU efficiency is also pretty low. This is the fraction of the CPU that BOINC gets when it is allowed to process. We need to figure out why. Could you run a complete series of Malware and Virus scans? Do you do some other program the heavily utilizes the CPU, such as another DC project?

---

BOINC WIKI

Well, the main problem is in your time stats. Even though your host is turned on 86.9% of the time according to BOINC, it's only being allowed to run work 2.9% of that. In addition to that when it is running work, only 14.9% of the CPU time is going to the science apps. A secondary factor is you're giving CPDN a 25% resource share (assuming you left it at 100).

This also explains the high negative LTD for CPDN, which I assume is the one you listed. If you're only running two, then SAH's LTD must be the compliment of that. The combination of the bad overall indicated host efficiency along with the relatively low resource share for CPDN is causing BOINC to think it has to run it exclusively now to avoid missing the deadline, even though that's almost a year away.

What I would suggest is to shut down BOINC and edit the client_state file time stats to something more reasonable for active_frac and cpu efficiency. 0.950000 for both would probably be adequate to get things back on track. You might also want to set the LTD for both projects to 0.000000 as well to 'reset' from the extended run on CPDN you just made. Then save the file and restart BOINC.

That should take care of the problem. FWIW, I've had the time stats get whacky occaisionally for no apparent reason. In this case if you see them start to get strange again then you may have to do a little poking around to find out what's 'hogging' the processor when you're not using it. Also work if you have BOINC set up to cache around two days of work, that's reasonable setting and shouldn't normally causing scheduling jams, even when running CPDN.

HTH,

Alinator

<edit> LOL... I see John was hanging around! I guess two answers saying about same thing meets the quorum. ;-)

Well I tried changing some of the settings you suggested but nothing seemed to help. Ultimatley, I've detached from the Climate project and the uninstalled BOINC completely and reinstalled it.

I not have a new work unit so that is what is important to me. I made a copy of the old directy though in case you'd like to view any of the xml files to track down the issue.

---

Well I tried changing some of the settings you suggested but nothing seemed to help. Ultimatley, I've detached from the Climate project and the uninstalled BOINC completely and reinstalled it.

I not have a new work unit so that is what is important to me. I made a copy of the old directy though in case you'd like to view any of the xml files to track down the issue.

You were not getting any new work because the CPDN work you had committed your computer till close to the deadline - no matter what you did. The only way out whild completing the CPDN work was to just let it run.

---

BOINC WIKI