| 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: What does this error indicate? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 10
|
|
| Author |
|
|
pirogue
Veteran Cruncher USA Joined: Dec 8, 2008 Post Count: 685 Status: Offline Project Badges: 
|
Result Log
----------------------------------------Result Name: E200069_ 129_ A.18.C14H8OSe2Si.7.set1d06_ 1-- <core_client_version>6.10.56</core_client_version> <![CDATA[ <stderr_txt> INFO: No state to restore. Start from the beginning. [12:35:14] Number of jobs = 16 [12:35:14] Starting job 0,CPU time has been restored to 0.000000. [12:35:14] Starting new Job [12:35:14] Qink name = fldman [12:35:14] Qink name = gesman [12:35:14] Qink name = scfman [12:38:09] Qink name = anlman [12:38:09] End of Job [12:38:22] Finished Job #0 [12:38:22] Starting job 1,CPU time has been restored to 49.722441. [12:38:23] Starting new Job [12:38:23] Qink name = fldman [12:38:36] Qink name = gesman [12:38:36] Qink name = scfman Quit requested: Exiting [12:39:31] Number of jobs = 16 [12:39:31] Starting job 1,CPU time has been restored to 49.722441. [12:39:34] Starting new Job [12:39:35] Qink name = fldman [12:39:35] Qink name = gesman [12:39:36] Qink name = scfman Application exited with RC = 0x4 [12:40:58] Finished Job #1 [12:40:58] Starting job 2,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #2 [12:40:58] Starting job 3,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #3 [12:40:58] Starting job 4,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #4 [12:40:58] Starting job 5,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #5 [12:40:58] Starting job 6,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #6 [12:40:58] Starting job 7,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #7 [12:40:58] Starting job 8,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #8 [12:40:58] Starting job 9,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #9 [12:40:58] Starting job 10,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #10 [12:40:58] Starting job 11,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #11 [12:40:58] Starting job 12,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #12 [12:40:58] Starting job 13,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #13 [12:40:58] Starting job 14,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #14 [12:40:58] Starting job 15,CPU time has been restored to 110.113260. [12:40:58] Skipping Job #15 called boinc_finish Exiting 0 </stderr_txt> ]]> |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
How long did the task run and what processor?
----------------------------------------Edit: Seems this is the first log posted that has "Quit requested: Exiting" in it, so am curious too... maybe a self-diagnosis, a build in QA, that continuing is fruitless.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 1 times, last edit by Sekerob at Jul 6, 2010 10:52:17 AM] |
||
|
|
pirogue
Veteran Cruncher USA Joined: Dec 8, 2008 Post Count: 685 Status: Offline Project Badges:
|
It ran for .03 hrs inside a Centos 5.5 (32-bit) VM.
---------------------------------------- |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
One of the bombings I've seen reported was probably related to short allocation of virtual memory space.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
pirogue
Veteran Cruncher USA Joined: Dec 8, 2008 Post Count: 685 Status: Offline Project Badges:
|
I don't think it's running out of swap space.
----------------------------------------Swap: 4128760k total, 72k used. |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Centos has shown problems in past... very few at WCG I think, probably hidden in these stats per OS page: http://boincstats.com/stats/host_os_stats.php?pr=wcg&st=0. Mind you, the HCC PI reported for that platform success on a Centos 64 platform, so it's not like it would not run other WCG sciences. Was this setup successful at other WCG sciences?
----------------------------------------Got some BOINC message log for us from before till after the result was starting to report the outcome? Sorry for asking questions you've probably already answered before. Omniscience has not come to me yet ;-)
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
pirogue
Veteran Cruncher USA Joined: Dec 8, 2008 Post Count: 685 Status: Offline Project Badges:
|
It's newly set up. I haven't run any other sciences on it.
----------------------------------------The only error messages in the log are from server problems. I've only had 2 of these errors, so I'm not too concerned. I was mainly hoping that "RC = 0x4" actually meant something. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I've only had 2 of these errors, so I'm not too concerned. I was mainly hoping that "RC = 0x4" actually meant something. Given that this error has been reported since June 21 in the beta, it would certainly be good if someone could tell us what it means. (... and, preferably, fix it.) |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Well we know that a new version will come for all platforms to fix a graphics issue, but kind of expect this not to happen until after the Windows/Mac beta has taken off.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
While it may be a while before there's a fix, it's surprising that there has been a sustained silence from the techs as to what the problem is.
The RC=0x4 errors must mean something and those who programmed the project should know what that is, so what's wrong with at least answering the question? I know that won't make the problem go away, but some of us would still be interested to know. |
||
|
|
|