Server is still dead.

It seem mostly up for me.

Nope.
The boinc-process server is still dead, that's according to the Server Staus page & the number of Tasks that are piling up waiting for Validation & Assimilation.
Waiting for Validation is over 325,000 now.

That's why even though people are returning work, their Credit isn't increasing & their RAC is going down.

---

Grant
Darwin NT

I don't want to tempt fate, but the boinc-process server appears to be alive again (at least for now).

---

Grant
Darwin NT

I really wish they'd fix the application error handling, or at least the data they send out to process. Got a bunch of Tasks that have errored out.

ERROR: Error in protocols::cyclic_peptide_predict::SimpleCycpepPredictpplication::set_up_n_to_c_cyclization_mover() function: residue 1 does not have a LOWER_CONNECT.

*deep sigh*

---

Grant
Darwin NT

I don't want to tempt fate, but the boinc-process server appears to be alive again (at least for now).

And the backlog has cleared.

---

Grant
Darwin NT

I am receiving a constant error message via BOINC re Rosetta@Home and I am not sure how to resolve it.

The message (relating solely to Rosetta@Home) is:

"Could not determine location of executable.
Could not find database. Either specify -database or set variable ROSETTA3_db"

Can someone advise where in user files (I assume) a configuration file relating to BOINC and Rosetta@Home needs modification?

Many thanks, Chris Raisin

I am receiving a constant error message via BOINC re Rosetta@Home and I am not sure how to resolve it.

The message (relating solely to Rosetta@Home) is:

"Could not determine location of executable.
Could not find database. Either specify -database or set variable ROSETTA3_db"

Can someone advise where in user files (I assume) a configuration file relating to BOINC and Rosetta@Home needs modification?

Many thanks, Chris Raisin

I've seen that message many times. Until those workunits get some hard to guess change, expect many more workunits running under Windows to have the same problem.

I am receiving a constant error message via BOINC re Rosetta@Home and I am not sure how to resolve it.

The message (relating solely to Rosetta@Home) is:

"Could not determine location of executable.
Could not find database. Either specify -database or set variable ROSETTA3_db"

Can someone advise where in user files (I assume) a configuration file relating to BOINC and Rosetta@Home needs modification?

Many thanks, Chris Raisin

Where are those error messages being shown?
Looking at your results, there are only 2 that have errored out,

ERROR: Error in protocols::cyclic_peptide_predict::SimpleCycpepPredictpplication::set_up_n_to_c_cyclization_mover() function: residue 1 does not have a LOWER_CONNECT.

Which has been an issue with some Tasks for ages now.

Other than what appears to be a heavily loaded system (11.5 hours to do 8 hours work, 4 hrs 15 min to do 3 hrs work), other than the 2 errored Tasks(due to a configuration issue with the Tasks themselves), all the others have processed & Validated without issue.

---

Grant
Darwin NT

Where are those error messages being shown?
Other than what appears to be a heavily loaded system (11.5 hours to do 8 hours work, 4 hrs 15 min to do 3 hrs work), other than the 2 errored Tasks(due to a configuration issue with the Tasks themselves), all the others have processed & Validated without issue.

Seems the message of the screensaver...

---

A strange error, sadly I can only give a sketchy report but I hope it’s enough :-

Host = https://boinc.bakerlab.org/rosetta/results.php?hostid=6231982

Boinc 7.24.1, Ubuntu 22.04.4

I allowed Ubuntu to update and then rebooted, subsequent to this Boinc Manager disconnected after running for about a minute - the event log showed a Rosetta task restarting and immediately Boinc closing having received signal 15. This would repeat each time I restated the host and the Boinc service restarted.

I have now aborted all of the Rosetta tasks and this behaviour has now stopped.

(How) can a Rosetta task kill Boinc?

Just a notification as I’ve never heard this described before.

You ran out of memory. Six jobs of 2.6 GB and you have 16 GB.

You ran out of memory. Six jobs of 2.6 GB and you have 16 GB.

That might do it.
I've got half that many cores/threads & twice that amount of RAM and over the last couple of days when i had mostly Rosetta_VS Tasks there have been times i've had over 60% of my RAM in use.
Even without the 2GB + Tasks, there were plenty of others using 1-1.5GB.


But normally if lack of RAM is an issue, the Taks should have suspended with a "Waiting for memory" note. It shouldn't cause things to crash & burn.

---

Grant
Darwin NT

You ran out of memory. Six jobs of 2.6 GB and you have 16 GB.

Ach, I thought I had 32gb.

I remember now, the 2 sticks wouldn't play with each other :-(

The other machine has 64gb, I'll update this one to match

Thanks