| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Human Proteome Folding - Phase 2
Thread: Some Errors |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 33
|
|
| Author |
|
|
burakreis
Cruncher Joined: Jun 8, 2005 Post Count: 16 Status: Offline Project Badges: 
|
I get a lot of errors ın
----------------------------------------Please help me I don't know reason(s) <core_client_version>6.2.18</core_client_version> <![CDATA[ <message> Incorrect function. (0x1) - exit code 1 (0x1) </message> <stderr_txt> ERROR:: Exit at: .\dock_structure.cc line:401 </stderr_txt> ]]> <core_client_version>6.2.18</core_client_version> <![CDATA[ <message> Incorrect function. (0x1) - exit code 1 (0x1) </message> <stderr_txt> ERROR:: Exit at: .\dock_structure.cc line:401 </stderr_txt> ]]> A lot of Same problems **Edited to reflect the research project that has experienced the error / TKH** [Edit 1 times, last edit by TKH at Sep 22, 2008 12:42:31 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I have had a few errors with HCC but they have very short run time.
ly190_ 00001_ 17-- Result Log <core_client_version>5.10.45</core_client_version> <![CDATA[ <message> Incorrect function. (0x1) - exit code 1 (0x1) </message> <stderr_txt> ERROR:: Exit at: .\dock_structure.cc line:401 </stderr_txt> ]]> |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
This problem is showing up in several threads. I do not know what is causing it, so I am leaving it for the staff to investigate.
Lawrence |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: 
|
These errors are associated with the HPF2 project and not HCC1. We are looking into these errors and have a new version of application in alpha that we believe will fix these errors.
-Uplinger |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
These errors are associated with the HPF2 project and not HCC1. We are looking into these errors and have a new version of application in alpha that we believe will fix these errors. My apologies, of course this was for a HPF2 WU. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
These errors are associated with the HPF2 project and not HCC1. We are looking into these errors and have a new version of application in alpha that we believe will fix these errors. -Uplinger Will we be informed when this problem is fixed? At the moment I was getting so many errors that I am excluding HPF2 from the workload. Robert |
||
|
|
JmBoullier
Former Community Advisor Normandy - France Joined: Jan 26, 2007 Post Count: 3716 Status: Offline Project Badges: 
|
As usual, yes.
----------------------------------------Cheers. Jean. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Will we be informed when this problem is fixed? There is a part of me that wants to post a truly sarcastic reply. Just look through all the forums and see how well the CAs and Techs keel these projects all rolling along. Thanks folks.  |
||
|
|
E165852
Cruncher Joined: Jul 17, 2008 Post Count: 4 Status: Offline |
The WU lz154_00020 is in error.
<core_client_version>6.2.18</core_client_version> <![CDATA[ <message> t@NVªÔáÁĢܷB (0x1) - exit code 1 (0x1) </message> <stderr_txt> ERROR:: Exit at: .\RotamerSet.cc line:1203 </stderr_txt> ]]> It consumes a lot of CPU and finally fall into error. It seems a guy still running. Did you stop distributing this WU? |
|||
|
||||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Will we be informed when this problem is fixed? There is a part of me that wants to post a truly sarcastic reply. Just look through all the forums and see how well the CAs and Techs keel these projects all rolling along. Thanks folks. Fret not O tech one! It is all too common on other BOINC message boards that projects don't keep crunchers well informed. No doubt the poster has seen this pattern far too often: it's not a WCG problem, it is a BOINC problem. You who work on a particular BOINC project sometimes get caught in the middle of a wider net, even if you're not the ones to blame. |
|||
|
||||
|
|