Resending LOST tasks?

Message boards : Number crunching : Resending LOST tasks?
Message board moderation

To post messages, you must log in.

1 · 2 · Next

AuthorMessage
Profile Cliff Harding
Volunteer tester
Avatar

Send message
Joined: 18 Aug 99
Posts: 1432
Credit: 110,967,840
RAC: 67
United States
Message 1238467 - Posted: 28 May 2012, 12:52:30 UTC

Running 7.0.xx on both of my machines. Over the last several days, I've noticed that the server has attempted to send several lost tasks only to find that the tasks are not lost at all. Is this a scheduler bug and has anyone else experienced this situation


I don't buy computers, I build them!!
ID: 1238467 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1238470 - Posted: 28 May 2012, 13:04:20 UTC - in response to Message 1238467.  

Yes and yes, see the other recent threads.

Claggy
ID: 1238470 · Report as offensive
Profile Khangollo
Avatar

Send message
Joined: 1 Aug 00
Posts: 245
Credit: 36,410,524
RAC: 0
Slovenia
Message 1238471 - Posted: 28 May 2012, 13:05:29 UTC

Just wait 8 more months and the problem will be fixed.
Maybe
ID: 1238471 · Report as offensive
Profile Wiggo
Avatar

Send message
Joined: 24 Jan 00
Posts: 23386
Credit: 261,360,520
RAC: 489
Australia
Message 1238472 - Posted: 28 May 2012, 13:05:53 UTC - in response to Message 1238470.  

Like thisthread.

Cheers.
ID: 1238472 · Report as offensive
andybutt
Volunteer tester
Avatar

Send message
Joined: 18 Mar 03
Posts: 262
Credit: 164,205,187
RAC: 516
United Kingdom
Message 1238598 - Posted: 28 May 2012, 19:27:38 UTC - in response to Message 1238467.  

I had the same yesterday for about twenty tasks
ID: 1238598 · Report as offensive
Profile Mr. Kevvy Crowdfunding Project Donor*Special Project $250 donor
Volunteer moderator
Volunteer tester
Avatar

Send message
Joined: 15 May 99
Posts: 3297
Credit: 1,114,826,392
RAC: 3,319
Canada
Message 1238679 - Posted: 29 May 2012, 0:34:37 UTC

Figured others were getting it... I've been seeing it for several days/occurrences too:

28/05/2012 20:31:05 | SETI@home | Resent lost task 30ja10ab.10032.13977.11.10.142_0
28/05/2012 20:31:05 | SETI@home | Resent lost task 16dc10ac.29188.10955.6.10.164_0
...{snip}...
28/05/2012 20:31:05 | SETI@home | [error] Already have task 30ja10ab.10032.13977.11.10.142_0
28/05/2012 20:31:05 | SETI@home | [error] Already have task 16dc10ac.29188.10955.6.10.164_0


ID: 1238679 · Report as offensive
Profile Wiggo
Avatar

Send message
Joined: 24 Jan 00
Posts: 23386
Credit: 261,360,520
RAC: 489
Australia
Message 1238691 - Posted: 29 May 2012, 1:24:22 UTC - in response to Message 1238679.  
Last modified: 29 May 2012, 1:25:28 UTC

Seeing as you all won't read the other thread I linked I'll repeat it, it will happen every time you report 64 tasks or more and if you want someone to blame for it then the culprit is Dr D.A. for writing quick fixes without proper testing. It will get fixed eventually but don't hold your breath waiting.

Cheers.
ID: 1238691 · Report as offensive
andybutt
Volunteer tester
Avatar

Send message
Joined: 18 Mar 03
Posts: 262
Credit: 164,205,187
RAC: 516
United Kingdom
Message 1238930 - Posted: 29 May 2012, 21:34:39 UTC - in response to Message 1238691.  

not every time
ID: 1238930 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14417
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1238954 - Posted: 31 May 2012, 16:53:15 UTC - in response to Message 1238930.  
Last modified: 31 May 2012, 17:29:15 UTC

not every time

OK, every time you report >64 tasks and request new work.

Remember that if you report again too soon after a 'lost task' event, you may lose credit - if any of the 'lost' tasks have, in fact, already completed, their reported runtime may be capped at the interval between the two reports.

I have plenty of ammunition available to test whether that one has been fixed when the scheduler comes back up.

Edit - well, we're stuck with reporting 64 at a time for the time being. Try not to ask for any new work until they're all reported, if you can.
ID: 1238954 · Report as offensive
andybutt
Volunteer tester
Avatar

Send message
Joined: 18 Mar 03
Posts: 262
Credit: 164,205,187
RAC: 516
United Kingdom
Message 1238991 - Posted: 31 May 2012, 17:57:25 UTC - in response to Message 1238954.  

that will be interesting after the last outage
ID: 1238991 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 5 Jul 99
Posts: 4654
Credit: 47,537,079
RAC: 4
United Kingdom
Message 1239000 - Posted: 31 May 2012, 18:10:41 UTC - in response to Message 1238954.  
Last modified: 31 May 2012, 18:14:17 UTC

not every time

OK, every time you report >64 tasks and request new work.

Remember that if you report again too soon after a 'lost task' event, you may lose credit - if any of the 'lost' tasks have, in fact, already completed, their reported runtime may be capped at the interval between the two reports.

I have plenty of ammunition available to test whether that one has been fixed when the scheduler comes back up.

Edit - well, we're stuck with reporting 64 at a time for the time being. Try not to ask for any new work until they're all reported, if you can.

I have NNT set, so as not to trigger the problem.

Claggy
ID: 1239000 · Report as offensive
Profile Khangollo
Avatar

Send message
Joined: 1 Aug 00
Posts: 245
Credit: 36,410,524
RAC: 0
Slovenia
Message 1239020 - Posted: 31 May 2012, 18:29:46 UTC

Putting <max_tasks_reported>64</max_tasks_reported> into cc_config.xml also does the trick; permanently.
ID: 1239020 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14417
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1239028 - Posted: 31 May 2012, 18:39:44 UTC - in response to Message 1239020.  

Putting <max_tasks_reported>64</max_tasks_reported> into cc_config.xml also does the trick; permanently.

Not every user reads these fora: not every user knows, or wants to know, how to set up a config file: and not every user runs a version of BOINC that supports that option.

I'll carry on trying to get it fixed at source, and let you know how I get on.
ID: 1239028 · Report as offensive
rob smith Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer moderator
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 20334
Credit: 416,307,556
RAC: 380
United Kingdom
Message 1239035 - Posted: 31 May 2012, 18:45:47 UTC

Far, far, far better to get it fixed at source than having to expect every user to have to hack a file for what is meant to be a run and forget tool.

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1239035 · Report as offensive
Profile Khangollo
Avatar

Send message
Joined: 1 Aug 00
Posts: 245
Credit: 36,410,524
RAC: 0
Slovenia
Message 1239041 - Posted: 31 May 2012, 18:50:18 UTC
Last modified: 31 May 2012, 18:50:55 UTC

And this is now what I meant. Of course it should be fixed at source.
Just for those who can; it is easily possible to do it now, by yourself, and avoid the resent lost tasks problem for the long months to come.
ID: 1239041 · Report as offensive
Profile Fred E.
Volunteer tester

Send message
Joined: 22 Jul 99
Posts: 768
Credit: 24,140,697
RAC: 0
United States
Message 1239157 - Posted: 31 May 2012, 22:27:03 UTC
Last modified: 31 May 2012, 22:31:07 UTC

The project may have fixed it today. I just reported 159 results. Scheduler only accepted 64, but I received no lost task messages.

I had been running with a max of 64 in cc_config.xml, but I had to revert to 6.10.60 this afternoon to get my uploads moving. Thus, my cc_config option did not restrict the number reported, and leaving it on NNT didn't avoid building up more than 64 to report.

Edit: just did it again with >64 tasks, no lost task messages.
Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.
ID: 1239157 · Report as offensive
bill

Send message
Joined: 16 Jun 99
Posts: 861
Credit: 29,352,955
RAC: 0
United States
Message 1239164 - Posted: 31 May 2012, 22:48:05 UTC - in response to Message 1239157.  

Lost task messages here within the last hour. <shrug>
ID: 1239164 · Report as offensive
-BeNt-
Avatar

Send message
Joined: 17 Oct 99
Posts: 1234
Credit: 10,116,112
RAC: 0
United States
Message 1239171 - Posted: 31 May 2012, 23:08:32 UTC

I'm getting them. And if I get shorted on the 1000+ I just turned in I'm gonna be upset.
Traveling through space at ~67,000mph!
ID: 1239171 · Report as offensive
hbomber
Volunteer tester

Send message
Joined: 2 May 01
Posts: 437
Credit: 50,852,854
RAC: 0
Bulgaria
Message 1239174 - Posted: 31 May 2012, 23:17:02 UTC
Last modified: 31 May 2012, 23:28:09 UTC

Yeah, great, just got 170 tasks marked as timeouted, BEFORE knowing that problem exists and happily hitting "Update" after each 64 tasks reported.
Seems they get validated etc, but anyway this behaviour is tottaly confusing.

P.S.
They all went to "pending" and slowly pouring to "valid", only real errors remained. Phew!
ID: 1239174 · Report as offensive
-BeNt-
Avatar

Send message
Joined: 17 Oct 99
Posts: 1234
Credit: 10,116,112
RAC: 0
United States
Message 1239182 - Posted: 31 May 2012, 23:42:18 UTC - in response to Message 1239174.  

Yeah, great, just got 170 tasks marked as timeouted, BEFORE knowing that problem exists and happily hitting "Update" after each 64 tasks reported.
Seems they get validated etc, but anyway this behaviour is tottaly confusing.

P.S.
They all went to "pending" and slowly pouring to "valid", only real errors remained. Phew!


Yeah checking mine over it appears most went into pending as expected a few went to valid and appears I'm getting proper credit. I've made the changes to my CC_config to avoid this, but this is just plan bad programming.
Traveling through space at ~67,000mph!
ID: 1239182 · Report as offensive
1 · 2 · Next

Message boards : Number crunching : Resending LOST tasks?


 
©2021 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.