Message boards :
Number crunching :
Resending LOST tasks?
Message board moderation
Author | Message |
---|---|
Cliff Harding Send message Joined: 18 Aug 99 Posts: 1432 Credit: 110,967,840 RAC: 67 |
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!! |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Yes and yes, see the other recent threads. Claggy |
Khangollo Send message Joined: 1 Aug 00 Posts: 245 Credit: 36,410,524 RAC: 0 |
|
Wiggo Send message Joined: 24 Jan 00 Posts: 34744 Credit: 261,360,520 RAC: 489 |
|
andybutt Send message Joined: 18 Mar 03 Posts: 262 Credit: 164,205,187 RAC: 516 |
I had the same yesterday for about twenty tasks |
Mr. Kevvy Send message Joined: 15 May 99 Posts: 3776 Credit: 1,114,826,392 RAC: 3,319 |
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 |
Wiggo Send message Joined: 24 Jan 00 Posts: 34744 Credit: 261,360,520 RAC: 489 |
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. |
andybutt Send message Joined: 18 Mar 03 Posts: 262 Credit: 164,205,187 RAC: 516 |
not every time |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
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. |
andybutt Send message Joined: 18 Mar 03 Posts: 262 Credit: 164,205,187 RAC: 516 |
that will be interesting after the last outage |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
not every time I have NNT set, so as not to trigger the problem. Claggy |
Khangollo Send message Joined: 1 Aug 00 Posts: 245 Credit: 36,410,524 RAC: 0 |
|
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
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. |
rob smith Send message Joined: 7 Mar 03 Posts: 22202 Credit: 416,307,556 RAC: 380 |
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? |
Khangollo Send message Joined: 1 Aug 00 Posts: 245 Credit: 36,410,524 RAC: 0 |
|
Fred E. Send message Joined: 22 Jul 99 Posts: 768 Credit: 24,140,697 RAC: 0 |
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. |
bill Send message Joined: 16 Jun 99 Posts: 861 Credit: 29,352,955 RAC: 0 |
Lost task messages here within the last hour. <shrug> |
-BeNt- Send message Joined: 17 Oct 99 Posts: 1234 Credit: 10,116,112 RAC: 0 |
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! |
hbomber Send message Joined: 2 May 01 Posts: 437 Credit: 50,852,854 RAC: 0 |
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! |
-BeNt- Send message Joined: 17 Oct 99 Posts: 1234 Credit: 10,116,112 RAC: 0 |
Yeah, great, just got 170 tasks marked as timeouted, BEFORE knowing that problem exists and happily hitting "Update" after each 64 tasks reported. 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! |
©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.