Message boards :
Number crunching :
Not reporting or requesting tasks
Message board moderation
Author | Message |
---|---|
Send message Joined: 15 Jun 09 Posts: 6 Credit: 514,084 RAC: 0 |
Hi guys, I hope you can help me. From time to time I only get the message "Not reporting or requesting tasks" but I'm out of work -.- Yesterday I only have to restart the Boinc client to fix it but today I am since 3 hours out of work. 12.07.2009 02:12:59 Milkyway@home update requested by user 12.07.2009 02:13:02 Milkyway@home Sending scheduler request: Requested by user. 12.07.2009 02:13:02 Milkyway@home Not reporting or requesting tasks 12.07.2009 02:13:07 Milkyway@home Scheduler request completed Greetings Tod //Sry for my english, I'm a pupil from Germany an not very good in english :) |
Send message Joined: 12 Nov 07 Posts: 2425 Credit: 524,164 RAC: 0 |
Could be that MW has built up a debt and BOINC is trying to let the other projects have their turn to run. Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. |
Send message Joined: 15 Jun 09 Posts: 6 Credit: 514,084 RAC: 0 |
But from my other Projects I get no work *lhc@home resscource: 100 *orbit@home resscource: 100 *milkyway_GPU@home resscource: 100 and milkyway@home: resscource: 750 |
Send message Joined: 15 Jul 08 Posts: 12 Credit: 73,431,791 RAC: 0 |
ALERT !! Milky servers are down. Database has a problem of connection. unable to D/L ou U/L jobs |
Send message Joined: 15 Jun 09 Posts: 6 Credit: 514,084 RAC: 0 |
ALERT !! yeah, but my system doesn't request tasks ...
Are some of my settings wrong? How should I configure Boinc to have enough work? At the moment I have "Connectet every 0 days" and "more work for 5 days" but I only get 24 WUs at once .... if Boinc sends a request. Then I crunch them and upload them and ... nothig happen )= no more work |
Send message Joined: 29 Aug 07 Posts: 327 Credit: 116,463,193 RAC: 0 |
ALERT !! It's probably the five day cache you have set. MW has three day deadlines and a 6 WU per core limit, try setting your cache to less than three. Calm Chaos Forum...Join Calm Chaos Now |
Send message Joined: 12 Nov 07 Posts: 2425 Credit: 524,164 RAC: 0 |
It's the 'connect' that needs set under 3. Mine is set 'connect' to .5 days and work buffer to 6.5 days. I don't have any problems getting work when I want some. But from my other Projects I get no work Well for starters MW_GPU isn't running yet. Orbit says it has 0 jobs. LHC has 0 jobs. So your only problem is not getting work from MW. Doesn't expecting the unexpected make the unexpected the expected? If it makes sense, DON'T do it. |
Send message Joined: 15 Jun 09 Posts: 6 Credit: 514,084 RAC: 0 |
It's very strange ... now I've deleted the whole milkyway-project folder and tada I got 24 new tasks. I hope MW sends me now the WUs frequently ;) If the problem occured again I will post it Thx to all Tod |
Send message Joined: 9 Nov 08 Posts: 41 Credit: 92,786,635 RAC: 0 |
Hi! Scheduler request completed: got 0 new tasks I crunch MilkyWay only on CPU.... and it does not download new WU until all of 24 previous dowloaded finished..... So after crunch last WU CPU is idle waiting for download new WU. The worst thing is that sometimes i don't have internet for few hours... so IDLE for long time.... BOINC 6.6.28 A proud member of the Polish National Team COME VISIT US at Polish National Team FORUM |
Send message Joined: 15 Jun 09 Posts: 6 Credit: 514,084 RAC: 0 |
Hi! Now I have the older Boinc-client 6.4.7 and this one requests alway work. Maybe that can fix your problem, too. I hope it will. Tod |
Send message Joined: 24 Dec 07 Posts: 1947 Credit: 240,884,648 RAC: 0 |
Hi! I think it has to do with your connect preference and additional work buffer settings. Reduce it so the total is less than 24 hours and you should then see a change in the way BOINC behaves. |
Send message Joined: 1 Sep 08 Posts: 520 Credit: 302,524,931 RAC: 0 |
At a guess, the problem is the BOINC client version -- various iterations of the 6.x BOINC client do quite illogical things regarding work and reporting. What operating system are you running. Of the 6.x clients, I've found the 6.4.5 version to be the least troublesome. If you are not running Vista or Win7, you might consider getting the earlier (and much less problematic) BOINC 5.4.5 client. You can get that (and any other BOINC client version) from: http://boincdl.ssl.berkeley.edu/dl/ Hi! |
Send message Joined: 21 Aug 08 Posts: 625 Credit: 558,425 RAC: 0 |
At a guess, the problem is the BOINC client version -- various iterations of the 6.x BOINC client do quite illogical things regarding work and reporting. Actually, it's likely the cache setting. My system performs exactly the same way, and I'm using the old BOINC 5.8.16. Actually, the typical process for me is: Last task completes...then uploads. Scheduler request goes out and 5 tasks are downloaded. Uploaded result from before reports, and 1 additional task downloads, giving me the 6/core. Next work request isn't until the last task from that batch completes. Rinse, repeat, ad infinitum... |
Send message Joined: 1 Sep 08 Posts: 520 Credit: 302,524,931 RAC: 0 |
It could be -- though I've not seen this with 5.4.5 (and never played with later 5.x iterations). Then again, I have set my Network Usage (and cache) to high levels. I've set things to let MilkyWay (and where I'm running a Cuda GPU) GridGPU 'open', with other projects for no new tasks, in conjunction with a high (8 day plus) cache setting. When I want to load balance and get more work on projects like Spinhenge, POEM, Rosetta, Einstein, etc.) I temporarily set them to get new work, which they get readily, and then set them back. At a guess, the problem is the BOINC client version -- various iterations of the 6.x BOINC client do quite illogical things regarding work and reporting. |
©2024 Astroinformatics Group