| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Android Support Forum
Thread: FightAIDS@Home - Vina 17 pages of Status Error after 2 Pages of Status Valid |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 5
|
|
| Author |
|
|
yoro42
Ace Cruncher United States Joined: Feb 19, 2011 Post Count: 8979 Status: Offline Project Badges: 
|
Last Valid completion on Ematic Quad Core Tablet Mdl EGQ307BL.:
----------------------------------------FAHV_ x3NF8_ B_ IN_ FBPa_ rig_ 0211360_ 1725_ 2-- 716 Valid 4/21/14 02:45:59 4/22/14 01:44:30 2.51 15.2 / 18.9 FAHV_ x3NF8_ B_ IN_ FBPa_ rig_ 0211360_ 1725_ 1-- 716 Valid 4/21/14 02:44:03 4/21/14 09:32:14 5.25 22.6 / 18.9 FAHV_ x3NF8_ B_ IN_ FBPa_ rig_ 0211360_ 1725_ 0-- 716 Error 4/21/14 02:42:14 4/21/14 02:44:37 0.00 0.1 / 0.0 (MyLast Valid) Result Log Result Name: FAHV_ x3NF8_ B_ IN_ FBPa_ rig_ 0211360_ 1725_ 1-- <core_client_version>7.3.12</core_client_version> <![CDATA[ <stderr_txt> INFO: No state to restore. Start from the beginning. [21:14:13] Number of tasks = 2 [21:14:13] Starting task 0,CPU time is 0.000000. [21:14:13] ./ZINC12818443.pdbqt size = 33 7 ../../projects/www.worldcommunitygrid.org/fahv.x3NF8_B_IN_FBPa_rig.pdbqt size = 2812 0 [23:56:56] Finished task #0 cpu time used 9683.760000 [23:56:56] Starting task 1,CPU time is 9683.760000. [23:56:56] ./ZINC12818445.pdbqt size = 31 8 ../../projects/www.worldcommunitygrid.org/fahv.x3NF8_B_IN_FBPa_rig.pdbqt size = 2812 0 [02:32:09] Finished task #1 cpu time used 9228.320000 02:32:09 (12130): called boinc_finish Then the errors begin the first failure follows: FAHV_ x3NF8_ A_ IN_ Y3a_ rig_ 0210817_ 1196_ 5-- 716 Error 4/21/14 04:14:19 4/22/14 01:13:04 6.79 45.3 / 0.0 First Failure Result Log Result Name: FAHV_ x3NF8_ A_ IN_ Y3a_ rig_ 0210817_ 1196_ 5-- <core_client_version>7.3.12</core_client_version> <![CDATA[ <message> process exited with code 195 (0xc3, -61) </message> <stderr_txt> INFO: No state to restore. Start from the beginning. [00:31:16] Number of tasks = 3 [00:31:16] Starting task 0,CPU time is 0.000000. [00:31:16] ./ZINC09871965.pdbqt size = 32 5 ../../projects/www.worldcommunitygrid.org/fahv.x3NF8_A_IN_Y3a_rig.pdbqt size = 2790 0 [07:22:20] Finished task #0 cpu time used 24446.450000 [07:22:20] Starting task 1,CPU time is 24446.450000. [07:22:20] ./ZINC09871967.pdbqt size = 32 5 ../../projects/www.worldcommunitygrid.org/fahv.x3NF8_A_IN_Y3a_rig.pdbqt size = 2790 0 Quit requested: Exiting [17:34:42] Number of tasks = 3 [17:34:42] Starting task 1,CPU time is 24446.450000. [17:34:42] ./ZINC09871967.pdbqt size = 32 5 ../../projects/www.worldcommunitygrid.org/fahv.x3NF8_A_IN_Y3a_rig.pdbqt size = 2790 0 ERROR: VINA was killed by signal 9. Retrying task. [17:34:48] Starting task 1,CPU time is 24446.450000. [17:34:48] ./ZINC09871967.pdbqt size = 32 5 ../../projects/www.worldcommunitygrid.org/fahv.x3NF8_A_IN_Y3a_rig.pdbqt size = 2790 0 ERROR: VINA was killed by signal 9. 17:34:58 (18550): called boinc_finish </stderr_txt> ]]> SEVENTEEN (17) PAGES later of the same errors (process exited with code 195 (0xc3, -61)) the most recent two failures follow: FAHV_ x3NF8_ B_ IN_ LEDGFa_ rig_ 0211795_ 2818_ 4-- android_232dc43 a Error 4/22/14 17:16:11 4/22/14 17:20:26 0.04 / 0.05 0.1 / 0.0 FAHV_ x3NF8_ A_ IN_ Y3b_ rig_ 0211066_ 0958_ 7-- android_232dc43 a Error 4/22/14 17:09:23 4/22/14 17:18:18 0.01 / 0.12 0.4 / 0.0 Result Log Result Name: FAHV_ x3NF8_ B_ IN_ LEDGFa_ rig_ 0211795_ 2818_ 4-- <core_client_version>7.3.12</core_client_version> <![CDATA[ <message> process exited with code 195 (0xc3, -61) </message> <stderr_txt> INFO: No state to restore. Start from the beginning. [10:16:16] Number of tasks = 3 [10:16:16] Starting task 0,CPU time is 0.000000. [10:16:16] ./ZINC35388298.pdbqt size = 30 6 ../../projects/www.worldcommunitygrid.org/fahv.x3NF8_B_IN_LEDGFa_rig.pdbqt size = 2830 0 ERROR: VINA was killed by signal 9. Retrying task. [10:16:30] Starting task 0,CPU time is 0.000000. [10:16:30] ./ZINC35388298.pdbqt size = 30 6 ../../projects/www.worldcommunitygrid.org/fahv.x3NF8_B_IN_LEDGFa_rig.pdbqt size = 2830 0 ERROR: VINA was killed by signal 9. 10:19:00 (10993): called boinc_finish </stderr_txt> ]]> Result Log Result Name: FAHV_ x3NF8_ A_ IN_ Y3b_ rig_ 0211066_ 0958_ 7-- <core_client_version>7.3.12</core_client_version> <![CDATA[ <message> process exited with code 195 (0xc3, -61) </message> <stderr_txt> INFO: No state to restore. Start from the beginning. [10:09:32] Number of tasks = 3 [10:09:32] Starting task 0,CPU time is 0.000000. [10:09:32] ./ZINC09157522.pdbqt size = 28 6 ../../projects/www.worldcommunitygrid.org/fahv.x3NF8_A_IN_Y3b_rig.pdbqt size = 2790 0 ERROR: VINA was killed by signal 9. Retrying task. [10:16:20] Starting task 0,CPU time is 0.000000. [10:16:20] ./ZINC09157522.pdbqt size = 28 6 ../../projects/www.worldcommunitygrid.org/fahv.x3NF8_A_IN_Y3b_rig.pdbqt size = 2790 0 ERROR: VINA was killed by signal 9. 10:16:42 (7058): called boinc_finish </stderr_txt> ]]>  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Power cycle. Doing this about every 3rd or 4th day.
Not doing WCG constantly, let a few come, process them, switch back to simap. Currently on a series of zero redundant, yes really being allowed to do it alone, but lots of repairs with _6 to _10 even had a few too late, meaning 9 returns went error with 195 in 95 of 100 cases and circulation stopped. Then pending validation is converted to too late. An utter waste of time. Lately started to recognize the bad tasks when elapsed and cpu are far apart and the percent progress not jiving. I just abort these when having a higher suffix value  . Looking in the result distribution detail, 9 out of 10 confirm, meaning no hope in heck. Personally, think technicians should program the distributor/feeder to take these out early and reassign them to a linux host. Like we see 7.20s being taken out and send with 7.16 to android, the other way around would expedite the pileup reduction of these for the android platform.Looked at some history and a chart named WCGAndroid.png, and there was about 300k credit/day for android in september for 12000 devices. Now there is 400k credit daily for near 32000 devices, meaning nothing has effectively improved on the whole, just my nexus 7-2013 seeming to do much much better than under the old app. Simap remains 100 percent picture perfect on results, so that's what they run during daytime, and wcg getting the manually controlled nighttime. The lesser disturbance the greater the chance it seems, but that may be subjective. No data to support this. The contribution is so puny on the whole, could as well switch the android feed off till a fix is found for the 195s. As one user noticed, certain batches seem too tough for android. If only these could be recognized by the distribution system and kept away for the mobiles, but that is probably only when pigs learn to fly as well, there's an elephant called dombo tough, seeing him in the mirror each time, when looking  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Worse, the android pipe generated 350k credit for the 22nd per boincstats. Rather sad to see the project that launched boinc for android together with einstein cannot deliver a stable application. Yes there's a learning curve, but is this true to the volunteers to advertise and then have a humongous failure rate?
|
||
|
|
noderaser
Senior Cruncher United States Joined: Jun 6, 2006 Post Count: 297 Status: Offline Project Badges: 
|
WCG had nothing to do with the launch of BOINC for Android, and there were 6 projects available at launch. The development of Android apps can be attributed more to the community-driven efforts of nativeBOINC and AndroBOINC than any project or Berkeley.
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Missed is completely, but a beta was announced at 01:43am. Just had 2.
nodenaser, reading the news blurbs, they, including wcg, started 2 years before last year's announcement on this, so nearly 3 years ago. Who had their car first in the showroom is not really of interest, but ibm being ultra security concious, it's very unlikely they'd ever would have gone with anything but the named 'boinc for android' from berkeley. Whether this was clean room development or in anyway used prior available boinc version open source code, do not know, don't care. The point of my message, there was a very long lead time and 8 months into production, deeply disappointing figures showing. Let's hope this beta does kick the 195 problem in the nuts to make it bow out for good. |
||
|
|
|