Missing Apps Part 2
log in

Advanced search

Message boards : News : Missing Apps Part 2

Previous · 1 · 2
Author Message
Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 2
Message 19427 - Posted: 10 May 2014, 13:40:50 UTC - in response to Message 19416.

Hallo.
Work from 2th May and returned 10th May is not validate.
Where is your promise to prolong deadline 7+7 days?
See: http://boic.thesonntags.com/collatz/results.php?hostid=132838&offset=0&show_names=0&state=6&appid=
One week of work lost.


As the tasks were re-issued, they do have a deadline of 14 days. The only thing I can figure is that the BOINC client and the BOINC server don't agree on how to handle the overdue WUs. Can you please post your event log with the message from the server stating the client should abandon the work?

The grace period is supposed to work like this:
host A gets a WU
host A starts crunching the WU but won't finish by the deadline, it keeps crunching anyway
The deadline is past so the server sends the WU to host B
host B starts crunching the WU
host A finally finishes and uploads the WU
If the date is < deadline + grace period, the host A should be awarded credit when it uploads and reports the result.
Host B would also receive credit if it returns the result prior to the deadline.

So why didn't it work in your case? My guess is that the host did a project update prior to uploading the WUs. I know that uploading the WUs causes the state on the client (and maybe the server?) to change which may affect the grace period logic. That's why I'd like you to post the BOINC event log. I'm hoping it will give some info I can pass on to the BOINC developers in order to figure out why the grace period didn't work in your case. Right now, it's just a theory as to why it didn't work.

farnost litomysl
Send message
Joined: 3 Sep 09
Posts: 3
Credit: 3,714,387,388
RAC: 0
Message 19429 - Posted: 10 May 2014, 15:29:46 UTC - in response to Message 19427.

Thanks for response.
Events log is on 5 pages, because other projects upload and download between collatz, but relevant is this:
00:06:06 start uploads ... (of 95 results)
00:07:05 Reporting 74 completed tasks
00:07:05 Requesting new tasks for ATI
00:07:09 Scheduler request completed: got 39 new tasks
00:07:09 results large collatz ...(name)... is no longer usable (21 pieces)
00:07:21 Finished upload of collatz... (last wu)
00:09:13 Reporting 45 completed tasks (it is curious,because 74+45=119,but there was only 95 results)
00:09:13 Scheduler request completed

That is all.
Only 2wu´s of 95 were validated
Computer number 132 838 with name: TEST-PC.
My commentary is blue.
NOW results:
1. lost ready work (bad)
2. lost energy (more than 100kWH)
3. lost credit (about 22 M)- very attractive present for our rivals in Pentathlon

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 2
Message 19431 - Posted: 10 May 2014, 18:51:10 UTC - in response to Message 19429.

Thanks for response.
Events log is on 5 pages, because other projects upload and download between collatz, but relevant is this:
00:06:06 start uploads ... (of 95 results)
00:07:05 Reporting 74 completed tasks
00:07:05 Requesting new tasks for ATI
00:07:09 Scheduler request completed: got 39 new tasks
00:07:09 results large collatz ...(name)... is no longer usable (21 pieces)
00:07:21 Finished upload of collatz... (last wu)
00:09:13 Reporting 45 completed tasks (it is curious,because 74+45=119,but there was only 95 results)
00:09:13 Scheduler request completed

That is all.
Only 2wu´s of 95 were validated
Computer number 132 838 with name: TEST-PC.
My commentary is blue.
NOW results:
1. lost ready work (bad)
2. lost energy (more than 100kWH)
3. lost credit (about 22 M)- very attractive present for our rivals in Pentathlon


I totally understand #1 and #2 but technically, #3 doesn't count since you were attempting to bunker 7 days in advance when SG made it clear that they were rescheduling. Had you started bunkering 3 days in advance when it was officially announced, your would not have been beyond the original 7 day deadline.
Consider this... everyone else that started bunkering 7 days in advance has the same issue so your rivals are facing the same problems if they also tried bunkering when it was first announced rather than waiting for the official announcement.

I'll forward the logs on to the BOINC developers and see if they can explain what happened, or better yet, come up with a fix.

Previous · 1 · 2
Post to thread

Message boards : News : Missing Apps Part 2


Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.