Message boards :
Number crunching :
Requesting 0 seconds of work with 15 WUs in cache
Message board moderation
Author | Message |
---|---|
Morten Ross Send message Joined: 30 Apr 01 Posts: 183 Credit: 385,664,915 RAC: 0 |
Hi, My 2xQuad Xeon (http://setiathome.berkeley.edu/show_host_detail.php?hostid=3816900)is almost out of work (should have more than 1200 units in cache), but is still not requesting new work! 12.05.2008 10:28:55 Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks Scheduler request succeeded: got 0 new tasks I'm baffled by this - any idea anyone? Morten Morten Ross |
Daniel Send message Joined: 21 May 07 Posts: 562 Credit: 437,494 RAC: 0 |
Hi, Is it set to No New Tasks? Daniel |
Morten Ross Send message Joined: 30 Apr 01 Posts: 183 Credit: 385,664,915 RAC: 0 |
|
Fred J. Verster Send message Joined: 21 Apr 04 Posts: 3252 Credit: 31,903,643 RAC: 0 |
Hi, Yesterday, 11 may, had quite the opposite, all 5 hosts stopped 'crunching' about 11:45 (UTC+1). Enough WU's in cache, 3rd time this happens, for NO apparent reason! Use BOINC 6.1.0. and the latest SSSE3/SSE4.1 optimized app.'s. No machine problems, would be odd, 5 hosts stopping about the same time. Network is OK. Out off options @ the moment? |
JDWhale Send message Joined: 6 Apr 99 Posts: 921 Credit: 21,935,817 RAC: 3 |
Hi, Do you have any "suspended" tasks... I don't know about BOINC 5.10.45, but the version I'm running, 5.10.30 will not request any work if any tasks are suspended. I've also heard that re-installing BOINC can "fix" this kind of problem. HTH, JDWhale |
Ingleside Send message Joined: 4 Feb 03 Posts: 1546 Credit: 15,832,022 RAC: 13 |
Hi, This is most likely a case of "too large cache-size". Taking a look on hostid-3816900 shows work downloaded 23.04 is returned today, this is 18-19 days turnaround-time, and this indicates you're likely running with a 20-day cache-setting. If isn't doing anything special, this likely means "connect every 10 days" + "additional 10 days cache". Now, having a large "additional N days" isn't normally a problem, but the "connect every 10 days" basically means "work with less than 20 days till deadline is in deadline-trouble..." If atleast one task in a project is in deadline-trouble, this shows-up in client as "Running, high priority", work-requests to project is blocked until not in deadline-trouble any longer, or idle cpu... Your task-list shows atleast one task has deadline 17.05, so if "connect every N days" is set to larger than 2.5 days, you're in deadline-trouble, and work-request is currently being blocked. To fix, if you have a permanent internet-connection, set "Connect every N days" to 0.1 days or something. You can still keep a fairly large cache by keeping "additional N days" at 10. It's still possible work-requests gets blocked with these settings, but normally it's for a much shorter time than if you're running with a high "connect every N days"-setting. "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14653 Credit: 200,643,578 RAC: 874 |
Hi, It also won't request any new work if you have a stalled download on the 'Transfers' tab. I've also heard that re-installing BOINC can "fix" this kind of problem. That's a bit drastic! Probably best to work through the other possibilities first, and keep this in reserve just in case.... I've heard of people who re-format their hard disks and re-install Windows for less than this: I call it the "sledgehammer and two short planks" school of computer maintenance. |
Morten Ross Send message Joined: 30 Apr 01 Posts: 183 Credit: 385,664,915 RAC: 0 |
Hi, Down to only 2 WUs in the queue and the magic happened - now it's downloadning like never before, and will propably not stop before 800 WUs (which is the daily limit). I have not changed my settings since 7 November 2007, so nothing on my part should have caused this. Furthermore, I have 9 other hosts where this has not happened. Problem solved for now... Morten Morten Ross |
Paul D. Buck Send message Joined: 19 Jul 00 Posts: 3898 Credit: 1,158,042 RAC: 0 |
Re-installing BOINC is not at all drastic. I have "upgraded" to 6.1.x and back to 5.x.y several times with no loss of work and only the slightest cost in time. With the new "sandbox" technology you will have to reinstall to set permissions quite often if you make changes within the BOINC directories. |
Odysseus Send message Joined: 26 Jul 99 Posts: 1808 Credit: 6,701,347 RAC: 6 |
With the new "sandbox" technology you will have to reinstall to set permissions quite often if you make changes within the BOINC directories. On a Mac I just correct the owner and group settings in the Finder’s Get Info window; I imagine Windows & Linux have similar functionsâ€â€available from a command line at least, if not from a GUI. |
Shourav De Send message Joined: 22 Apr 08 Posts: 6 Credit: 780,164 RAC: 0 |
I'd think a 20 day cache is a bit excessive O_O. Also from personal observation, the Boinc client will not request additional work without also reporting as completed a portion of your cache. |
1mp0£173 Send message Joined: 3 Apr 99 Posts: 8423 Credit: 356,897 RAC: 0 |
I'd think a 20 day cache is a bit excessive O_O. Also from personal observation, the Boinc client will not request additional work without also reporting as completed a portion of your cache. You're correct on all counts. The reason is that BOINC is looking at the due dates, and is "worried" about reporting on time if it isn't supposed to connect more than three times per month. Setting "connect every 0.5 days" and then setting the additional cache will allow BOINC to "top up" every day. |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
It really depends on the deadlines. If you have "connect every X" set to 10 days, the CPU scheduler knows that it has to finish all work at least 10 days before the report deadline so that it can be reported before you disconnect your computer from the internet for 10 days. If you also have additional work set to 10 days, you have 20 days of work to get finished 10 days before the deadline. If the deadlines are significantly longer than 30 days, there is unlikely to be any problem. However, if deadlines are less than 20 days, you are going to return work late. With mixed deadlines, it is possible to get the CPU scheduler in a bind with a queue that is too long. If you connect to the internet more frequently than once every 10 days, please drop your connect every X setting to something more reflective of reality. BOINC WIKI |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.