Some errors with wus secY_hybrid_02

504195042
504195047

- Unhandled Exception Record -
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x7C812AFB

Engaging BOINC Windows Runtime Debugger...

---

I'm seeing about 1 in 50 errors as well. These seemed to error out on the wingmans machine as well. Clearly there is some glitch in the 3.30 workunits...

However, about 6 of them were because of me when I tried to increase RAM with mixed G-Skill/Corsair parts and it buggered up long term... Oh well.. I knew I was taking a chance... order more Corsair to do it properly.

Many error out now (with ram restored correctly) in the first few minutes or seconds and the wingmans do as well. Soooo, don't think it is really a problem on my system..

Also, FWIW, all my running boxes have GPU's do tasks as well.

It's too bad the WU display here doesn't show the normal Error, Pending, Valid selections that most BOINC websites have or it would be a lot easier to figure things out.

Still crunching! Seem to be getting fewer errors as I work through the last batch that downloaded..

8-)

Got some system-wide slowdowns, high RAM usage, and a couple computation errors with 3.30.

---

Hi.

Had this one error today, after 18sec.

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=460839382

ab_11_29__optpps_T5311_optpps_03_09_35686_277399_1

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>


Initialization complete.
Setting WU description ...
Unpacking zip data: ../../projects/boinc.bakerlab.org_rosetta/minirosetta_database_rev48292.zip
Setting database description ...
Setting up checkpointing ...
Setting up graphics native ...
EFPCWLVEEFVVAEECSPCSNFRAKTTPECGPTGYVEKITCSSSKRNEFKSCRSALME
can not find a residue type that matches the residue PRO_p:pro_hydroxylated_case1at position 3

ERROR: core::util::switch_to_residue_type_set fails

ERROR:: Exit from: src/core/util/SwitchResidueTypeSet.cc line: 143
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

</stderr_txt>
]]>

---

Not had any errors, but as these units work through, they fail to upload, so I have 22 units complete but going nowhere. Some seem partially uploaded. A retry sees them upload, but only to the percentage that they had stopped at before, then zilch. This just started to happen by itself, so I'm guessing that all the successfully completed and uploaded WUs were pre-3.30.
Any news would be good!
Dennis

---

Menace, how many K of the file is getting sent up before it ends? It shouldn't reset to zero if anything is actually reaching the upload server. Uploads should not be dependent upon a specific R@h version either. I am just a home user like everyone else, and I've not been seeing any upload problems. Perhaps you have a firewall or other network issue somewhere?

Are others having upload problems?

---

Rosetta Moderator: Mod.Sense

Hi.

This is an odd one it ran for 1hr, 30min then erred.

Rc015_broker_pairings_50135_4819_0

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=461221621

( last part of log )

Unpacking WU data ...
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/Rc015_pairings_broker_input.zip
Setting database description ...
Setting up checkpointing ...
Setting up graphics native ...
BOINC:: Worker startup.
Starting watchdog...
Watchdog active.
# cpu_run_time_pref: 14400

ERROR: impossible to find a valid fold-tree with given sheet-topology and pairings
ERROR:: Exit from: src/protocols/jumping/SheetBuilder.cc line: 328
called boinc_finish

</stderr_txt>
]]>

---

Hi.

Is it better to abort tasks i have for mini 3.30, so you get BETTER usable results with the new app.

[Quote] May 16, 2012
Rosetta@Home software updated to version 3.31. Addresses issues with improper initialization of inputs in hybrid protocol for comparative modeling. /[quote]

I'm just asking after seeing this, specially with CASP running.

---