For some weeks now I've had several tasks sitting in Ready to Report and when I request an Update for the project get "Server Error: Feeder not Running." So what am I doing wrong since others are obviously processing tasks?

I've been running Rosetta for some years and this is a new issue to me.

TIA

For some weeks now I've had several tasks sitting in Ready to Report and when I request an Update for the project get "Server Error: Feeder not Running." So what am I doing wrong since others are obviously processing tasks?

They were just extremely lucky to have requested work when it was available.
Mostly, it isn't.

I've been running Rosetta for some years and this is a new issue to me.

It's been an issue for 6 months (or more, and one of many), If you use IPV6, you can't get or return work.
You need to edit your Hosts file to get to the Scheduler etc directly.


See here.

---

Grant
Darwin NT

Edit: I see 3 of your PCs have grabbed some of those tasks

I seem to have kicked the sleeping beast with my question(s) and it's awakened. I've turned off WCG requests on some of the computers to try and get more Rosetta tasks.

Why?
If there ends up being some WCG work, you'll get some. If there is some Rosetta work you might get some. Disable WCG and you're unlikely to get any.
When work is released here you generally have a 30min or less window to request some before it's gone.

---

Grant
Darwin NT

Edit: I see 3 of your PCs have grabbed some of those tasks

I seem to have kicked the sleeping beast with my question(s) and it's awakened

I'm a big fan of this kind of thinking
There's no reason for it ever to work, apart from all the times it does

---

Is there a place where I can send a "private" message to whoever is responsible for the 4.20 tasks being sent out? I'm experiencing problems with them on one computer, only one computer. I suspect it has to do with the bios/cpu/os/video card configuration. Basically those tasks will go out grab every byte of memory, swap, and then things really get ugly since the only way out of it is to hit the power button. I have a work around, hobble along limiting the number of 4.20 tasks that are allowed to run.

---

Is there a place where I can send a "private" message to whoever is responsible for the 4.20 tasks being sent out?

Nope.
Although it would have come in useful over the years when a researcher released a whole batch of faulty Tasks.

I'm experiencing problems with them on one computer, only one computer. I suspect it has to do with the bios/cpu/os/video card configuration. Basically those tasks will go out grab every byte of memory, swap, and then things really get ugly since the only way out of it is to hit the power button. I have a work around, hobble along limiting the number of 4.20 tasks that are allowed to run.

Limiting the number of Rosetta 4.20 Tasks is the only work around other than limiting the number of cores/threads in use, which is BOINC wide, or limiting the number of cores/threads for the project as a whole, which would limit the number Beta Tasks if they were to ever release anymore.

My i7 8700k systems had 16GB of RAM, but i upgraded them to 32GB so they could handle the large RAM requirement Rosetta 4.20 Tasks.
Generally you needed roughly 2GB RAM per Rosetta 4.20 Task, although from memory there were batches where some Taks would use as much as 4GB each. I'm surprised it's taken this long for some larger RAM requirement Tasks to be released since they started issuing Rosetta 4.20 Tasks again.

---

Grant
Darwin NT

Generally you needed roughly 2GB RAM per Rosetta 4.20 Task.

And that's the problem, on that one computer. Basically it's got 32GB of memory and 16c/32t. It runs out of memory. But, I have another machine with the same amount of memory and cores/threads (everything else about the computer is different). It works fine.
I've gone into the /var/lib/boinc/projects/boinc.bakerlab.org_rosetta/app_config.xml file and added the lines:
<app>
<name>rosetta</name>
<max_concurrent>16</max_concurrent>
</app>
To limit the amount of rosetta tasks running.
Changing the values in the /var/lib/boinc/global_prefs_override.xml file to:
<ram_max_used_busy_pct>95.000000</ram_max_used_busy_pct>
<ram_max_used_idle_pct>95.000000</ram_max_used_idle_pct>
Which seems to do nothing. It appears to ignore it and runs it out of memory/swap.
BTW, this isn't the first time I've run into this, and it only happens on that one set of circumstances on the one computer. Other projects/computers work fine.

---