<message>
Maximum memory exceeded
</message>

in task 1578464

AdeB

ran ok, but validate errors:

https://ralph.bakerlab.org/result.php?resultid=1579165
https://ralph.bakerlab.org/result.php?resultid=1579162
https://ralph.bakerlab.org/result.php?resultid=1579146
https://ralph.bakerlab.org/result.php?resultid=1579140
https://ralph.bakerlab.org/result.php?resultid=1579139
https://ralph.bakerlab.org/result.php?resultid=1578704

https://ralph.bakerlab.org/workunit.php?wuid=1397739
I kill this wu (and other 5), because after 36 minutes it's at 0% (initializing)....
Use of ram? Over 500 mb!!

242l_A_50_I_ddg_predictions_82409_001_MUT.242l_A_50_I_.out_12117_1_0

According to the information in the graphics window this one was still initializing after 52 minutes. A minute or so after I closed the window it uploaded and now reports that it has completed one decoy successfully. As my target runtime is 4 hours I suspect that it is not simply a matter of an error in the graphics. The question then is would it be just as well to abort WUs that don't initialize within x minutes and report them here as stefanob has done or is there valuable information in the 4.41MB upload that would be lost if the WU is not allowed to end on its own?


Snags

The question then is would it be just as well to abort WUs that don't initialize within x minutes and report them here as stefanob has done or is there valuable information in the 4.41MB upload that would be lost if the WU is not allowed to end on its own?
Snags

I kill the wu because i cannot work with my pc (over 1Gb of ram....)!!!
I think that debug is important, but this is too much for my poor notebook
I return to rosetta 1.97 (90 mb at WU)

I had to kill this task. It made other applications crash and claimed almost all of the memory (including virtual memory).

AdeB

Work Unit: 1aye D 35 a ddg predictions 82009 003 MUT D 35 A .out 12105 1 1

Taking up 563 K of Ram

Now going on 16 hours.

Now ending, locking up my system time to time!

Work Unit 1395454

---

238l_A_103_V_ddg_predictions_82409_010_MUT.238l_A_103_V_.out_12126_1_0

Another one. I was away from the computer while this one ran but it ended itself in less than an hour with the same report as the last WU. I'm sorry I wasn't around to take note of the amount of memory it claimed. Obviously if it's taking up all the computer's memory it's going to get killed by the cruncher. Has anyone tried quitting(not suspending) BOINC (or even just that task) thus removing it from memory then restarting? I wonder if it would error out immediately on restart and further if that error report would contain anything more useful than a simple abort.
I vaguely recall the project adding code to end those WUs that never seem to start and assume that's catching mine though I see nothing obvious in the sterr out unless the clue is this line: reached end of minirosetta::main(). I further assume that claiming one decoy is just to give me some credit without having to run a special validator script. If my assumptions are correct the question of most interest though would be, Why did my WUs end gracefully but Nflight's run on for 16 hours?

Snags

KIlled This Task.
Target time 2hrs. No progress after 6.5 hrs.

---

theta_PCS_BOINC_abrelax.1xcycles.v1_SAVE_ALL_OUT_12132_2_0

21 decoys completed but output file absent:

Thu Aug 27 00:03:14 2009|ralph@home|Computation for task theta_PCS_BOINC_abrelax.1xcycles.v1_SAVE_ALL_OUT_12132_2_0 finished
Thu Aug 27 00:03:14 2009|ralph@home|Output file theta_PCS_BOINC_abrelax.1xcycles.v1_SAVE_ALL_OUT_12132_2_0_0 for task theta_PCS_BOINC_abrelax.1xcycles.v1_SAVE_ALL_OUT_12132_2_0 absent

stderr out:
======================================================
DONE :: 21 starting structures 13985.5 cpu seconds
This process generated 21 decoys from 21 attempts
======================================================

BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down cleanly ...
called boinc_finish

</stderr_txt>
<message>
<file_xfer_error>
<file_name>theta_PCS_BOINC_abrelax.1xcycles.v1_SAVE_ALL_OUT_12132_2_0_0</file_name>
<error_code>-161</error_code>
</file_xfer_error>

Just had two 6 hour WUs fail due to

<error_code>-161</error_code>
</file_xfer_error>

Other than the transfer issue the WUs completed OK and generated a number of Decoys each.

See 1582694 and 1583046

Conan

---

mmhm, i have permanent calculation faults (@40%) :( ...what is the problem?...cu

hK

Another file transfer error:

thioredoxin_PCS_BOINC_abrelax.1xcycles.v1_SAVE_ALL_OUT_12132_19_1

This one only ran for a few seconds:

Incorrect function. (0x1) - exit code 1 (0x1)

ERROR: ERROR: Unable to open silent_input file: 'default.out'
ERROR:: Exit from: ....srccoreiosilentSilentFileData.cc line: 96
BOINC:: Error reading and gzipping output datafile: default.out

==Mike

---

Don't believe everything you think.

4 x the same error:

ERROR: ERROR: Unable to open silent_input file: 'default.out'
ERROR:: Exit from: ....srccoreiosilentSilentFileData.cc line: 96
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

https://ralph.bakerlab.org/result.php?resultid=1583639
https://ralph.bakerlab.org/result.php?resultid=1583638
https://ralph.bakerlab.org/result.php?resultid=1583662
https://ralph.bakerlab.org/result.php?resultid=1583661

happens between 5-9 seconds into the task

I'm getting Ralph workunits for 1.95 while Rosetta is at 1.97. How come?

I'm getting Ralph workunits for 1.95 while Rosetta is at 1.97. How come?

Good question.
Looks like a (quick-)fix to me at Rosetta@home.
Perhaps the techs would like to answer the question why Ralph is still at minirosetta 1.95?

And an error:
proteinG_PCS_BOINC_abrelax.1xcycles.v1_NOGZ_SAVE_ALL_OUT_12136_6_1

ERROR: ERROR: Unable to open silent_input file: 'default.out'
ERROR:: Exit from: ....srccoreiosilentSilentFileData.cc line: 96
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

Had the second run of this WU, the first run it had the same error.

Have a nice day,
Path7.

This 1585116 on Mac sat for over an hour apparently initialising ( 0% progress : model 0 step 0) yet it completed OK. I used the Sampler to get a dump of what it was doing while initialising: it's way too big to post here but will Email it if it's of interest.

I've had the same issue with a few recent Rosetta@home workunits.

Task 1585136
myoglobin_PCS_BOINC_abrelax.1xcycles.v1_SAVE_ALL_OUT_12132_13_1

======================================================
DONE :: 6 starting structures 3145.11 cpu seconds
This process generated 6 decoys from 6 attempts
======================================================

BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down cleanly ...
called boinc_finish

</stderr_txt>
<message>
<file_xfer_error>
<file_name>myoglobin_PCS_BOINC_abrelax.1xcycles.v1_SAVE_ALL_OUT_12132_13_1_0</file_name>
<error_code>-161</error_code>
</file_xfer_error>

</message>
]]>

An earlier attempt to crunch this WU by another user resulted in the same xfer error.

This task errored after 5+ hours with a file upload error.

---