This Wu failed after trying to restart from last checkpoint.

(I update BOINC so it was taken out of memory)

http://ralph.bakerlab.org/result.php?resultid=569191

Anders n

Result ID 566072
Name 1csl__BOINC_EXCLUDENB_PERMITZERO_RNA_ABINITIO-1csl_-_2156_10_1
Workunit 500961
Created 25 Jun 2007 4:05:10 UTC
Sent 25 Jun 2007 4:47:22 UTC
Received 25 Jun 2007 8:41:02 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status 1 (0x1)
Computer ID 7180
Report deadline 29 Jun 2007 4:47:22 UTC
CPU time 0
stderr out

<core_client_version>5.10.2</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
Graphics are disabled due to configuration...
# cpu_run_time_pref: 7200
ERROR:: Exit from: pose.cc line: 769

</stderr_txt>
]]>

Validate state Invalid
Claimed credit 0
Granted credit 0
application version 5.69

Result ID 563617
Name 1FAB_BOINC_MFR_ABRELAX_2144_24_1
Workunit 499540
Created 23 Jun 2007 6:10:18 UTC
Sent 23 Jun 2007 6:10:25 UTC
Received 23 Jun 2007 17:42:55 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status 0 (0x0)
Computer ID 8763
Report deadline 27 Jun 2007 6:10:25 UTC
CPU time 6887.484375
stderr out

<core_client_version>5.10.2</core_client_version>
<![CDATA[
<stderr_txt>
# cpu_run_time_pref: 7200
# random seed: 2605369
======================================================
DONE :: 1 starting structures 6886.77 cpu seconds
This process generated 4 decoys from 4 attempts
======================================================


BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down...

</stderr_txt>
<message>
<file_xfer_error>
<file_name>1FAB_BOINC_MFR_ABRELAX_2144_24_1_0</file_name>
<error_code>-161</error_code>
</file_xfer_error>

</message>
]]>

Validate state Invalid
Claimed credit 28.4623439083363
Granted credit 0
application version 5.68

I'm 8.5hrs in to this symm fold dock relax task and still have not completed the second model. Seems significantly higher then the 1hr/model mentioned previously.

After a fair run of successes my G5 Mac got a computation error (no crash AFAICT) with exit code 1 (0x1), running v5.68 on gp04__BOINC_SYMM_FOLD_AND_DOCK_RELAX_SUBSYSTEM-gp04_-delC126__2078_10 after a little over six hours of crunching. The system had been running with the screensaver blacked out and the display sleeping for at least twelve hours. The output ends with

ERROR:: Exit from: hbonds.cc line: 636

My Mac G4/733 crashed after more than ten hours of crunching 1gidA_BOINC_MG_SASAPAIR_ALLRES_RNA_ABINITIO_SAVE_ALL_OUT_BARCODE_RNA_CONTACT_RNA_LONG_RANGE_CONTACT_RNA_SASA-1gidA-_2068_172; last time I looked it was showing only about ten minutes to go but hadn’t decremented that time for quite a while. (The percent done was over 98% and continuing to increment.) Exit status 1 (0x1), with the all-too-familiar “SIGBUS: bus error” message in the output file. Once again, the crash occurred either while the display was blacked out (having displayed the screensaver for a minute) or when I interrupted it. BTW this system has always been set to work while in use and to keep apps in memory, so I don’t understand why starting and stopping the graphics should be a problem—if that’s indeed the case.

My sidechains still fall off on 5.67, as they did with 5.65
Example screenshot

Error:
http://ralph.bakerlab.org/result.php?resultid=523659

<core_client_version>5.8.16</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
# cpu_run_time_pref: 7200
# random seed: 2662174


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x009B93DB read attempt to address 0x1133FE5C

Engaging BOINC Windows Runtime Debugger...



********************

Hello, everyone! I seem to have been recruited into my first alpha project (the first that identifies itself as such, at least). I regret that my first posting here has to be negative. Well, mixed …

After getting “No work from project” messages for a few hours after attaching, my G4/400 running BOINC v5.4.9 under Mac OS 10.3.9 received its first WU, 2tif__DIVERSE_ABRELAX__NEWRELAXFLAGS_BCFROMFRAGS20_SAVE_ALL_OUT_frags83__1986_4. It got a “Compute error” in less than twenty seconds:

<message>
process exited with code 1 (0x1)
</message>
<stderr_txt>
Rosetta@home Macintosh Stack Size checker.
  Original size:            0.
  Maximum size:      8388608.
  RLIM_INFINITY            0
# cpu_run_time_pref: 3600
ERROR:: Unable to determine sequence length from pdb file
# random seed: 2680619
ERROR:: Exit from: pose.cc line: 1929
</stderr_txt>

The other two hosts that crunched it, both Windows/AMD, also had errors.

On the brighter side, the next WU I received seems to be doing OK. It began with an estimate of around 25 hours and kicked my host into “panic mode”, but got most of the way through the task in just a couple of hours. Then it seemed to slow down; when I left the shop it was somewhat over 90% done, having found a configuration that vaguely resembled the ‘template’, but still showing about 13 hours to go. When I got home, however, I was encouraged to see that the host had downloaded another WU, indicating that BOINC thinks the current one is almost done.

Awesome graphics, BTW. :)

P.S. Re checkpoints: I forgot to mention that my Mac crashed while running this task (@#$%! Acrobat!) but when I rebooted it resumed very near where it had been when interrupted.

Same for me

http://ralph.bakerlab.org/result.php?resultid=505151
http://ralph.bakerlab.org/result.php?resultid=505150

=Lupus=

Maion, I believe your time remaining is working just the way Rhiju intended for it to. Once the remaining time estimate gets <10min. then time starts moving slower. This is avoid exceeding 100%. So, basically, once you get below a 10 minute estimated time remaining, the estimate is not on track anymore. Basically, the client is unsure exactly when it will finish, but in each case, the 15 and 17 minutes estimates were not far from right.

...But Rhiju assures us they won't be sending WUs which take more then an hour per model on Rosetta. And so on Rosetta, with shorter WUs, the estimates should appear better. The 1hr time preference is always going to be the toughest to provide a good estimate on. As it is the time preference that will see the most variation (in percentage terms) between the actual time and the preference.

OK, just talked to David K about this. Right now we keep track of time crunched based on a call to the BOINC API ... i.e. the BOINC manager keeps track of how much time was spent on each workunit. If you preempt after an hour and resume later, the BOINC manager will tell Rosetta about the hour already spent.

But if you shut BOINC down and restart that could cause a problem in a lot of estimates... we can try to make the Rosetta app more self-sufficient, keeping track of cpu time spent so far, but that might be a can of worms. Worth the time?

Just so we have all the facts right. When a Ralph Wu 5.58 is resumed after preemt the % done goes back to 0 and time to complete goes very high.
I just had one it preemted at 2 H and when restarted time to complete was
at nearly 6 H (rapidly going down as % was going up). I have a 4 H setting for
Ralph on that computer.

Anders n

...our solution to this problem is to be careful -- we do *not* plan to send workunits to Rosetta@home that take more than an hour per decoy!

It's funny you should say that RIGHT when I've got 4 Ralph WUs and all 4 are taking more then an hour for their first model. (but TRUE, you said "on Rosetta" not "on Ralph").

I ended and started BOINC again (I've got 5.57), this time they didn't end and report in the way they did before... but the completion % of the two tasks is the same, even though one had completed two models, and the other lost all of it's work on model 1. So, right now one has 2:20:xx of CPU, and is showing same %completed as the one that just restarted 5min ago. So it isn't taking total CPU time for the WU in to account, just CPU since last BOINC start up.

See also anders n's post where they observed similar behavior.

...our solution to this problem is to be careful -- we do *not* plan to send workunits to Rosetta@home that take more than an hour per decoy!

It's funny you should say that RIGHT when I've got 4 Ralph WUs and all 4 are taking more then an hour for their first model. (but TRUE, you said "on Rosetta" not "on Ralph").

I ended and started BOINC again (I've got 5.57), this time they didn't end and report in the way they did before... but the completion % of the two tasks is the same, even though one had completed two models, and the other lost all of it's work on model 1. So, right now one has 2:20:xx of CPU, and is showing same %completed as the one that just restarted 5min ago. So it isn't taking total CPU time for the WU in to account, just CPU since last BOINC start up.

See also anders n's post where they observed similar behavior.