| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: The Clean Energy Project - Phase 2 Forum
Thread: Application exited with RC = 0x1 (Job 6 out of 7) |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 13
|
|
| Author |
|
|
enels
Senior Cruncher Joined: Apr 25, 2008 Post Count: 286 Status: Offline Project Badges: 
|
RC means Return Code
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Not the first to give us the right answer of what it meant :O)
|
||
|
|
tombell12
Advanced Cruncher Australia Joined: Oct 8, 2009 Post Count: 87 Status: Offline Project Badges: 
|
Hi guys,
I've noticed this same error code just happen with one of my workunits. Clicking on the workunit name shows me alongside with 2 others also with an "Error" status. It ran for about 7 hours & then suddenly "completed"  . Here is the actual log:Result Name: E234369_ 310_ S.288.C32H20N4O4S1.QQUZOATYFPURDD-UHFFFAOYSA-N.19_ s1_ 14_ 2-- <core_client_version>7.2.31</core_client_version> <![CDATA[ <stderr_txt> INFO: No state to restore. Start from the beginning. [10:42:49] Number of jobs = 8 [10:42:49] Starting job 0,CPU time has been restored to 0.000000. [14:51:16] Finished Job #0 [14:51:16] Starting job 1,CPU time has been restored to 14646.637488. [15:06:24] Finished Job #1 [15:06:24] Starting job 2,CPU time has been restored to 15542.348430. [15:19:20] Finished Job #2 [15:19:20] Starting job 3,CPU time has been restored to 16303.680110. [15:32:26] Finished Job #3 [15:32:26] Starting job 4,CPU time has been restored to 17079.675884. [15:43:40] Finished Job #4 [15:43:40] Starting job 5,CPU time has been restored to 17744.520946. [15:53:22] Finished Job #5 [15:53:22] Starting job 6,CPU time has been restored to 18317.091416. Application exited with RC = 0x1 [17:52:55] Finished Job #6 [17:52:55] Starting job 7,CPU time has been restored to 25413.296105. [17:52:55] Skipping Job #7 17:53:00 (5000): called boinc_finish </stderr_txt> ]]> Interesting point SekeRob: Tasks for CEP2 cut out at about 5 error copies after which they are automatically put on a 'investigate' list. I'd almost expect this workunit to go on the list  |
||
|
|
|