Please post bugs/issues with minirosetta v1.32 here.

I'm sorry if this is irrelevant to the version and not the servers, but, since the new version came out, I have been unable to receive and WUs, and none of my settings ever changed. Once gain I apologize if this is just the servers and not the version. Just a coincidence.

This WU died on startup:
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=165026170

The task below just failed on my machine. This is the first mini rosetta work unit to get processed since the new release and the error seems to be similar to the errors that I was repeatedly getting on version 1.28.

https://boinc.bakerlab.org/rosetta/result.php?resultid=182934444

BTW, version 5.98 WUs have been running successfully.

Task reported too late to validate ?????

Here are two tasks submitted by a new machine I just brought up. It's a slightly older 2.34 GLIBC machine using 5.8.16 for a client (All the newer ones want GLIBC 2.4+)

The task was obtained, crunched and submitted the next day without any abort or error indicated in the STDOUT.. But with 0.00 credit ??? (The machine is only crunching Rosetta at this point).

What is up with this ?? ... Could it be the machine ?? This is the first time I have seen this one... (and ... yes, the clocks are synchronized by NTP, so TOD should not be an issue)

https://boinc.bakerlab.org/rosetta/result.php?resultid=182943687

stderr out

<core_client_version>5.8.16</core_client_version>
<![CDATA[
<stderr_txt>
# cpu_run_time_pref: 43200
======================================================
DONE :: 1 starting structures 43113 cpu seconds
This process generated 84 decoys from 84 attempts
======================================================

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

</stderr_txt>
]]>

Validate state Task was reported too late to validate
Claimed credit 155.951746654641
Granted credit 0
application version 1.32

https://boinc.bakerlab.org/rosetta/result.php?resultid=182943208

stderr out

<core_client_version>5.8.16</core_client_version>
<![CDATA[
<stderr_txt>
# cpu_run_time_pref: 43200
======================================================
DONE :: 1 starting structures 42875.1 cpu seconds
This process generated 123 decoys from 123 attempts
======================================================

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

</stderr_txt>
]]>

Validate state Task was reported too late to validate
Claimed credit 155.091236560251
Granted credit 0
application version 1.32

---

Looking for a team ??? Join BoincSynergy!!

Please post bugs/issues with minirosetta v1.32 here.

Had the first one I got fail.
ERROR: Cannot find file 'minirosetta_databasechemical/residue_type_sets/centroid/CSD_ATOM_TYPE_SET fa_standard'
ERROR:: Exit from: ....srccorechemicalresidue_io.cc line: 132
called boinc_finish

It is WU ID 165103113

---

Task reported too late to validate ?????

Here are two tasks submitted by a new machine I just brought up. It's a slightly older 2.34 GLIBC machine using 5.8.16 for a client (All the newer ones want GLIBC 2.4+)

The task was obtained, crunched and submitted the next day without any abort or error indicated in the STDOUT.. But with 0.00 credit ??? (The machine is only crunching Rosetta at this point).

What is up with this ?? ... Could it be the machine ?? This is the first time I have seen this one... (and ... yes, the clocks are synchronized by NTP, so TOD should not be an issue)

https://boinc.bakerlab.org/rosetta/result.php?resultid=182943687

stderr out

<core_client_version>5.8.16</core_client_version>
<![CDATA[
<stderr_txt>
# cpu_run_time_pref: 43200
======================================================
DONE :: 1 starting structures 43113 cpu seconds
This process generated 84 decoys from 84 attempts
======================================================

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

</stderr_txt>
]]>

Validate state Task was reported too late to validate
Claimed credit 155.951746654641
Granted credit 0
application version 1.32

https://boinc.bakerlab.org/rosetta/result.php?resultid=182943208

stderr out

<core_client_version>5.8.16</core_client_version>
<![CDATA[
<stderr_txt>
# cpu_run_time_pref: 43200
======================================================
DONE :: 1 starting structures 42875.1 cpu seconds
This process generated 123 decoys from 123 attempts
======================================================

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

</stderr_txt>
]]>

Validate state Task was reported too late to validate
Claimed credit 155.091236560251
Granted credit 0
application version 1.32

found the problem for this one.... copied directory from another cruncher and forgot to dump the client_state.... my bad...

---

Looking for a team ??? Join BoincSynergy!!

Please post bugs/issues with minirosetta v1.32 here.

Had the first one I got fail.
ERROR: Cannot find file 'minirosetta_databasechemical/residue_type_sets/centroid/CSD_ATOM_TYPE_SET fa_standard'
ERROR:: Exit from: ....srccorechemicalresidue_io.cc line: 132
called boinc_finish

It is WU ID 165103113

You can ignore these quick failures. They are old jobs that are getting reissued due to errors or past deadlines. These old jobs will fail because they use an incompatible database. There shouldn't be too many of these so please just ignore them.

are there no new 1.32 work units?
i only got 2 so far and the rest are all 5.98
last download of 1.32 was the 6th if the report date is the 16th?

Hey David, thanks for clearing that up for us, I was about to say "Is there some files missing from the Database?"

Anyhow, just out of curiosity, I checked the Projects folder on all my machines, and it appears that the Mini-Rosetta rev 1.28 executable is gone but the old Database, "minirosetta_database_rev23035" is still there. The new 23513 is there as well. Will there be any more use for the 23035 that went with 1.28? Or is it safe to delete it?

Thanks, keep up the good work guys!

P.S. When is/does CASP8 wrap up?

---

now using boinc mgr 6.2.16 and had to restart the project as folders and files from the old 5.10.45 were not being picked up including tasks.

The errors I post here are from a new batch of work:

https://boinc.bakerlab.org/rosetta/result.php?resultid=183864069
https://boinc.bakerlab.org/rosetta/result.php?resultid=183864068
https://boinc.bakerlab.org/rosetta/result.php?resultid=183862855
https://boinc.bakerlab.org/rosetta/result.php?resultid=183862854

there are many more errors from various 1.32 tasks that would take to much time to post, but the error message is more or less the same....

<core_client_version>6.2.16</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>

ERROR: in::file::zip minirosetta_database_rev23035.zip does not exist!
ERROR:: Exit from: ....srcappspublicboincminirosetta.cc line: 105
called boinc_finish
</stderr_txt>


here is another random sample from over a total of 30+ failed work units between 5.98 and 1.32

https://boinc.bakerlab.org/rosetta/result.php?resultid=183857588
core_client_version>6.2.16</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
ERROR: Option file open failed for: 062408_bblum_abrelax_flags

</stderr_txt>
]]>

0 secs run time

You can ignore these quick failures. They are old jobs that are getting reissued due to errors or past deadlines. These old jobs will fail because they use an incompatible database. There shouldn't be too many of these so please just ignore them.

What's up with this task?

Task ID 184003550
ERROR: Cannot find file 'minirosetta_databasechemical/residue_type_sets/fa_standard/CSD_ATOM_TYPE_SET fa_standard'
ERROR:: Exit from: ....srccorechemicalresidue_io.cc line: 132
called boinc_finish

Outcome Client error
Client state Compute error
Exit status 1 (0x1)
Validate state Invalid
Yet the wing man has completed it good as gold.
Is this normal?
Speedy

---

Have a crunching good day!!

I had 3 that wouldn't run, and it crashed my boinc. I don't have a log since when it closed it erased it. I have no more work units left to be processed.

You can ignore these quick failures. They are old jobs that are getting reissued due to errors or past deadlines. These old jobs will fail because they use an incompatible database. There shouldn't be too many of these so please just ignore them.

What's up with this task?

Task ID 184003550
ERROR: Cannot find file 'minirosetta_databasechemical/residue_type_sets/fa_standard/CSD_ATOM_TYPE_SET fa_standard'
ERROR:: Exit from: ....srccorechemicalresidue_io.cc line: 132
called boinc_finish

Outcome Client error
Client state Compute error
Exit status 1 (0x1)
Validate state Invalid
Yet the wing man has completed it good as gold.
Is this normal?
Speedy

The success was from version 1.28. 1.32 versions will fail for these older tasks , few of which are still lingering around.

Here's another Rosetta Mini unhandled exception error. I got quite a lot of these from 1.28, and this is the only one I have got from ver 1.32 so far. It's always on just the one computer, and always from the Rosetta Mini's. I've never gotten one of these errors ever from 5.82 or 5.98 on any system. Here's a link to the failed WU:

184522226

---

Another one bites the dust: 184906376

What causes this access violation?? And again, it only happens with the Mini's, not Beta.

---

Every morning for the last week, I find the computer frozen, and the mini rosetta on the task bar. I have detached from the project, to see what happens with the other projects.. just for info.

When I close the graphics window, Vista tell me that there is an error with "minirosetta_graphics_1.30_windows_intelx86...". Even so the WU still running normally.

Windows Vista 32, BOINC 6.3.8.

---

Every morning for the last week, I find the computer frozen, and the mini rosetta on the task bar. I have detached from the project, to see what happens with the other projects.. just for info.

I am having this same issue.

This was a strange one. 185494746
The library was activated and an email was sent off. The work unit stopped responding. Boinc had to be shut down and restarted at which point the unit went to 100% and reported.

The stderr txt showed 'needs psipred_ss2 to run filters'
access violation

Despite this it was reported to be a success

---