I moved Markus' post here from Q&A boards. Sorry the post is so long.

Looks like one of the CAPRI WUs may have caused the reported msgs.

See Rhiju's post below/above. There have been some problems with these tasks on some machines and so they've stopped sending them out.

Markus, could you post links to the two specific hosts (and the specific tasks if possible) where you had problems?

---

Rosetta Moderator: Mod.Sense

Tell me there's some mistake here in the native structure shown
(linky to screenshot with a rather straight native structure shown for a t015_1_NMRREF_1_t015_1_id_model_07_idlIGNORE_THE_REST_core_2097_3599_0 task).

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

Result ID 106047623
Name t030__BOINC_CAPRI14_DOCK_FIXBACKBONE_POSE_LOOPS-t030_-plexinmonomer__2083_6224_0
Workunit 96261079
Created 16 Sep 2007 14:15:43 UTC
Sent 16 Sep 2007 14:34:53 UTC
Received 20 Sep 2007 3:58:44 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 510574
Report deadline 26 Sep 2007 14:34:53 UTC
CPU time 23419.390625
stderr out <core_client_version>5.10.20</core_client_version>
<![CDATA[
<stderr_txt>
# cpu_run_time_pref: 21600
# random seed: 3549877
# cpu_run_time_pref: 21600
**********************************************************************
Rosetta score is stuck or going too long. Watchdog is ending the run!
Stuck at score -207.662 for 1800 seconds
**********************************************************************
GZIP SILENT FILE: .xxt030.out

</stderr_txt>
]]>


Validate state Valid
Claimed credit 97.7521869214656
Granted credit 20
application version 5.80

This WU ran for 23,419 secs for only 20 credits, is this right?

Well Michael at least you got 20, mine ran for over 28,000 sec and got 5.38.

---

I have 5 machines on Rosetta at present:

3x Intel E4300 Core2Duos- Kubuntu v7.04 (64bit) 1gb ram - these machines have been locking one core and sometimes both cores over the last day or so. I have aborted all WU's with the word CAPRI in them. I also currently have nearly all work units with 'IGNORE THE REST' in the units name also locking and freezing cores or completely locking machines with an error message saying something like 'if this keeps happening you may need to reset the project'.

1x AMD X2/4600 - Kubuntu v7.04 (64bit) 1gb ram - this machine is mostly ok - no locking but some errored WU's.

1x AMD 3200+ - Kubuntu v7.04 (32bit) 512mb ram - same as the 4600 machine above.

I currently have 2 of the E4300's locked - no work ticking over for the last hour or so - one of the machines is totally locked and am unable to use the OS at all - the other machine only has BOINC locked up, but I can use the OS.

---

I noticed that the ...CAPRI14_DOCK... native looked wrong, they were too far apart to be interacting at all, compared with what I have seen before.

Of the eight post-CAPRI WUs that I've returned, two produced "validate errors". I received credit for the other six
but they all had "watchdog shutting down" notes, and one had "WARNING! Not sure non-ideal rotamers are compatible
with symmetry yet..." What's going on?!?

107006854: Validate error
106890130: Watchdog notice
106794699: Watchdog and Warning notices
106724332: Validate error
106613376: Watchdog notice
106550676: Watchdog notice
106521483: Watchdog notice
106514350: Watchdog notice

Of the eight post-CAPRI WUs that I've returned, two produced "validate errors". I received credit for the other six
but they all had "watchdog shutting down" notes, and one had "WARNING! Not sure non-ideal rotamers are compatible
with symmetry yet..." What's going on?!?

107006854: Validate error
106890130: Watchdog notice
106794699: Watchdog and Warning notices
106724332: Validate error
106613376: Watchdog notice
106550676: Watchdog notice
106521483: Watchdog notice
106514350: Watchdog notice

See this post about no more Capri for now.

RE: Watchdog notice

Normal. Been that way since the watchdog was implemented. Since the watchdog runs in a seperate thread, this message just confirms that the watchdog thread properly ended as the task was completed.

So it is just saying everything ended normally, including the watchdog.

---

Rosetta Moderator: Mod.Sense

RE: Watchdog notice

Normal. Been that way since the watchdog was implemented. Since the watchdog runs in a seperate thread, this message just confirms that the watchdog thread properly ended as the task was completed.

So it is just saying everything ended normally, including the watchdog.

When the watchdog has to end a task, is it of any use at all to the project scientifically, or is it practically aborted? I think I heard that the watchdog will abort a task if it goes a given amount of times longer than your preferred runtime, regardless of whether the application is showing visible progress; is this true? If so, are those terminated results useful at all?

---

RE: Watchdog notice

Normal. Been that way since the watchdog was implemented. Since the watchdog runs in a seperate thread, this message just confirms that the watchdog thread properly ended as the task was completed.

So it is just saying everything ended normally, including the watchdog.

When the watchdog has to end a task, is it of any use at all to the project scientifically, or is it practically aborted? I think I heard that the watchdog will abort a task if it goes a given amount of times longer than your preferred runtime, regardless of whether the application is showing visible progress; is this true? If so, are those terminated results useful at all?

oh...good question..has me wondering the same thing.

---

Result ID 106760639
Name NeT6__BOINC_SYMM_FOLD_AND_DOCK_RELAX-NeT6_-mfr__2100_7176_0
Workunit 96937615

Validate state Valid
Claimed credit 91.5795040403045
Granted credit 48.2594968464685
application version 5.80

Never seen such a big difference between claimed and granted credits,unless the WU failed in some way but don't see any sign of that. Anyone got any ideas?

---

When the watchdog has to end a task, is it of any use at all to the project scientifically, or is it practically aborted?

Results are always useful. I exchanged some EMails with Chu some time ago and collected some details on the watchdog. I'll compile them into the FAQ and post them shortly.

Even knowing that a given approach does not function as expected is important to know. This is why Rosetta considers all results useful and meaningful, and attempts to issue credit to participants for their assistence in making such a determination.

---

Rosetta Moderator: Mod.Sense

I moved Markus' post here from Q&A boards. Sorry the post is so long.

Looks like one of the CAPRI WUs may have caused the reported msgs.

See Rhiju's post below/above. There have been some problems with these tasks on some machines and so they've stopped sending them out.

Markus, could you post links to the two specific hosts (and the specific tasks if possible) where you had problems?

Sorry, I've been wondering where my post was gone. The two maschines are

https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=603857
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=509233

How can I figure it out which workunit was currently in progress?

---

Explanation of watch dog added to FAQ here. Please post any comments, or suggestions about it here.

---

Rosetta Moderator: Mod.Sense

serious problems with this WU from 5.80 non capri

---

Left over CAPRI14
https://boinc.bakerlab.org/rosetta/result.php?resultid=106850152

---

Jmarks

I am forgot to say: I have Core Duo processor, ADSL connection and Windows XP SP2 as operating system.

---

beat__BOINC_JUMPRELAX_BARCODE2_CONSTRAINT-beat_-_1951_67075_0 ( workunit 98293407 ) stuck on 0% for >1 hour on an Intel iMac2 under OS X 10.4.10 with Boinc 5.10.20. Aborting.

---

I noticed that all of my work units are now based on the 5.80 Beta again. The last few days, it looked like most of them were an older version of the application.

This morning, I have 5 out of 6 units with Compute Error status.

The computer ID is 43057

Can someone please look into this situation? It is very frustrating to have so much CPU time wasted. I just refocused 100% of this computer on R@H because it looked like the problems were fixed. If we are going back to compute errors, it would appear to be a better use of resources to focus this CPU on other projects until R@H is fixed.

What is the problem with all the failed WUs and 5.8?

---

Thx!

Paul

beat__BOINC_JUMPRELAX_BARCODE2_CONSTRAINT-beat_-_1951_61847_0
WU 108207857 v.5.80
Ran 21% over my specified run time preference; never saw this before.