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: 4
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 434 times and has 3 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Protection fault, still valid

[04:11:46] Finished Job #11
[04:11:46] Starting job 12,CPU time has been restored to 10280.421875.
Application exited with RC = 0xc0000005
[04:53:39] Finished Job #12
[04:53:39] Starting job 13,CPU time has been restored to 12609.687500.


E203940_ 631_C.30.C25H14N4S.00393408.2.set1d06_ 0--

Not a problem for me, if it isn't one for you ;-)


The result starts with several heartbeat errors, caused by the workunit itself - the CEP startup phase often keeps the core client too busy to update the heartbeat timestamp. I'm not sure what affect this can have on the result quality. (Not recommended to run with projects that don't have checkpoints)
----------------------------------------
[Edit 1 times, last edit by Former Member at Nov 17, 2011 9:08:01 AM]
[Nov 17, 2011 9:04:28 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Protection fault, still valid

Hmmm, this is from a different workunit (E203931_ 567_ C.29.C25H16N2SSi.00350982.4.set1d06_ 0--) :

[16:49:49] Finished Job #11
[16:49:49] Starting job 12,CPU time has been restored to 9114.859375.
Application exited with RC = 0x1
[18:44:32] Finished Job #12
[18:44:32] Starting job 13,CPU time has been restored to 15793.484375.


Again Job12 crashed and the overall result is valid, I guess that's normal then
[Nov 17, 2011 9:21:52 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Protection fault, still valid

There's a set of RC conditions that are known and accepted, i.e. old hat. The result is taken as correct up to the point where it exits.

If the task were considered dubious, a second or third copy would be issued to verify.

Happy crunching CEP2, in zero redundancy (most of the times).

--//--
[Nov 17, 2011 9:37:14 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Protection fault, still valid

thanks :-)
[Nov 17, 2011 1:42:53 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread