Tony, do you have JP's EMail address? The French guy who always needs new Rosetta .exe EMailed? Could you ask him to see if he can help with this post by French person on Q&A boards? The main parts that translated properly were that he's poor, alone and in a wheelchair. Perhaps JP can read between the lines better than the translation website.

---

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/

Tony, do you have JP's EMail address? The French guy who always needs new Rosetta .exe EMailed? Could you ask him to see if he can help with this post by French person on Q&A boards? The main parts that translated properly were that he's poor, alone and in a wheelchair. Perhaps JP can read between the lines better than the translation website.

Mail sent

Another question quickly, efficiently and comprehensivly answered!
Thanks a lot guys.

Stwato

Another for you. Result for WU 20318986

Hope these are useful.

---

Ian Cundell, St Albans, UK

Here's one that went crazy. resultid 23976562

On this host hostid 214416

This host does nothing but crunch.

Another host did complete the WU sucessfully.

<core_client_version>5.4.9</core_client_version>
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
X_NB neighbors
increase MAX_NB in param.cc
allatom: 1434 res: 95 atom: 1 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1437 res: 95 atom: 3 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1437 res: 95 atom: 3 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1437 res: 95 atom: 3 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1437 res: 95 atom: 3 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1437 res: 95 atom: 3 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1450 res: 95 atom: 4 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1450 res: 95 atom: 4 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1450 res: 95 atom: 4 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1450 res: 95 atom: 4 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1450 res: 95 atom: 4 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1438 res: 95 atom: 5 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1438 res: 95 atom: 5 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1438 res: 95 atom: 5 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1438 res: 95 atom: 5 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1438 res: 95 atom: 5 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1434 res: 95 atom: 1 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1434 res: 95 atom: 1 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1434 res: 95 atom: 1 has more than MAX_NB neighbors

*snipped a lot of lines*

allatom: 1567 res: 103 atom: 4 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1567 res: 103 atom: 4 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1550 res: 103 atom: 5 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1550 res: 103 atom: 5 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1550 res: 103 atom: 5 has more than MAX_NB neighbors
increase MAX_NB in param.cc
allatom: 1550 res: 103 atom: 5 has more than MAX_NB neighbors


Unhandled Exception Detected...

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

Engaging BOINC Windows Runtime Debugger...

---

Problems with download of WUs: Either now work or heavily overcommitted.

https://boinc.bakerlab.org/rosetta/forum_thread.php?id=1703

Hi,

I run SETI@Home, Einstein and Rosetta. Rosetta is set to 20%. The problem is, that once Rosetta has finished all WUs it never downloads any new WUs. Even when the long_term_debt is highly positive (e.g. 30,000 and bigger) it does not download any WUs. The only way to force download is to pause other projects, but in this case it downloads so many WUs that the computer is overcommitted for many days.

I currently run at "Contact server every 3 days". Even when setting this to 0.3 days before suspending the other projects and resetting it after the download it still downloads too many WUs.

This is what I tried:
1. Set "Contact server every 3 days" to 0.3 days.
2. Set SETI@Home and Einstein to "No new work"
3. Suspend SETI@Home and Einstein
4. Rosetta downloads some WUs
5. Set SETI@Home and Einstein to "Allow new work"
6. Restart SETI@Home and Einstein
7. Set "Contact server every xx days" back to 3 days.
8. Now Rosetta downloads even more WUs, which should not happen since SETI and Einstein are both active -> computer is overcommitted.

Is there a solution to this problem? Resetting long_term_dept to 0.0 on all projects does not help either.

The client errors are there because I have other projects running and therefore manually aborted these Work-Units so that the other project get their share as well. Otherwise Rosetta would have taken over my computers exclusively for several days.

I followed your advice and let it run for several days without any interfearance. I did not get any new work for 5 days but tonight it downloaded 30 work-units and is overcommitted again!

Obviously the scheduling of Rosetta does not work at all.

---

Blimey. Whole flurry of errors. All today (well, yesterday - 16 June). Had nothing like this for weeks.

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

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

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

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

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

---

Ian Cundell, St Albans, UK

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

i was viewing the graphics window at the time it failed incase that makes a difference

---

Want to search the BOINC Wiki, BOINCstats, or various BOINC forums from within firefox? Try the BOINC related Firefox Search Plugins

I have just joined the project. On one PC of the 9 WUs it has been sent it has successfully processed 5 but errored out on 4.

from my log:

17/06/2006 04:25:04 Unrecoverable error for result t299__CASP7_JUMPRELAX_SAVE_ALL_OUT_BARCODE_cterm2_nohelix3_hom001__681_83011_0 ( - exit code -1073741819 (0xc0000005))

Clues or advice?


A different unit to that above but some debug info to help devs.
https://boinc.bakerlab.org/rosetta/result.php?resultid=24466158

---

First error ever on this machine (31,000 credit):

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

stderr out

<core_client_version>5.5.0</core_client_version>
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# random seed: 3706611
# cpu_run_time_pref: 14400
# cpu_run_time_pref: 14400
ERROR:: Exit at: .dock_structure.cc line:401

</stderr_txt>

btw [BOINCUK]Tigher, (0xc0000005) is usually a memory error, in my experience.

btw [BOINCUK]Tigher, (0xc0000005) is usually a memory error, in my experience.

Gulp! Hmmm thanks.

---

Another problem - looks the same from this end as the other ones I had.

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

When I leave from working on the computer, I'll exit IE to see if that helps.

Bandit's Mom

---

https://boinc.bakerlab.org/rosetta/hosts_user.php?userid=94664

I have been accumulating computation errors lately.

---

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

This WU created about three good models with energy minima between -200 and -300. then it failed to do more good models which each succeeding model completing within minutes and always the same energy minimum of about -30. Watching on the graphics showed a stretched protein where no folding was achieved. I "aborted" the model the soft way with 6 restarts of BOINC (to prevent sending out the same WU).

I watched such WU in the past. Perhaps there is a pattern.

---

This WU created about three good models with energy minima between -200 and -300. then it failed to do more good models which each succeeding model completing within minutes and always the same energy minimum of about -30.

I for one have been HOPING to see WUs that would act like that. If you knew that a -300 was possible, and you are sitting at a -30, there are cases where it might be SMART to bail on this one and invest the time in pursuing something with more potential.

I don't know that this is what happened in your case, I'll leave that for the project team to assess. I just wanted to point out that it is the TYPE of thing that I think we'll see more of as the algorythm gets smarter.

---

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/

This WU created about three good models with energy minima between -200 and -300. then it failed to do more good models which each succeeding model completing within minutes and always the same energy minimum of about -30.

I for one have been HOPING to see WUs that would act like that. If you knew that a -300 was possible, and you are sitting at a -30, there are cases where it might be SMART to bail on this one and invest the time in pursuing something with more potential.

I don't know that this is what happened in your case, I'll leave that for the project team to assess. I just wanted to point out that it is the TYPE of thing that I think we'll see more of as the algorythm gets smarter.

I agree! Using previous result for "pruning" decision is an idea that for a long time crossed my mind. I'm a bit in chess engine programming and in these engines a lot of "pruning" is done in positions where one side is just too worse to have any chance of reaching the current score with any move. However in the case reported it was most certainly something different, since the models finished successively in a few minutes without really folding the protein (it was stretched in the graphics) and with always the same score. In the end I had over 150 models of which only three had not been "aborted".

---

stuck at 74.101% Rosetta 5.22 Windows 0.0000% of CPU usage
Thus, aborted by hand after 3 hours of IDLE time!
https://boinc.bakerlab.org/rosetta/result.php?resultid=24659040

Thanks

---

Click signature for global team stats

For the past week or so I've been getting 2-3 crashes per day. The failed work units show up as "Compute Error" with no credit. Do I need to report this? Or will the appropriate party see these errors and be able to deal with them on their own?

---

Do I need to report this? Or will the appropriate party see these errors and be able to deal with them on their own?

It is "HELPFUL" if you report them. It gives the opportunity to ask you questions about your computing environment so they might learn more about the system that's seeing the failure. It is not "required".

Credit for failed WUs is issued once the daily credit run is made. You will see this when you display the WU details... not on the WU listing. Like this one for example.

It looks like most of them were ended by the "watchdog". One was a -107 error (which is something that's been under review for a while already).

The watchdog is trying to assure your computer doesn't get stuck in an unexpected loop on a work unit. If it notices no progress on a work unit in 5 restarts, then it ends it. Do you restart this computer frequently? Or have a number of other projects running in BOINC?

If you would, go to your General Preferences, and let us know what you have set for "Switch between applications every...minutes", and for "Leave applications in memory while preempted?". And is Rosetta your only BOINC project?

---

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/

A crash.

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

It happend when i was shutting down grafics window.

Anders n

---