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: 21
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Project Name: Help Conquer Cancer
Created: 18/03/11 Name: X0000071841313200607211817 Minimum Quorum: 2 Replication: 2 X0000071841313200607211817_ 2-- - In Progress 20/03/11 14:52:18 24/03/11 14:52:18 0.00 0.0 / 0.0 X0000071841313200607211817_ 3-- - In Progress 20/03/11 14:51:48 24/03/11 14:51:48 0.00 0.0 / 0.0 X0000071841313200607211817_ 1-- 640 Error 19/03/11 23:02:44 20/03/11 07:05:01 2.16 50.8 / 0.0 X0000071841313200607211817_ 0-- 640 Error 19/03/11 23:02:41 20/03/11 14:50:12 2.19 49.2 / 0.0 I am _1 Project Name: Help Conquer Cancer Created: 08/03/11 Name: X0000065781006200603141434 Minimum Quorum: 2 Replication: 2 X0000065781006200603141434_ 4-- 640 Valid 20/03/11 14:52:31 21/03/11 13:34:33 2.13 35.3 / 36.6 X0000065781006200603141434_ 3-- 640 Valid 20/03/11 14:50:47 21/03/11 07:35:04 2.11 37.8 / 36.6 X0000065781006200603141434_ 2-- 640 Error 20/03/11 07:35:56 20/03/11 14:49:30 1.92 51.5 / 0.0 X0000065781006200603141434_ 0-- 640 Error 10/03/11 07:37:04 11/03/11 17:09:33 1.86 36.7 / 0.0 X0000065781006200603141434_ 1-- - No Reply 10/03/11 07:34:38 20/03/11 07:34:38 0.00 0.0 / 0.0 I am _2 On both occasions my wingman also errored These are on bullet proof rigs the first error is on a machine that has returned 767 wu the 2nd error is on a machine that has returned 8345 wu, with no hardware changes in either cheers |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Suspect an initial distribution file glitch. Certainly the _3 and _4 validating suggests a bad seed. Watch the outcome of your second sample and any further errors. It would be nice if you clicked in the error link and posted a copy of the Result Log, then couple the completion time to any log information in the stdoutdae.txt or stdoutdae.old files to see if it what the fail constituted.
--//-- PS, bullet proof is until one of those system/security software updates decide to go rouge ;>) |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Result Name: X0000071841313200607211817_ 1--
<core_client_version>6.10.58</core_client_version> <![CDATA[ <stderr_txt> In ExtractGlcmFeatures: End of 0 iteration of outer loop. In ExtractGlcmFeatures: End of 1 iteration of outer loop. In ExtractGlcmFeatures: End of 2 iteration of outer loop. In ExtractGlcmFeatures: End of 3 iteration of outer loop. In ExtractGlcmFeatures: End of 4 iteration of outer loop. In ExtractGlcmFeatures: End of 5 iteration of outer loop. In ExtractGlcmFeatures: End of 6 iteration of outer loop. In ExtractGlcmFeatures: End of 7 iteration of outer loop. In ExtractGlcmFeatures: End of 8 iteration of outer loop. In ExtractGlcmFeatures: End of 9 iteration of outer loop. In ExtractGlcmFeatures: End of 10 iteration of outer loop. In ExtractGlcmFeatures: End of 11 iteration of outer loop. In ExtractGlcmFeatures: End of 12 iteration of outer loop. In ExtractGlcmFeatures: End of 13 iteration of outer loop. In ExtractGlcmFeatures: End of 14 iteration of outer loop. In ExtractGlcmFeatures: End of 15 iteration of outer loop. In ExtractGlcmFeatures: End of 16 iteration of outer loop. In ExtractGlcmFeatures: End of 17 iteration of outer loop. In ExtractGlcmFeatures: End of 18 iteration of outer loop. In ExtractGlcmFeatures: End of 19 iteration of outer loop. In ExtractGlcmFeatures: End of 20 iteration of outer loop. In ExtractGlcmFeatures: End of 21 iteration of outer loop. In ExtractGlcmFeatures: End of 22 iteration of outer loop. In ExtractGlcmFeatures: End of 23 iteration of outer loop. In ExtractGlcmFeatures: End of 24 iteration of outer loop. called boinc_finish </stderr_txt> ]]> Result Name: X0000065781006200603141434_ 2-- <core_client_version>6.10.58</core_client_version> <![CDATA[ <stderr_txt> In ExtractGlcmFeatures: End of 0 iteration of outer loop. In ExtractGlcmFeatures: End of 1 iteration of outer loop. In ExtractGlcmFeatures: End of 2 iteration of outer loop. In ExtractGlcmFeatures: End of 3 iteration of outer loop. In ExtractGlcmFeatures: End of 4 iteration of outer loop. In ExtractGlcmFeatures: End of 5 iteration of outer loop. In ExtractGlcmFeatures: End of 6 iteration of outer loop. In ExtractGlcmFeatures: End of 7 iteration of outer loop. In ExtractGlcmFeatures: End of 8 iteration of outer loop. In ExtractGlcmFeatures: End of 9 iteration of outer loop. In ExtractGlcmFeatures: End of 10 iteration of outer loop. In ExtractGlcmFeatures: End of 11 iteration of outer loop. In ExtractGlcmFeatures: End of 12 iteration of outer loop. In ExtractGlcmFeatures: End of 13 iteration of outer loop. In ExtractGlcmFeatures: End of 14 iteration of outer loop. In ExtractGlcmFeatures: End of 15 iteration of outer loop. In ExtractGlcmFeatures: End of 16 iteration of outer loop. In ExtractGlcmFeatures: End of 17 iteration of outer loop. In ExtractGlcmFeatures: End of 18 iteration of outer loop. In ExtractGlcmFeatures: End of 19 iteration of outer loop. In ExtractGlcmFeatures: End of 20 iteration of outer loop. In ExtractGlcmFeatures: End of 21 iteration of outer loop. In ExtractGlcmFeatures: End of 22 iteration of outer loop. In ExtractGlcmFeatures: End of 23 iteration of outer loop. In ExtractGlcmFeatures: End of 24 iteration of outer loop. called boinc_finish </stderr_txt> ]]> post in same sequence as OP Bullet proof well as bullet proof as can be, they work all win updates are off thanks for the input sekerob cheers |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Could be a galactic cosmic ray that hit the servers and interfered with the hopper... the sun is still relatively low in it's cycle so there's more 10Be coming down than average. Think there was also some extra solar storms from direct hit CME's and more than average Aurora Borealis over the Toronto region that day
(who knows did I make that up as I went, but if nothing else, blame the neutrino's that are supposed to not interact with anything on planet earth, almost never but it's a possible to rock the rock just briefly ;>) |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Could be a galactic cosmic ray that hit the servers and interfered with the hopper... the sun is still relatively low in it's cycle so there's more 10Be coming down than average. Think there was also some extra solar storms from direct hit CME's and more than average Aurora Borealis over the Toronto region that day (who knows did I make that up as I went, but if nothing else, blame the neutrino's that are supposed to not interact with anything on planet earth, almost never but it's a possible to rock the rock just briefly ;>) Darn them solar winds, Darn* them Thanks for the input cheers *edited to appropriate forum language - ErikaT Edit By OP I have been around forums for a decade, come across ludicrous FAQs, comical Ali rules, been involved in debate/arguments/points, having reached the Morgan Freeman (Ellis Boyd "Red" Redding) Shawshank Redemption parole hearing attitude in regards to forums " so you go on stamp you forms sonny and stop wasting my time, because to tell you the truth I don't give a ****" This edit by erikat almost brought me out of retirement, what some people consider as valuable input, extraordinary. I would love to know why the edited word was. [Edit 3 times, last edit by Former Member at Mar 21, 2011 10:00:01 PM] |
||
|
Atlantis555
Cruncher Russia Joined: Jun 18, 2010 Post Count: 32 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Sekerob! What's that, 3 pages of server aborted?
![]() |
||
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2990 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
It's nothing to worry about - it's just the WCG techs are attempting to clean out the HCC queue as quickly as possible. Thus (as explained in the other thread, here -> Prepping for version 6.42 of Help Conquer Cancer ), they've now overlaid work for those WU's still out there. Therefore, where as normally, there are only 2 replica WU's sent out for each task, they've currently upped this to 4. Thus, as soon as the first 2 have been returned and validated, the system will attempt to Server Abort the rest (that is, when the next communication between the main Server and the respective computers which still have those WU's outstanding, the system will abort them).
----------------------------------------![]() [Edit 2 times, last edit by gb009761 at Apr 8, 2011 2:00:38 PM] |
||
|
z2000
Advanced Cruncher Joined: Feb 27, 2011 Post Count: 116 Status: Offline |
It looks like those work units were completed before you began yours.
----------------------------------------![]() [Edit 1 times, last edit by z2000 at Apr 8, 2011 2:02:26 PM] |
||
|
bernie99
Cruncher Joined: Jun 15, 2009 Post Count: 7 Status: Offline |
To Skyrob.
I'am in a same situation. I think it's wasted time !!!! for all Pourquoi envoyer 4 jobs alors que 2 suffisent ? J'ai l'impression de perdre mon temps !!! Nom du projet: Help Conquer Cancer Créé le :: 31/03/11 Nom: X0000073700859200608031013 Quorum minimum: 2 Réplication: 4 Nom du résultat Numéro de version de l'application Etat Heure d'envoi Heure de retour prévue / Heure de retour Temps d'unité centrale (heures) Crédit BOINC demandé/accordé X0000073700859200608031013_ 3-- 640 Serveur abandonné 07/04/11 15:52:32 08/04/11 13:48:31 0,00 0,0 / 0,0 it's mine X0000073700859200608031013_ 2-- 640 Serveur abandonné 06/04/11 08:56:22 08/04/11 09:09:36 0,00 0,0 / 0,0 X0000073700859200608031013_ 0-- 640 Valide 01/04/11 14:27:56 08/04/11 08:58:29 2,70 44,9 / 41,7 X0000073700859200608031013_ 1-- 640 Valide 01/04/11 14:26:07 08/04/11 06:50:23 2,19 38,4 / 41,7 Will 6.4 solve the problem ? Thanks |
||
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2990 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
bernie99, as the system was able to 'Server Abort' those 2 WU's before they started, where's the 'waste of time'?. I'd much rather the WCG techs do it this way, than have to wait until the natural clearance of WU's through the system - which would probably take a little over 10 days (i.e. the usual deadline, plus 2, 3, 4 days for repair WU's to be returned). After all, they did wait 3-4 days before over scheduling the WU's, so anyone with an average cache, would have had them all cleared out before the 3rd (and subsequent) copy was issued.
----------------------------------------We've got to keep in mind, why they're doing this - so as to get a new version of the app out quickly, one which will increase the speed of HCC WU's being crunched. ![]() |
||
|
|
![]() |