Questions and Answers :
Windows :
Maximum daily WU quota per CPU 1/day
Message board moderation
Author | Message |
---|---|
Tetard Send message Joined: 31 Dec 02 Posts: 6 Credit: 114,272,323 RAC: 0 |
For one server, impossible to download WU, -Deferring communication for 22 hr 26 min 26 sec -Message from server: (reached daily quota of 2 results) -Message from server: No work sent What can I do ? |
Byron S Goodgame Send message Joined: 16 Jan 06 Posts: 1145 Credit: 3,936,993 RAC: 0 |
For one server, impossible to download WU, Would need to have you un-hide your computer, or to at least post the message log from the BOINC Manager on the pc that's not getting work. Both would help even more. Otherwise we're left to guessing about it, and if I were to guess I'd say there's a chance you're putting out errors on the WU's you're getting, and BOINC is limiting you on what it will recieve, until valid work is produced on the pc. |
Tetard Send message Joined: 31 Dec 02 Posts: 6 Credit: 114,272,323 RAC: 0 |
Effectively i had some problem with boinc setup and some WU was in error since one week. Cant I reset this situation ? Or just wait tomorrow ? I reinstall the client but those parameters are stored on seti server. |
Byron S Goodgame Send message Joined: 16 Jan 06 Posts: 1145 Credit: 3,936,993 RAC: 0 |
Effectively i had some problem with boinc setup and some WU was in error since one week. If this started a week ago I'd have to say just waiting isn't going to solve the problem( though still guessing here). Since you say you did just reinstall the client it wouldn't hurt to make sure your firewall isn't blocking BOINC from downloading. There is a chance that a reset may help, but without knowing what the errors are that were produced and why, it's not very easy to know what course of action to take. Message log could be of use or the Tasks Details of the WU's that had errors are going to be the most help to determine that. |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
This message is caused by returning 100 tasks / CPU in a row with errors. If you have corrected the problem, the quota will rise very rapidly. If you have not, then the quota will stay at one. Every task that is either misses the deadline, or has computation, download, or upload errors, will reduce the quota by one. Any task that is returned on time without errors will double the quota. The low limit is one task / CPU / day. The high is set by the project and is 100 / CPU /day for SETI. Of course other projects have other quotas. CPDN has a quota of 4 / CPU / day, and there was one with very short tasks that had a limit of 1000 / CPU / day. BOINC WIKI |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Adding to all this, the only ways to get around it is: 1) To fix whatever problem it is you are having. Without a look at the error code that BOINC is throwing out, this is going to be extremely difficult to give help on. (Give us the hostID number or link to any of the tasks that got an error) 2) Get a new hostID number for the machine. Now this may sound easy, but it isn't. The only sure way these days to get a new ID number is to change your OS drastically (say: from Windows to Linux), to change your CPU drastically (from an Intel to an AMD) or to reformat and start all over. Trouble is, if the problem isn't fixed, this new hostID will end up at 1 task per CPU per day in under a week as well. It's easier to fix whatever problem you are having. |
Tetard Send message Joined: 31 Dec 02 Posts: 6 Credit: 114,272,323 RAC: 0 |
All is OK now, After correcting the problem and the first WU was correctly calculated, the wu/day grow normally. Thanks Tetard |
©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.