Questions and Answers :
Preferences :
Not uploading completed WUs
Message board moderation
Author | Message |
---|---|
Dave McIntosh Send message Joined: 13 Jan 11 Posts: 7 Credit: 11,073,549 RAC: 0 |
For a while now (and since the upgarde to the latest version, but not blaming that) completed WUs are not uploading automatically. I have to go Projects, select the project (Seti@Home) and click Update. Any help or suggestions greatfully received. Dave. |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
How long have you let BOINC go before observing this? Meaning, do you wait 8 hours? 16 hours? 36 hours? |
Dave McIntosh Send message Joined: 13 Jan 11 Posts: 7 Credit: 11,073,549 RAC: 0 |
I'll get completed WUs often - probably every 10 or 15 minutes another will complete |
Gundolf Jahn Send message Joined: 19 Sep 00 Posts: 3184 Credit: 446,358 RAC: 0 |
That doesn't answer OzzFan's question! How long did you wait before clicking "update"? And for your first post, are you speaking about uploading or reporting of WUs? Gruß, Gundolf Computer sind nicht alles im Leben. (Kleiner Scherz) SETI@home classic workunits 3,758 SETI@home classic CPU time 66,520 hours |
Ex: "Socialist" Send message Joined: 12 Mar 12 Posts: 3433 Credit: 2,616,158 RAC: 2 |
Newer Boinc versions wait longer to report units and request work. They report work and request work in bigger batches now. I'm not sure how long you are waiting for those units to upload, but be patient... #resist |
Dave McIntosh Send message Joined: 13 Jan 11 Posts: 7 Credit: 11,073,549 RAC: 0 |
Okay, thanks. I'll wait overnight (it's now 19:30)- currently there are three WUs "ready to report". |
Ex: "Socialist" Send message Joined: 12 Mar 12 Posts: 3433 Credit: 2,616,158 RAC: 2 |
I don't even run a crunching rig that does alot of work, and I've had at least thirty waiting to report in the past. I know others probably even have longer lists. I'm sure your fine. :-) #resist |
Gundolf Jahn Send message Joined: 19 Sep 00 Posts: 3184 Credit: 446,358 RAC: 0 |
You shouldn't let that queue get too long (somebody mentioned a limit of 50 tasks to report) or you risk getting server timeouts on connection attempts. Gruß, Gundolf |
Dave McIntosh Send message Joined: 13 Jan 11 Posts: 7 Credit: 11,073,549 RAC: 0 |
At 09:05 - 10 hours later I had 60 WUs "ready to report". So I set off the process manually. Thanks for all your help. |
Hammeh Send message Joined: 21 May 01 Posts: 135 Credit: 1,143,316 RAC: 0 |
You can always use cc_config to force BOINC to report results immediately if it bothers you, however, this is not advisable as it puts extra load on the already busy seti@home servers. Peter |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
At 09:05 - 10 hours later I had 60 WUs "ready to report". So I set off the process manually. Thanks for all your help. 10 hours isn't the default time. 24 hours is. Try to give it more time. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Completed work is reported at the first of: 1) 24 hours before deadline. 2) Connect Every X before deadline. 3) 24 hours after task completion. 4) Immediately if the upload completes later than either 1, 2, or 3 upon completion of the task. 5) On a trickle up message. 6) On a trickle down request. 7) On a server scheduled connection. Used, but I am not certain by which project. 8) On a request for new work. 9) When the user pushes the update button. 10) On a request from an account manager. 11) Report immediately every task, if "No new Task" is set. 12) Report immediately if CPU or network time-of-day override starts in the next 30 minutes. (BOINC 7.0) 13) When minimum work buffer is reached. (BOINC 7.0) |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
^^^ There you go. I would do well to copy and paste that, but I'm lazy. |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
Completed work is reported at the first of: #13 is a repeat of #8. This is when the work fetch will occur. BOINC WIKI |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
#13 is a repeat of #8. This is when the work fetch will occur. Well, yes and no. The list of when reports happen is one for BOINC 5, 6 and 7. In BOINC 5 and 6 work requests happen at random, it seems. So better to differentiate between just a mere work request and when minimum work is reached. |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
#13 is a repeat of #8. This is when the work fetch will occur. No it wasn't. It was when the work on hand dropped below the sum of "connect every X" and "extra work". On 7 that changes to "connect every X". BOINC WIKI |
Francesco Forti Send message Joined: 24 May 00 Posts: 334 Credit: 204,421,005 RAC: 15 |
Completed work is reported at the first of: I think that an other point can be as soon as a "high task priority" is uploaded. |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
Completed work is reported at the first of: Not always. A low resource share task is likely to run high priority early, complete early and then sit there for a while. A task running in high priority gets the same treatment as any other task once it is done. 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.