| 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: 48
|
|
| Author |
|
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1684 Status: Offline Project Badges:
|
Hello,
----------------------------------------I received several HCC WUs during the last night (2009-04-10 -> 2009-04-11) with a "High Priority" status for my Q9600 system (kerdiwi03). Finally, all the WUs are in error and boinc (5.10.45) crashed completely (Windows XP error message related to Visual C++). Only a system reboot and the download of fully new WUs made a restart possible. 7 WUs are concerned with this problem with similar error message:
<core_client_version>5.10.45</core_client_version> I am unable to investigate the situation on two other remote systems For new crunchers ! I have to mention that I experience such crash for the first time after around 27 months. So, you should not be too much disappointed and frustrated; usually WCG projects run very accurately. Anyway, I wish everybody a great Easter time. Cheers, Yves |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7847 Status: Offline Project Badges:
|
4/11/2009 1:29:49 PM|World Community Grid|Computation for task X0000057420350200510121420_1 finished
----------------------------------------4/11/2009 1:29:49 PM|World Community Grid|Starting X0000057621100200510171120_0 4/11/2009 1:29:49 PM|World Community Grid|Starting task X0000057621100200510171120_0 using hcc1 version 606 4/11/2009 1:29:51 PM|World Community Grid|Started upload of X0000057420350200510121420_1_0 4/11/2009 1:30:03 PM|World Community Grid|Finished upload of X0000057420350200510121420_1_0 4/11/2009 2:28:08 PM|World Community Grid|Computation for task X0000057621100200510171120_0 finished 4/11/2009 2:28:08 PM|World Community Grid|Output file X0000057621100200510171120_0_0 for task X0000057621100200510171120_0 absent 4/11/2009 2:28:08 PM|World Community Grid|Starting X0000057681126200509190906_0 4/11/2009 2:28:08 PM|World Community Grid|Starting task X0000057681126200509190906_0 using hcc1 version 606 4/11/2009 2:28:10 PM|World Community Grid|Computation for task X0000057681126200509190906_0 finished 4/11/2009 2:28:10 PM|World Community Grid|Output file X0000057681126200509190906_0_0 for task X0000057681126200509190906_0 absent 4/11/2009 2:28:10 PM|World Community Grid|Starting HFCC_t1_00251579_TrkB_0003_0 4/11/2009 2:28:10 PM|World Community Grid|Starting task HFCC_t1_00251579_TrkB_0003_0 using hfcc version 610 4/11/2009 2:29:11 PM|World Community Grid|Sending scheduler request: To fetch work. Requesting 167347 seconds of work, reporting 3 completed tasks 4/11/2009 2:29:16 PM|World Community Grid|Scheduler request succeeded: got 2 new tasks I just had two of these units go bad. I have not had any other on this machine. Not worried but will monitor. Windows 2K, Boinc v5.10.45. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
Zanth
Advanced Cruncher USA Joined: Aug 18, 2008 Post Count: 88 Status: Offline Project Badges:
|
I had a few go bad the other day, but the last few I got have been fine.
----------------------------------------![]() |
||
|
|
rkar22
Cruncher Joined: Nov 17, 2004 Post Count: 48 Status: Offline Project Badges:
|
I just noticed a new variation of WU this thread is about. While the ones I saw so far errored out reliably before having consumed any CPU time, this one seems to be a bit different:
X0000057701466200509190901_ 4-- In Progress 12.04.09 07:51:27 15.04.09 15:03:27 0.00 0.0 / 0.0 X0000057701466200509190901_ 3-- Inconclusive 11.04.09 03:11:49 12.04.09 07:22:19 8.40 47.8 / 0.0 X0000057701466200509190901_ 2-- Error 10.04.09 23:20:16 11.04.09 03:02:54 0.00 0.0 / 0.0 X0000057701466200509190901_ 1-- Inconclusive 10.04.09 18:12:32 11.04.09 08:55:35 12.96 91.1 / 0.0 X0000057701466200509190901_ 0-- Error 10.04.09 18:12:30 10.04.09 23:17:41 0.00 0.0 / 0.0 The two errored out copies ran (or rather had no chance to start to run) on Linux clients and generated the well known result logs, the two being in Inconclusive state produced the same result logs as successfully completing WUs do. I'll force my copy to proceed now ... ... and it errored out immediately. Now I'm very curious how the Inconclusive copies will end up ... |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges:
|
Robert, which core client version do you see in the Result Log of these Inconclusive WUs?
----------------------------------------Just for curiosity, or maybe for a clue... Jean. |
||
|
|
rkar22
Cruncher Joined: Nov 17, 2004 Post Count: 48 Status: Offline Project Badges:
|
Jean, I should have checked the client versions right away, before leaving my computers alone for a bit more than a day - now I have no more access to this information and don't even know how those two initially inconclusive copies ended up, as meanwhile all of the errored out WUs disappeared from my Results Status page
(except for one where one copy is still in progress).I still keep receiving a few "repair" units for WUs with initial copies sent out on Friday after 3 am ... maybe there will be another WU of this kind with inconclusive copies ... |
||
|
|
knreed
Former World Community Grid Tech Joined: Nov 8, 2004 Post Count: 4504 Status: Offline Project Badges:
|
We modified things last week so that instead of relying on 'on the fly' compression for the download of the input data files we are pre-compressing them. This is being done for FAAH, CEP1, DDDT, RICE and HFCC. We tried it briefly for Help Conquer Cancer but it didn't yield any savings. What you are seeing with the errors are a side effect of the compression that we looking into now. Unfortunately this means that 1/4th of the workunits for a day (about 12,000) were loaded and are erroring out. We have now cancelled these and are re-running them without the pre-compression.
Workunits effected have a file suffix of .gzb The compression is working as desired for the other projects and it will continue with them. However, for Help Conquer Cancer we will not use it. We apologize for the issues and hope they are behind us now. If you want to check if any of your workunits on your client are impacted, simply do an 'update' from the Projects tab on the advanced view for World Community Grid. This will contact the servers and if you have any of the errant workunits, they will be canceled on your client. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Last night 13 April my Quad Core2 crunching for cancer started showing computation errors on every work unit as it started up. I thought it was my system so I shut Boinc down and re-installed Boinc but still had errors.
It was good to know now it was the work units and not my system. |
||
|
|
|