| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Cure Muscular Dystrophy - Phase 2 Forum
Thread: Aborted WUs |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 7
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I've had a huge number of CMD2_0006 WUs self abort overnight and suspect this was due to them running out of time, as almost all were due to return on 18 June. I now have only 3 CMD2_0006 & 4 CMD2_0010 WUs left to run. Very strange!
----------------------------------------Oops! CMD2_0006/7/8 WUs just began downloading, but not many.  [Edit 1 times, last edit by Former Member at Jun 18, 2009 4:39:44 AM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
What was their original 'sent' date/time? If you post a few of these 'aborted' lines from the Result Status page we can tell more with less guess. Also click the Work Unit name of one aborted and copy past the distribution detail which gives us some info on the version these jobs were processed.
----------------------------------------1. If these jobs had a sent time of June 4, they were surely version 6.13 2. If these jobs had a sent time after June 10, they were surely version 6.14
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
As requested, and in that order.
 CMD2_ 0006-2A5AA.clustersOccur-MYH1.clustersOccur_ 229_ 403648_ 403955_ 1-- Fast-PC Error 04/06/09 03:57:30 18/06/09 04:20:48 0.00 0.0 / 0.0 CMD2_ 0006-2A5AA.clustersOccur-MYH1.clustersOccur_ 170_ 300546_ 300788_ 0-- Fast-PC Error 04/06/09 03:57:30 18/06/09 04:20:48 0.00 0.0 / 0.0 CMD2_ 0006-2A5AA.clustersOccur-MYH1.clustersOccur_ 170_ 300299_ 300545_ 1-- Fast-PC Error 04/06/09 03:57:30 18/06/09 04:20:48 0.00 0.0 / 0.0 CMD2_ 0006-2A5AA.clustersOccur-MOESA.clustersOccur_ 101_ 367874_ 368525_ 0-- Fast-PC Error 04/06/09 03:57:30 18/06/09 04:20:48 0.00 0.0 / 0.0 CMD2_ 0006-2A5AA.clustersOccur-KPYM.clustersOccur_ 51_ 128159_ 128699_ 0-- Fast-PC Error 04/06/09 03:57:30 18/06/09 04:20:48 0.00 0.0 / 0.0 ----------------------------------------------------------------------------------- CMD2_ 0006-2A5AA.clustersOccur-MYH1.clustersOccur_ 229_ 403648_ 403955_ 2-- - In Progress 18/06/09 04:14:39 23/06/09 18:38:39 0.00 0.0 / 0.0 |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Okay, that's some results that clearly passed their deadline i.e. became redundant, but am taken aback by them not being marked "aborted", rather "error". What client version do you run, though point 1 below should tell too? What OS?
----------------------------------------Then, 1. click on one such error link and post content 2. Ref. my earlier post request, click the Work Unit name of one "aborted" task you posted above and copy/paste the details which gives us some info on the version these jobs were processed.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Jun 18, 2009 5:33:51 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Done.
----------------------------------------Client ver = 6.6.28 OS = Vista Home Premium. Error link = <core_client_version>6.6.28</core_client_version> Result name = CMD2_ 0006-2A5AA.clustersOccur-MYH1.clustersOccur_ 229_ 403648_ 403955_ 2-- - In Progress 18/06/09 04:14:39 23/06/09 18:38:39 0.00 0.0 / 0.0 CMD2_ 0006-2A5AA.clustersOccur-MYH1.clustersOccur_ 229_ 403648_ 403955_ 0-- 613 Pending Validation 04/06/09 04:07:20 04/06/09 17:06:31 1.76 31.7 / 0.0 CMD2_ 0006-2A5AA.clustersOccur-MYH1.clustersOccur_ 229_ 403648_ 403955_ 1-- 613 Error 04/06/09 03:57:30 18/06/09 04:20:48 0.00 0.0 / 0.0 All were shown as aborted by the client. [Edit 2 times, last edit by Former Member at Jun 18, 2009 5:49:31 AM] |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
hmmm, I think the developers kicked in the 6.6 self abort upon reaching deadline, if not started yet function. The WCG validator is not set to recognize that condition yet, the techs working to upgrade the server side BOINC daemons, but when getting to 6.6 level I don't know **.
----------------------------------------6.6. is NOT ready, though I'm sure many middle of the road, single DC project crunchers will tell they have no problems. Development continues and bugs continue to be reported and I have sincere doubts after my own experiences it's remotely ready for the big public, though most were so kindly told via the message log there was this new version from Berkeley. See FAQ to fix that: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=25784 Edit: ** 'Error' results go against the daily quota of reliable devices. Please lower your cache as this project is going to run for many months and the WCG grid is very stable. 4 Days tops and you'll have them almost all the time.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 3 times, last edit by Sekerob at Jun 18, 2009 8:59:48 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Thanks for the information and help Sekerob. I've installed 6.2.28 and set my cache to 4 days, as suggested.
|
||
|
|
|