| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Just lost my entire cache of workunits on 2 machines! |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 52
|
|
| Author |
|
|
deltavee
Ace Cruncher Texas Hill Country Joined: Nov 17, 2004 Post Count: 4894 Status: Offline Project Badges: 
|
I was wondering why I was getting so many repair WUs. After reading this thread, now I know. Have had no problems.
|
||
|
|
kateiacy
Veteran Cruncher USA Joined: Jan 23, 2010 Post Count: 1027 Status: Offline Project Badges: 
|
So far no problems myself. However I notice that some WUs that I've received recently and haven't started running yet don't show an App Version. For example, here are a couple of repair jobs I got from people who had the error. They show app version 611 or 640; mine shows "-".
----------------------------------------Result Name App Version Number Status Sent Time Time Due / Return Time CPU Time (hours) Claimed/ Granted BOINC Credit HFCC_ L4_ 00935974_ L4_ 0001_ 1-- - In Progress 3/1/11 13:54:12 3/5/11 13:54:12 0.00 0.0 / 0.0 HFCC_ L4_ 00935974_ L4_ 0001_ 0-- 611 Error 2/28/11 10:18:41 3/1/11 13:46:18 0.98 12.3 / 0.0 Result Name App Version Number Status Sent Time Time Due / Return Time CPU Time (hours) Claimed/ Granted BOINC Credit HFCC_ L4_ 00966000_ L4_ 0000_ 1-- - In Progress 3/1/11 13:54:54 3/5/11 13:54:54 0.00 0.0 / 0.0 HFCC_ L4_ 00966000_ L4_ 0000_ 0-- 640 Error 3/1/11 04:34:08 3/1/11 13:45:59 0.00 0.0 / 0.0 I'm running BOINC 6.10.17 under Ubuntu 10.04.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The app version is I think (... ergo sum) only reported when completed... or?
--//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Two of my machines had their queues wiped out. New incoming work seems to executing fine.
|
||
|
|
kernel_trick
Cruncher Joined: Aug 27, 2007 Post Count: 17 Status: Offline Project Badges: 
|
Lost: ~450 WU's
---------------------------------------- |
||
|
|
PMH_UK
Veteran Cruncher UK Joined: Apr 26, 2007 Post Count: 786 Status: Offline Project Badges: 
|
Ok with 640, including this one already validated against a 617:
----------------------------------------ts01_ b133_ pr67a0_ 2-- 640 Valid 01/03/11 11:32:49 01/03/11 15:40:03 4.07 63.1 / 64.3 ts01_ b133_ pr67a0_ 1-- 617 Valid 27/02/11 01:49:35 27/02/11 10:43:26 4.40 65.6 / 64.3 ts01_ b133_ pr67a0_ 0-- 617 Error 27/02/11 01:49:25 01/03/11 11:12:17 0.00 0.0 / 0.0 All appears OK now, not sure why my 3 Linux 64 and other Win PCs did not get hit (yet). Paul.
Paul.
|
||
|
|
Snowweasel
Cruncher United States Joined: Nov 22, 2005 Post Count: 33 Status: Offline Project Badges:
|
I had upped my cache overnight to fetch a few more DDDT2s, and my XP machine dumped them all like this. I haven't researched it much except that it looks like similar errors, and one is running currently on that machine and is 96% complete.
----------------------------------------Had an error on my Win7 machine, but it looks like something different.  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
For my host this started at 1:28 am on 3/1 (gmt) It was running only WCG, actually only DDDT-2, on 3 cores. All simultaneously got the "exited with zero status but no 'finished' file message, but restarted and completed/validated using 6.17.. All succeeding tasks in the cache that I've checked have one of 3 messages in its error status, re wcg_dddt2_charmm_6.17_windows_intelx86
----------------------------------------1) signature verification error, -120 2) input file missing or invalid (no sig error mentioned)- 163 3) input file missing or invalid (no sig error mentioned)- 120 The 6.40 app started downloading @ to the host @ 4:41 am gmt, finished with image files within about 2 minutes. First sig verification error in my client log is at 5:28 am gmt During the next 4 hours all the cached wus errored out, plus more tasks were downloaded and also errored out. When I got home there were 3 tasks running 6.40 and one waiting (4-core box) and my quota was blown. I forced an update to report the 150 or so remaining errored tasks at 7:24 am gmt Windows XP Pro SP3 client 6.10.58 Intel Q9450 Thanks for resetting quotas. [Edit 2 times, last edit by Former Member at Mar 1, 2011 8:17:59 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Forced the hand and now have 6.17 and 6.40 DDDT2's running side by side. 1 Finished without a hitch since.
Client: 6.10.58 OS: Ubuntu 10.10 2.6.35-27.48 CPU: Quad Mem: 4GB, 3.5 allowed during use. 29% commit. AV: -- FW: -- --//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
All my caches errored out as well. That was 104 WU's lost so I guess my machine reliabilities took a hit as well. As of now, I was able to force 2 6.40 WU's for my 2 core machine and only 3 for my 4 core system, Kind of limping along right now.
Running Fedora 13 and 14 Linux x86_64 with client 6.10.58 64 bit. |
||
|
|
|