Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 16
Posts: 16   Pages: 2   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 135742 times and has 15 replies Next Thread
petehardy
Senior Cruncher
USA
Joined: May 4, 2007
Post Count: 318
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: CEP2 jobs failing quickly: "process exited with code 195 (0xc3, -61)"

Mine used no cpu time.


----------------------------------------

"Patience is a virtue", I can't wait to learn it!
[Jul 13, 2010 8:27:29 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 jobs failing quickly: "process exited with code 195 (0xc3, -61)"

I believe it could be the WU, but I also think it's undetermined clients for the discussed sample worked out as this:

E200132_ 322_ A.19.C16H11NSSi.228.0.set1d06_ 2-- 619 Valid 7/13/10 07:45:31 7/13/10 23:42:03 4.85 96.7 / 104.0 < Mine
E200132_ 322_ A.19.C16H11NSSi.228.0.set1d06_ 0-- 619 Valid 7/13/10 04:04:32 7/14/10 01:35:07 5.99 111.3 / 104.0
E200132_ 322_ A.19.C16H11NSSi.228.0.set1d06_ 1-- 619 Error 7/13/10 04:01:14 7/13/10 06:56:13 0.01 0.3 / 0.0 < 195 error

It's log:

Result Name: E200132_ 322_ A.19.C16H11NSSi.228.0.set1d06_ 1--
<core_client_version>6.10.17</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
[01:54:16] Number of jobs = 16
[01:54:16] Starting job 0,CPU time has been restored to 0.000000.
[01:54:16] Starting new Job
[01:54:18] Qink name = fldman
[01:54:18] Qink name = gesman
[01:54:18] Qink name = scfman
Application exited with RC = 0xb
[01:54:59] Finished Job #0
called boinc_finish
Exiting 195

</stderr_txt>
]]>


This one ran actually quite extraordinary for checkpoints on messages scanning. Short, short, long, 12 short (3 minutes each) and then long again 64 minutes. The last usually the longest, if not always.

edit: undetermined, not undermined :P
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
----------------------------------------
[Edit 1 times, last edit by Sekerob at Jul 14, 2010 7:03:49 AM]
[Jul 14, 2010 7:02:49 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Sekerob
Ace Cruncher
Joined: Jul 24, 2005
Post Count: 20043
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 jobs failing quickly: "process exited with code 195 (0xc3, -61)"

This one took much longer to fail, same 195 error as in the OP, but the RC =0x9 is different ( a first I think posted on the forums) and seems possibly to be related with file permissions... maybe another volunteer who handled the rights as in another thread yesterday?

<core_client_version>6.10.17</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
INFO: No state to restore. Start from the beginning.
INFO: No state to restore. Start from the beginning.
[21:06:34] Number of jobs = 16
[21:06:34] Starting job 0,CPU time has been restored to 0.000000.

...

[07:30:59] Starting job 0,CPU time has been restored to 0.000000.
Application exited with RC = 0x9
[ERROR] Failed to open either source or destination files while copying A.19.C17H10SSe.102.1.noopt.bp86.sto6g.n.sp/53.0 to A.19.C17H10SSe.102.1.noopt.bp86.sto6g.n.sp.53.0. Error: 2
[ERROR] Failed to open either source or destination files while copying A.19.C17H10SSe.102.1.noopt.bp86.sto6g.n.sp/stdout.txt to A.19.C17H10SSe.102.1.noopt.bp86.sto6g.n.sp.out. Error: 2
[07:31:07] Finished Job #0
called boinc_finish
Exiting 195

</stderr_txt>
]]>


PS: Not found with forum advanced search.
----------------------------------------
WCG Global & Research > Make Proposal Help: Start Here!
Please help to make the Forums an enjoyable experience for All!
----------------------------------------
[Edit 1 times, last edit by Sekerob at Jul 19, 2010 4:09:40 PM]
[Jul 19, 2010 4:08:27 PM]   Link   Report threatening or abusive post: please login first  Go to top 
codes
Advanced Cruncher
Joined: Oct 20, 2009
Post Count: 142
Status: Offline
Reply to this Post  Reply with Quote 
confused Re: CEP2 jobs failing quickly: "process exited with code 195 (0xc3, -61)"

Just got 3 real repair jobs of which the multiple wingman indicate to fail on this 195 error at 0.0 time i.e. immediately. They don't cost time, but do loose a little bit of R++ rating :D

Just in case other cruncher see this, here's how such a result log looks... and of course, it went in 11 second when put ahead of the queue:

"real repair jobs"?
"wingman"?
"R++ rating"?

Other than understanding some work units failed processing, the rest of these words must be code for some WCG testing team?
[Jul 19, 2010 5:12:23 PM]   Link   Report threatening or abusive post: please login first  Go to top 
RaymondFO
Veteran Cruncher
USA
Joined: Nov 30, 2004
Post Count: 561
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: CEP2 jobs failing quickly: "process exited with code 195 (0xc3, -61)"

[ot] I will attempt to define these terms for you:

Wingman - Where the specific work unit ("WU") is sent out to usually two (2) (HPF2 is the exception. Please refer to that thread for more information) computers/users (aka "crunchers") for validation purposes, the other party to you is called "Wingman" as that computer/cruncher is your assigned partner to complete the WU.

Repair Jobs- From time to time, WU's are not completed due to various factors such as: WU not being returned on time ("no reply"), WU returned was deemed "inconclusive" and needs to be re-checked by another independent computer, WU aborted by the WCG server or by the user for various reasons, WU received is invalid as it may not have met a certain validity or other test and the results needs to be redone, or the WU was detached by the user. When these situations occur, another duplicate "repair job" is sent out to complete or verify the WU results for the scientists. Repair jobs currently have four (4) day turnarounds whereas normally distributed WU's currently have a ten (10) window for completion.

R++ - WCG had internal reliability ratings on computers that process WCG WU assignments. These rating are never published and are for WCG internal purposes only. The higher the computer reliability rating, your computer maybe eligible to receive "repair jobs." Reliability rating is how well your computer performs, accurately returns work units without errors or exceptions. Please note that to receive a repair WU, your computer must average turnarounds in less than two (2) days, I believe.

Hope this helps. [/ot]
----------------------------------------
[Edit 1 times, last edit by RaymondFO at Jul 19, 2010 8:48:17 PM]
[Jul 19, 2010 5:44:51 PM]   Link   Report threatening or abusive post: please login first  Go to top 
codes
Advanced Cruncher
Joined: Oct 20, 2009
Post Count: 142
Status: Offline
Reply to this Post  Reply with Quote 
Re: CEP2 jobs failing quickly: "process exited with code 195 (0xc3, -61)"

Thanks for the explaination.
[Jul 20, 2010 1:08:26 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 16   Pages: 2   [ Previous Page | 1 2 ]
[ Jump to Last Post ]
Post new Thread