| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Help Fight Childhood Cancer Project Forum
Thread: Repeated Errors with workunits run on a Linux desktop |
| 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 |
Hello,
sorry, but I have got bad news. On my desktop I use the operating system Ubuntu 11.04 - the Natty Narwhal - released in April 2011 and supported until October 2012. Unfortunately, repeatedly calculation errors have occurred with the help fight childhood cancer project workunits . The system is not overclocked or manipulated in any way, so I have no explanation for the errors. The logs are as follows: Result Name: HFCC_ target-9_ 00050689_ target-9_ 0000_ 0-- <core_client_version>6.10.59</core_client_version> <![CDATA[ <message> process got signal 11 </message> <stderr_txt> INFO:[18:14:41] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[18:16:38] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 27000 _maxGenSeenSoFar changed: 6750 About to enter main loop...(dockings already completed: 0) Updating Best Energy for WU: 0.00 Finished Docking number 0 Finished Docking number 1 Finished Docking number 2 Finished Docking number 3 Finished Docking number 4 Finished Docking number 5 Finished Docking number 6 Updating Best Energy for WU: -8.40 Finished Docking number 7 Finished Docking number 8 Updating Best Energy for WU: -8.77 Finished Docking number 9 Finished Docking number 10 Finished Docking number 11 Finished Docking number 12 Finished Docking number 13 Finished Docking number 14 </stderr_txt> ]]> World Community Grid Result Log Result Name: HFCC_ target-9_ 00050689_ target-9_ 0001_ 0-- <core_client_version>6.10.59</core_client_version> <![CDATA[ <message> process got signal 11 </message> <stderr_txt> INFO:[19:56:22] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[19:59:11] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 27000 _maxGenSeenSoFar changed: 6750 About to enter main loop...(dockings already completed: 0) Updating Best Energy for WU: 0.00 Finished Docking number 0 Finished Docking number 1 Updating Best Energy for WU: -7.77 Finished Docking number 2 Updating Best Energy for WU: -7.93 Finished Docking number 3 Updating Best Energy for WU: -8.31 Finished Docking number 4 Finished Docking number 5 Finished Docking number 6 Finished Docking number 7 Updating Best Energy for WU: -8.47 Finished Docking number 8 Finished Docking number 9 Finished Docking number 10 Finished Docking number 11 Finished Docking number 12 Finished Docking number 13 Finished Docking number 14 Finished Docking number 15 Finished Docking number 16 Finished Docking number 17 Finished Docking number 18 Finished Docking number 19 Updating Best Energy for WU: -9.58 Finished Docking number 20 Finished Docking number 21 Finished Docking number 22 Finished Docking number 23 Restoring grahics. bestEnergy: -10.140800 maxGenSeen: 6750 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 27000 About to enter main loop...(dockings already completed: 24) Finished Docking number 24 Finished Docking number 25 Finished Docking number 26 Finished Docking number 27 Finished Docking number 28 Finished Docking number 29 Finished Docking number 30 Finished Docking number 31 Finished Docking number 32 Finished Docking number 33 Finished Docking number 34 Finished Docking number 35 Finished Docking number 36 Finished Docking number 37 Finished Docking number 38 Finished Docking number 39 Finished Docking number 40 Finished Docking number 41 Finished Docking number 42 Finished Docking number 43 Finished Docking number 44 Finished Docking number 45 Finished Docking number 46 Finished Docking number 47 Finished Docking number 48 Finished Docking number 49 Finished Docking number 50 Finished Docking number 51 Restoring grahics. bestEnergy: -10.140800 maxGenSeen: 6750 AG Check: Found receptor.A.map Beginning AutoDock... INFO: Setting num_generations: 27000 About to enter main loop...(dockings already completed: 52) Finished Docking number 52 Finished Docking number 53 Finished Docking number 54 Finished Docking number 55 Finished Docking number 56 Finished Docking number 57 Finished Docking number 58 Finished Docking number 59 Finished Docking number 60 Finished Docking number 61 Finished Docking number 62 Finished Docking number 63 Finished Docking number 64 Finished Docking number 65 Finished Docking number 66 Finished Docking number 67 Finished Docking number 68 Finished Docking number 69 Finished Docking number 70 Finished Docking number 71 Finished Docking number 72 Finished Docking number 73 Finished Docking number 74 Finished Docking number 75 Finished Docking number 76 Finished Docking number 77 Finished Docking number 78 Finished Docking number 79 Finished Docking number 80 Finished Docking number 81 Finished Docking number 82 Finished Docking number 83 Finished Docking number 84 Finished Docking number 85 Finished Docking number 86 Finished Docking number 87 Finished Docking number 88 Finished Docking number 89 Finished Docking number 90 Finished Docking number 91 Finished Docking number 92 Finished Docking number 93 Finished Docking number 94 Finished Docking number 95 Finished Docking number 96 Finished Docking number 97 Finished Docking number 98 Finished Docking number 99 Finished Docking number 100 Finished Docking number 101 Finished Docking number 102 Finished Docking number 103 Finished Docking number 104 Finished Docking number 105 Finished Docking number 106 Finished Docking number 107 Finished Docking number 108 Finished Docking number 109 Finished Docking number 110 Finished Docking number 111 Finished Docking number 112 Finished Docking number 113 Finished Docking number 114 Finished Docking number 115 Finished Docking number 116 Finished Docking number 117 Finished Docking number 118 Finished Docking number 119 Finished Docking number 120 Finished Docking number 121 Finished Docking number 122 Finished Docking number 123 Finished Docking number 124 Finished Docking number 125 Finished Docking number 126 Finished Docking number 127 Finished Docking number 128 Updating Best Energy for WU: -10.14 Finished Docking number 129 Finished Docking number 130 Finished Docking number 131 Finished Docking number 132 Finished Docking number 133 Finished Docking number 134 Finished Docking number 135 Finished Docking number 136 Finished Docking number 137 Finished Docking number 138 Finished Docking number 139 Finished Docking number 140 Finished Docking number 141 Finished Docking number 142 Finished Docking number 143 Finished Docking number 144 Finished Docking number 145 Finished Docking number 146 Finished Docking number 147 Finished Docking number 148 Finished Docking number 149 Finished Docking number 150 Finished Docking number 151 Finished Docking number 152 Finished Docking number 153 </stderr_txt> ]]> close Return to Top World Community Grid Result Log Result Name: HFCC_ target-9_ 00059241_ target-9_ 0000_ 0-- <core_client_version>6.10.59</core_client_version> <![CDATA[ <message> process got signal 11 </message> <stderr_txt> INFO:[16:43:00] Start AutoGrid... autogrid: autogrid4: Successful Completion. INFO:[16:44:22] End AutoGrid... Beginning AutoDock... INFO: Setting num_generations: 27000 _maxGenSeenSoFar changed: 6750 About to enter main loop...(dockings already completed: 0) Updating Best Energy for WU: 0.00 Finished Docking number 0 Updating Best Energy for WU: -5.03 Finished Docking number 1 Finished Docking number 2 Finished Docking number 3 Finished Docking number 4 Finished Docking number 5 Finished Docking number 6 Finished Docking number 7 Finished Docking number 8 Finished Docking number 9 Finished Docking number 10 Finished Docking number 11 Finished Docking number 12 Finished Docking number 13 Finished Docking number 14 Finished Docking number 15 Updating Best Energy for WU: -5.14 Finished Docking number 16 Finished Docking number 17 Finished Docking number 18 Finished Docking number 19 Finished Docking number 20 Finished Docking number 21 Finished Docking number 22 Finished Docking number 23 Finished Docking number 24 Finished Docking number 25 Finished Docking number 26 Finished Docking number 27 Updating Best Energy for WU: -5.17 Finished Docking number 28 Finished Docking number 29 Finished Docking number 30 Finished Docking number 31 Finished Docking number 32 Finished Docking number 33 Updating Best Energy for WU: -5.17 Finished Docking number 34 Finished Docking number 35 Finished Docking number 36 Finished Docking number 37 Finished Docking number 38 Finished Docking number 39 Finished Docking number 40 </stderr_txt> ]]> close Return to Top Result Log Result Name: HFCC_ target-9_ 00059486_ target-9_ 0001_ 0-- <core_client_version>6.10.59</core_client_version> <![CDATA[ <message> process got signal 11 </message> <stderr_txt> INFO:[16:42:47] Start AutoGrid... </stderr_txt> ]]> I would like to ask someone to check and resolve the problem. One of the bad workunits run for a short time, the others quite long, and all ended with calculation errors.... Thanks in advance for any help Greetings Kafejka |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Signal 11 is a sign of a ''too busy'' system [typical of Linux]. This is why I've set BOINC to pause on this Ubuntu host whenever the non-BOINC load is greater than 40%, the "while processor usage is less then 40%" is preventing this error for me. Also unstable networking could cause this on Linux. Someone posted he'd managed to configure a fix by installing dnsmasq [or dnsmasq basic as dnsmasq conflicts with Network Manager]. Did not say what the settings were that needed entering, but it's likely related to the localhost IP.
--//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello,
thanks a lot for your answer. I will try setting BOINC to switch off if CPU usage is above 90% hoping that this will fix the problem. Setting it to 40% would stop BOINC too often. BOINC progress is important for me. I will go on crunching forever Greetings and thank you again Kafejka |
||
|
|
-Tails-
Cruncher Joined: Sep 25, 2010 Post Count: 23 Status: Offline Project Badges: 
|
Actually I dont think this problem is platform related, I had the same issue with my windows client, 10 wu errored out in a row. I never had this problem before, and I hope I'll never meet this problem in the future, with other projects.
---------------------------------------- [Edit 1 times, last edit by -Tails- at May 2, 2012 2:50:18 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Plz point me to words where it's said to be Linux exclusive? Too busy can happen on Windows too, cept I get this mostly on Linux, so much so that the described setting stopped the tasks from failing altogether. It costs maybe 5-15 minutes a day [LAIM on of course] and only when I'm using the system, never when it's crunching and left alone, which is most of the time. 5-15 minutes is a whole lot less then a series of jobs bumming out when they've done 6-8-10-12 hours.
Kafejka, WCG actually uses a default of 50% for clean profiles opposed to the 25% that is default in the Berkeley client. 40% non-BOINC use is actually a lot, but that was for me the trial and error point, where CEP2's started crashing when I was doing e.g. system updates that take longer than 30 seconds of intense disk IO [the most common cause] --//-- |
||
|
|
Dark Angel
Veteran Cruncher Australia Joined: Nov 11, 2005 Post Count: 721 Status: Offline Project Badges: 
|
Signal 11 is a sign of a ''too busy'' system [typical of Linux]. Sek, I think that would be the phrase that -Tails- is referring to. That could potentially suggest the problem is Linux dependent. It's probably a problem in translation, that's all. It's nothing worth stewing over.  Currently being moderated under false pretences [Edit 1 times, last edit by Dark Angel at May 5, 2012 11:15:43 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello SekeRob,
thank you very much for your help. There would be something to be said about the problem with signal -i, but right at the moment I am to tired to do so. I will go on crunching, on and on and on. All the best Kafejka |
||
|
|
|