| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: FightAIDS@Home - VINA Beta test July 9, 2013 - Issues Thread |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 82
|
|
| Author |
|
|
p3nguin53
Advanced Cruncher USA Joined: Dec 8, 2008 Post Count: 95 Status: Offline Project Badges: 
|
I have another beta WU stuck in a restarting loop on my Vista machine:
Restarting task BETA_FAHV_x4I7G_RT_NNRTIadj_wNNRTI_0045259_0944_2 using beta18 version 703 All 3 Beta's that tried to run on this machine got stuck in restarting loops. Reboot and suspend/resume didn't help. Decided to abort this one. |
||
|
|
9maMSSuNWXgttyKdZhMemeXmEx8
Senior Cruncher Puerto Rico Joined: Feb 20, 2008 Post Count: 191 Status: Offline Project Badges: 
|
Received 3 tasks, which turned to be Valid.
----------------------------------------  |
||
|
|
ov7
Cruncher Joined: May 14, 2009 Post Count: 15 Status: Offline Project Badges: 
|
Hello,
Four your information : 18/07/2013 14:08:44 World Community Grid Restarting task BETA_FAHV_x4I7G_RT_NNRTIadj_wNNRTI_0045261_1354_3 using beta18 version 703 This WU is restarting endlessly. Olivier |
||
|
|
Gil II
Senior Cruncher Canada Joined: Dec 6, 2006 Post Count: 368 Status: Offline Project Badges:
|
I have 4 Betas that have been in execution since yesterday and not getting anywhere I am also getting these messages:
----------------------------------------19/07/2013 2:37:34 PM World Community Grid Restarting task BETA_FAHV_x4I7G_RT_NNRTIadj_wNNRTI_0045260_1267_2 using beta18 version 703 19/07/2013 2:37:34 PM World Community Grid Restarting task BETA_FAHV_x4I7G_RT_NNRTIadj_wNNRTI_0045260_1183_2 using beta18 version 703 19/07/2013 2:37:34 PM World Community Grid Restarting task BETA_FAHV_x4I7G_RT_NNRTIadj_wNNRTI_0045260_0281_2 using beta18 version 703 19/07/2013 2:37:34 PM World Community Grid Restarting task BETA_FAHV_x4I7G_RT_NNRTIadj_wNNRTI_0045260_0224_2 using beta18 version 703  |
||
|
|
TITI2410FR
Cruncher Joined: May 16, 2010 Post Count: 4 Status: Offline Project Badges:
|
always problem with android, all beta test error.
Journal des résultats Nom du résultat: BETA_ SN2S_ AAB68717_ 0000027_ 4188_ 4-- <core_client_version>7.2.7</core_client_version> <![CDATA[ <message> process exited with code 195 (0xc3, -61) </message> <stderr_txt> INFO: No state to restore. Start from the beginning. [07:50:50] Number of tasks = 8 [07:50:50] Starting task 0,CPU time is 0.000000. [07:50:50] ./ZINC01121954.pdbqt size = 29 6 ../../projects/www.worldcommunitygrid.org/beta14.target_AAB68717.pdbqt size = 357 0 ERROR: VINA was killed by signal 11. Retrying task. [08:23:57] Starting task 0,CPU time is 0.000000. [08:23:57] ./ZINC01121954.pdbqt size = 29 6 ../../projects/www.worldcommunitygrid.org/beta14.target_AAB68717.pdbqt size = 357 0 ERROR: VINA was killed by signal 11. 08:24:10 (2554): called boinc_finish SIGSEGV: segmentation violation Exiting... |
||
|
|
JSYKES
Senior Cruncher Joined: Apr 28, 2007 Post Count: 200 Status: Offline Project Badges:
|
There certainly appears to be a problem with some of the FAHV WU's - a reasonably high percentage work perfectly but of the couple of dozen that I have had, I have needed to abort two so far.....a question for the tech guys, is there an auto abort option possible that could trigger after a set number of retries (maybe 10?) to save wasting days of processing before the WU expires on the calendar date??? Just a thought.....
---------------------------------------- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hard coded in BOINC, that is if this invokes a zero status like revert to a previous checkpoint or to the beginning of task, it's 100 times before a WU goes south. Of course, the science app is maybe able to capture the error and do this sooner. If this happens only near the checkpoint with large interval, often where the task moves on to a next segment and the intermediate computation result is small to save, then 100 is of course a long time before the trigger is pulled. To me it's relative to the job size. If set to run 45 minutes on the Androids, then it's silly to not help it out of it's misery sooner than e.g. 450 minutes... [efficiency I'd consider... resend it sooner [with priority] to someone else and have it take a try quicker identifies a reproducible dud, and maybe more rumble on the forums :O]. WCG operates a factor for a task to time out. On what to measure time outs... Elapsed or CPU time... it's how BOINC records time, which is not actual wallclock, but the time it's allowed to run, meaning if BOINC is set to 25% Throttle, it's 4 hours before 1 hour Elapsed is recorded.
2 lira of lose [bit]coins (you may choose the least valued of this currency). |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
P.S. Anyone seeing small sized undulations on AutoDock... this is normal as the docking is seeking the lowest energy taking docking point. If it cant match or equal the lowest energy achieved at the previous checkpoint, it's try more times or skip forward.
|
||
|
|
KerSamson
Master Cruncher Switzerland Joined: Jan 29, 2007 Post Count: 1670 Status: Offline Project Badges: 
|
As usual with VINA based WUs, I observed several invalid results on a host based on Athlon II x4, running an updated Ubuntu 10.04 x64.
----------------------------------------It is really boring and frustrating since there is only very few projects available not running VINA. Yves |
||
|
|
nasher
Veteran Cruncher USA Joined: Dec 2, 2005 Post Count: 1422 Status: Offline Project Badges: 
|
did we run out of android WU's?
---------------------------------------- |
||
|
|
|