Not uploading completed WUs


log in

Advanced search

Questions and Answers : Preferences : Not uploading completed WUs

Author Message
Dave McIntosh
Send message
Joined: 13 Jan 11
Posts: 7
Credit: 10,211,985
RAC: 6,127
New Zealand
Message 1226969 - Posted: 4 May 2012, 2:06:09 UTC

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
Volunteer tester
Avatar
Send message
Joined: 9 Apr 02
Posts: 13625
Credit: 31,067,971
RAC: 20,392
United States
Message 1226992 - Posted: 4 May 2012, 3:27:54 UTC - in response to Message 1226969.

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: 10,211,985
RAC: 6,127
New Zealand
Message 1227039 - Posted: 4 May 2012, 5:47:59 UTC - in response to Message 1226992.

I'll get completed WUs often - probably every 10 or 15 minutes another will complete

Profile Gundolf Jahn
Send message
Joined: 19 Sep 00
Posts: 3184
Credit: 359,436
RAC: 34
Germany
Message 1227060 - Posted: 4 May 2012, 6:54:57 UTC - in response to Message 1227039.

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

Profile Ex
Volunteer moderator
Volunteer tester
Avatar
Send message
Joined: 12 Mar 12
Posts: 2895
Credit: 1,797,699
RAC: 1,325
United States
Message 1227063 - Posted: 4 May 2012, 6:56:17 UTC

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...
____________
-Dave #2

3.2.0-33

Dave McIntosh
Send message
Joined: 13 Jan 11
Posts: 7
Credit: 10,211,985
RAC: 6,127
New Zealand
Message 1227078 - Posted: 4 May 2012, 7:30:53 UTC - in response to Message 1227063.

Okay, thanks. I'll wait overnight (it's now 19:30)- currently there are three WUs "ready to report".

Profile Ex
Volunteer moderator
Volunteer tester
Avatar
Send message
Joined: 12 Mar 12
Posts: 2895
Credit: 1,797,699
RAC: 1,325
United States
Message 1227102 - Posted: 4 May 2012, 8:47:22 UTC

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.

:-)
____________
-Dave #2

3.2.0-33

Profile Gundolf Jahn
Send message
Joined: 19 Sep 00
Posts: 3184
Credit: 359,436
RAC: 34
Germany
Message 1227113 - Posted: 4 May 2012, 10:09:25 UTC - in response to Message 1227102.

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: 10,211,985
RAC: 6,127
New Zealand
Message 1227386 - Posted: 4 May 2012, 21:08:15 UTC

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.

Profile Hammeh
Volunteer tester
Avatar
Send message
Joined: 21 May 01
Posts: 135
Credit: 1,143,316
RAC: 0
United Kingdom
Message 1227406 - Posted: 4 May 2012, 21:40:48 UTC

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
Volunteer tester
Avatar
Send message
Joined: 9 Apr 02
Posts: 13625
Credit: 31,067,971
RAC: 20,392
United States
Message 1227423 - Posted: 4 May 2012, 22:26:35 UTC - in response to Message 1227386.

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.

Profile Ageless
Avatar
Send message
Joined: 9 Jun 99
Posts: 12332
Credit: 2,633,975
RAC: 1,213
Netherlands
Message 1227429 - Posted: 4 May 2012, 22:36:30 UTC

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)
____________
Jord

Fighting for the correct use of the apostrophe, together with Weird Al Yankovic

OzzFan
Volunteer tester
Avatar
Send message
Joined: 9 Apr 02
Posts: 13625
Credit: 31,067,971
RAC: 20,392
United States
Message 1227451 - Posted: 4 May 2012, 23:16:14 UTC - in response to Message 1227429.

^^^ There you go. I would do well to copy and paste that, but I'm lazy.

John McLeod VII
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 15 Jul 99
Posts: 24694
Credit: 522,659
RAC: 19
United States
Message 1228418 - Posted: 6 May 2012, 20:05:43 UTC - in response to Message 1227429.

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)

#13 is a repeat of #8. This is when the work fetch will occur.
____________


BOINC WIKI

Profile Ageless
Avatar
Send message
Joined: 9 Jun 99
Posts: 12332
Credit: 2,633,975
RAC: 1,213
Netherlands
Message 1228463 - Posted: 6 May 2012, 22:02:00 UTC - in response to Message 1228418.

#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.
____________
Jord

Fighting for the correct use of the apostrophe, together with Weird Al Yankovic

John McLeod VII
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 15 Jul 99
Posts: 24694
Credit: 522,659
RAC: 19
United States
Message 1228805 - Posted: 7 May 2012, 21:10:43 UTC - in response to Message 1228463.

#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.

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

Profile Francesco Forti
Avatar
Send message
Joined: 24 May 00
Posts: 281
Credit: 140,415,388
RAC: 51,437
Switzerland
Message 1231976 - Posted: 14 May 2012, 13:28:35 UTC - in response to Message 1227429.

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)


I think that an other point can be as soon as a "high task priority" is uploaded.
____________

John McLeod VII
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 15 Jul 99
Posts: 24694
Credit: 522,659
RAC: 19
United States
Message 1232322 - Posted: 15 May 2012, 4:54:03 UTC - in response to Message 1231976.

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)


I think that an other point can be as soon as a "high task priority" is uploaded.

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

Questions and Answers : Preferences : Not uploading completed WUs

Copyright © 2014 University of California