Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 177
|
![]() |
Author |
|
Bugg
Senior Cruncher USA Joined: Nov 19, 2006 Post Count: 271 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Well, since Mar 9, 2012 I've been getting this in my log for days now:
----------------------------------------3/9/2012 7:42:02 PM | World Community Grid | Didn't resend lost task c4cw_target05_160338721_0 (expired) 3/9/2012 7:42:02 PM | World Community Grid | Didn't resend lost task c4cw_target05_160364807_0 (expired) 3/9/2012 7:42:02 PM | World Community Grid | Didn't resend lost task c4cw_target05_160458750_0 (expired) 3/9/2012 7:42:02 PM | World Community Grid | Didn't resend lost task c4cw_target05_160456102_0 (expired) They're still listed on my Results Status page as being In Progress, even though they were done and uploaded, just not reported. The reason they weren't reported is because that server or whatever was down when it tried to report each of them. Was this the problem mentioned earlier where someone said those work units are now just gone? Also, how would I stop BOINC from continually posting this in the log? ![]() i5-12600K (3.7GHz), 32GB DDR5, Win11 64bit Home |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yes, the same issue, where my machine did fetch the lost copies and recrunched them. Queer to say the least why your device did not fetch those copies again... There's a timelimit, the message suggests says so, after which a lost task is really considered lost. Device off, ad interim device reset, too much in cache already to not fetch work.... don't know.
At any rate, they'll likely go No Reply on whatever date they mature and a new copy send out. Have another look at the WU quorum detail if interested. --//-- |
||
|
Bugg
Senior Cruncher USA Joined: Nov 19, 2006 Post Count: 271 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Well, really not much I can do either way, right? So I just won't worry about 'em. You say they'll get resent out to someone, that's cool. Just making sure they're not lost/gone for good.
----------------------------------------Thanks. ![]() i5-12600K (3.7GHz), 32GB DDR5, Win11 64bit Home |
||
|
Bugg
Senior Cruncher USA Joined: Nov 19, 2006 Post Count: 271 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
SekeRob, perhaps you could explain how I can get those lines to stop appearing in my event log. The ones that I posted above, as it still seems to be trying to send them, even though it says it didn't resend them. It does it every time it does a work fetch or report of another work unit.
----------------------------------------![]() i5-12600K (3.7GHz), 32GB DDR5, Win11 64bit Home |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
same situation here also
----------------------------------------Result Name App Version Number Status Sent Time Time Due / Return Time CPU Time (hours) Claimed/ Granted BOINC Credit SN2S_ AAB20796_ 0000013_ 0203_ 2-- - In Progress 3/6/12 08:41:08 3/15/12 01:26:10 0.00 0.0 / 0.0 SN2S_ AAB20796_ 0000013_ 0203_ 0-- 613 Valid 2/25/12 08:38:36 2/26/12 07:12:59 7.86 160.1 / 186.9 SN2S_ AAB20796_ 0000013_ 0203_ 1-- 613 Valid 2/25/12 08:38:36 3/6/12 14:21:56 11.13 213.6 / 186.9 and it does not show up as a wu in progress on my pc but guess it will go away on the 15th of march [Edit 1 times, last edit by Former Member at Mar 13, 2012 3:15:17 AM] |
||
|
Rickjb
Veteran Cruncher Australia Joined: Sep 17, 2006 Post Count: 666 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Repair WUs are still coming with normal 10-day Report deadlines, not the shorter (5-day?) deadlines previously used for these WUs.
----------------------------------------This applies to devices that are running quorum of 1 on ZR projects. Will repair WU deadlines revert to the short dates automatically, or is a tweak to the new server software needed? [Edit, 14 Mar 12: Newly-issued repair WUs now have the shorter deadlines. However, some of my machines that have just been re-declared fast-returners may temporarily lose that status when I bump up their work queues in preparation for the impending WCG server outage. [/Edit] [Edit 1 times, last edit by Rickjb at Mar 14, 2012 2:28:12 AM] |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Short answer: No the reverting is a manual activation action. Could be today, could be next week. Depends on how many devices the techs see as having rebuild that =< 0.2% error rating since March 6.
WCG used a fraction field with the old server software to apply to repair tasks (new copies of those ending in Error/Invalid/Aborted etc). So 40%, which is the repair formula applied to the original deadline period turns HCC to 0.4 * 7 days = 2.8 days and all others 0.4 * 10 days = 4 days... plus whatever fraction that was determined as needed for big repairs going to slow devices that still manage a regular return time of under 2 days... Some have received repairs with 12 days deadline, indicating that this last piece is still working. The repair fraction switched off by word of knreed until enough statistical data has accumulated to assign the reliability rating again, for only then can they also start the repair feeds again. Repairs have feeder priority and had that continued would it have completely clogged the distributor... there were no reliable rated devices. --//-- P.S. The Beta's have a standard of 4 days and get a repair deadline of 1.6 days. FAQ: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=17160 |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Got a HFCC repair WU (_2):
HFCC_ target-8_ 02394038_ target-8_ 0000_ 2-- - In Progress 13.03.12 15:33:30 19.03.12 15:33:30 0.00 0.0 / 0.0 HFCC_ target-8_ 02394038_ target-8_ 0000_ 1-- - In Progress 13.03.12 15:33:20 19.03.12 15:33:20 0.00 0.0 / 0.0 HFCC_ target-8_ 02394038_ target-8_ 0000_ 0-- 640 Error 13.03.12 14:58:23 13.03.12 15:01:34 0.00 119.0 / 0.0 So are the shorter deadlines for repair WUs already in place? |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yes and No, according what you just posted. By the looks the _1 and _2 have a 6 day deadline and were issued today right after the _0 failed. 6 days is not 10 days, but then I dont know what the current standard deadline is for HFCC. The SN2S do 10 days as always, but those are quorum 2 also.
--//-- |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
For Techs, another possible switch over issue: The first result returned is declared Inconclusive when the second returned is outright in error. Would it not be proper to leave the 1st in Pending Validation state? To me and most, there was no quorum validation conducted.
CMD2_ 2010-2ZFH_ C.clustersOccur-3CTZ_ A.clustersOccur_ 15_ 2-- - In Progress 3/14/12 22:31:53 3/20/12 22:31:53 0.00 0.0 / 0.0 CMD2_ 2010-2ZFH_ C.clustersOccur-3CTZ_ A.clustersOccur_ 15_ 1-- 640 Inconclusive 3/13/12 22:02:11 3/14/12 22:31:37 6.00 103.7 / 0.0 CMD2_ 2010-2ZFH_ C.clustersOccur-3CTZ_ A.clustersOccur_ 15_ 0-- 640 Error 3/13/12 21:59:09 3/13/12 22:05:33 0.00 0.0 / 0.0 --//-- |
||
|
|
![]() |