Message boards : Number crunching : No Work Units??
Author | Message |
---|---|
Iserlohner Send message Joined: 3 Feb 08 Posts: 3 Credit: 418,345 RAC: 4 |
Hi Guys, I haven't had any WU's in a couple of days any Ideas? 12/04/2008 02:21:27|rosetta@home|Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks 12/04/2008 02:21:32|rosetta@home|Scheduler request succeeded: got 0 new tasks Is it me? Or am I going mad TTFN, TC |
Paul D. Buck Send message Joined: 17 Sep 05 Posts: 815 Credit: 1,812,737 RAC: 0 |
Are you running other projects? What are your resource shares? Did any of those projects just come off a 'dry spell"? |
Iserlohner Send message Joined: 3 Feb 08 Posts: 3 Credit: 418,345 RAC: 4 |
Are you running other projects? Hi Paul, I'm running Cels Rosetta WCG SETI I currently have 0 Cels WU's 0 Rosetta WU's 0 WCG WU's SETI is uploading but not downloading I have reset all bar SETI Resource Shares are: Cels 9.88% Rosetta 33.33% WCG 31.37% SETI 25.41 Confusing or what? They stopped downloading WU's a couple of days ago, thought it might be server probs but now I haven't got a clue Cheers for the quick reply TC |
Iserlohner Send message Joined: 3 Feb 08 Posts: 3 Credit: 418,345 RAC: 4 |
Are you running other projects? A result I reset SETI, (the only project with active work units) And the WU's have come flooding in from all quarters I'm happy again Cheers Paul |
Paul D. Buck Send message Joined: 17 Sep 05 Posts: 815 Credit: 1,812,737 RAC: 0 |
Sometimes BOINC does get all confused and the only alternative is to reset all the projects. The resource shares seem "reasonable" in that they spread the load around several projects. I am not sure I would have been able to help much more, but I knew the INITIAL questions to ask ... so that someone else could help ... :) But, you got going on your own ... cool ... |
Ingleside Send message Joined: 25 Sep 05 Posts: 107 Credit: 1,514,472 RAC: 0 |
Confusing or what? Hmm, it looks like you had around 250 SETI-wu's at time of reset, meaning even on a quad-core it's maybe 5 days of cached work... So, chances are your client was in deadline-trouble, this shows as "Running, high priority" on Task-tab. A client in deadline-trouble can in some instances block all work-requests until not in deadline-trouble any longer, or idle cpu... "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
Paul D. Buck Send message Joined: 17 Sep 05 Posts: 815 Credit: 1,812,737 RAC: 0 |
If you have DLS/Cable connection and a couple projects, as you do, USUALLY there is little issue with keeping the queue size at 0.1 days. I used to like to have about 5 projects with roughly the same resource shares i that I am more agnostic about projects than most people ... I am not that fanatical about any one project over another ... Well, I am more fanatical about projects that support OS-X than those that do not ... :) |
P . P . L . Send message Joined: 20 Aug 06 Posts: 581 Credit: 4,865,274 RAC: 0 |
I'm getting this now, had the same last week but it cleared up this hasn't. 5/12/2008 11:19:38 AM|rosetta@home|Requesting 7618 seconds of new work 5/12/2008 11:19:44 AM|rosetta@home|Scheduler RPC succeeded [server version 601] 5/12/2008 11:19:44 AM|rosetta@home|Message from server: Not sending work - last request too recent: 68 sec 5/12/2008 11:19:44 AM|rosetta@home|Deferring communication for 1 min 0 sec 5/12/2008 11:19:44 AM|rosetta@home|Reason: no work from project Server shows plenty of work! pete. |
Paul D. Buck Send message Joined: 17 Sep 05 Posts: 815 Credit: 1,812,737 RAC: 0 |
I'm getting this now, had the same last week but it cleared up this hasn't. Yes, but ... You have to let the system work ... in this case you are trying to "force" the capture of work... and ... the system is telling you to be patient. If the last comm is too recent, you have to wait until the delay period passes ... |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
In your case, it would appear it is BOINC that is getting impatient. To prevent the servers from getting flooded, BOINC enforces a wait between requests. By now, the problem has cleared up on it's own. The client eventually waits long enough and the project sends work. Rosetta Moderator: Mod.Sense |
Ingleside Send message Joined: 25 Sep 05 Posts: 107 Credit: 1,514,472 RAC: 0 |
I'm getting this now, had the same last week but it cleared up this hasn't. Ah, the "client doesn't wait long enough before re-ask"-bug, a quick look reveals this was fixed in v5.10.23, while one of your clients is still running v5.10.20... So, upgrading your BOINC-client will fix this problem. "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." |
Message boards :
Number crunching :
No Work Units??
©2025 University of Washington
https://www.bakerlab.org