If you study the Grafana dashboard for Rosetta you can see when large groups of work were released and when tasks were generated to be released.

https://grafana.kiska.pw/d/boinc/boinc?orgId=1&var-project=Rosetta@Home&from=now-7d&to=now

Bill F

---

In October 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

If you study the Grafana dashboard for Rosetta you can see when large groups of work were released and when tasks were generated to be released.

https://grafana.kiska.pw/d/boinc/boinc?orgId=1&var-project=Rosetta@Home&from=now-7d&to=now

Thanks Bill - I keep forgetting that page. I must bookmark it
But I'm thinking more of whether the project is converting the 1.8m queued tasks so they're ready to send - and it's still not.
Let alone fixing the out-of-date security certificates of servers that's catching everyone out - no dice there either.
Let alone all the other technical things that go way over my head and I can't recall to even mention.

I don't think I'm asking too much - except it appears I am...

---

If you study the Grafana dashboard for Rosetta you can see when large groups of work were released and when tasks were generated to be released.

https://grafana.kiska.pw/d/boinc/boinc?orgId=1&var-project=Rosetta@Home&from=now-7d&to=now

Thanks Bill - I keep forgetting that page. I must bookmark it
But I'm thinking more of whether the project is converting the 1.8m queued tasks so they're ready to send - and it's still not.
Let alone fixing the out-of-date security certificates of servers that's catching everyone out - no dice there either.
Let alone all the other technical things that go way over my head and I can't recall to even mention.

I don't think I'm asking too much - except it appears I am...

Noticed it yesterday and it's still the case - assimilation building up a backlog too.
I don't think much of that maintenance

---

128.95.160.156 boinc-files.bakerlab.org

Yep, that's work, thx!

By the way... how did you know that this server(128.95.160.156) also handles download requests by boinc-files.bakerlab.org hostname?
Was it a simple iterating through university IP addresses?..
Or did one of the staff share such information?

Although I have very rarely crunched for this project and visited this forum even less often over the past years, this is not the first time I have seen these strange "dirty hacks" just to get BOINC to work with this project...
It looks extremely stupid and depressing : /

i don't know, i just grab it there on this forum ^^

128.95.160.156 boinc-files.bakerlab.org

Yep, that's work, thx!

By the way... how did you know that this server(128.95.160.156) also handles download requests by boinc-files.bakerlab.org hostname?
Was it a simple iterating through university IP addresses?..
Or did one of the staff share such information?

Although I have very rarely crunched for this project and visited this forum even less often over the past years, this is not the first time I have seen these strange "dirty hacks" just to get BOINC to work with this project...
It looks extremely stupid and depressing : /

Someone discovered it here in late March

There is no need to disable ipv6 at all, only these two Rosetta-Servers can be reached with ipv4 with these IPs.
It works only this way at the moment:

128.95.160.156 boinc-files.bakerlab.org
128.95.160.156 bwsrv1.bakerlab.org

I agree that you shouldn't have to disable ipv6, but the second part I don't agree with. I only have ipv4 internet connectivity, and set up a packet sniffer to see what R@H IP's my machines are connecting to. So far I've seen packets to/from .156, .157 and .134, uploading/downloading/updating, seem to use .156 and .157, and reporting seems to use .134 (hoping it uses .135 as well, but I've only had a couple WU to report complete since I started the capture, so not enough data yet).

---

Noticed it yesterday and it's still the case - assimilation building up a backlog too.
I don't think much of that maintenance

It took fully 4 days for that assimilation backlog to slowly clear down

---

Hi !

I have a problem with 2 tasks of Rosetta Beta. The 2 tasks are terninated ok but the 2 same tasks refuse to be validated since at least 2 weeks. Any idea why?

I run with win 11 on a i7 10th generation.

thank's and sorry for my so-so written english !

---

Hi !

I have a problem with 2 tasks of Rosetta Beta. The 2 tasks are terninated ok but the 2 same tasks refuse to be validated since at least 2 weeks. Any idea why?

The las time your system contacted the Rosetta server was on the 6th July.
Is BOINC running? Has the Project been suspended? Is networking enabled?

---

Grant
Darwin NT

Not reporting a problem

4-5000k Roseta Beta tasks have been consistently available to download for almost all of the last 18 hours
I'm reluctant to think something has been fixed permanently, but this has been the most consistent availability for many months

On the downside, there are only 870k tasks queued left.
It may turn out this only accelerates us running out of tasks altogether

---

Hello,

I’m not receiving a work package because I keep getting a 'feeder not running' error message, even though the server status page shows it’s running.
Do you have any suggestions as to what might be causing this issue? Thank you!

2025. 07. 20. 18:23:28 | | Fetching configuration file from https://boinc.bakerlab.org/rosetta/get_project_config.php
2025. 07. 20. 18:23:43 | Rosetta@home | Fetching scheduler list
2025. 07. 20. 18:23:44 | Rosetta@home | Master file download succeeded
2025. 07. 20. 18:23:49 | Rosetta@home | Sending scheduler request: Project initialization.
2025. 07. 20. 18:23:49 | Rosetta@home | Requesting new tasks for CPU and NVIDIA GPU
2025. 07. 20. 18:23:51 | Rosetta@home | Scheduler request completed: got 0 new tasks
2025. 07. 20. 18:23:51 | Rosetta@home | Server error: feeder not running
2025. 07. 20. 18:23:51 | Rosetta@home | Project requested delay of 3600 seconds

I’m not receiving a work package because I keep getting a 'feeder not running' error message, even though the server status page shows it’s running.
Do you have any suggestions as to what might be causing this issue? Thank you!

2025. 07. 20. 18:23:28 | | Fetching configuration file from https://boinc.bakerlab.org/rosetta/get_project_config.php
2025. 07. 20. 18:23:43 | Rosetta@home | Fetching scheduler list
2025. 07. 20. 18:23:44 | Rosetta@home | Master file download succeeded
2025. 07. 20. 18:23:49 | Rosetta@home | Sending scheduler request: Project initialization.
2025. 07. 20. 18:23:49 | Rosetta@home | Requesting new tasks for CPU and NVIDIA GPU
2025. 07. 20. 18:23:51 | Rosetta@home | Scheduler request completed: got 0 new tasks
2025. 07. 20. 18:23:51 | Rosetta@home | Server error: feeder not running
2025. 07. 20. 18:23:51 | Rosetta@home | Project requested delay of 3600 seconds

Something changed at the project end. You need to make this edit to your hosts file

To edit the hosts file in Windows using Notepad - at location C:/Windows/System32/drivers/etc/hosts - follow these steps:
<Open Notepad as Administrator>
Search for "Notepad" in the Windows search bar.
Instead of left-clicking it, right-click on Notepad and select "Run as administrator"
When the dialog box pops up select Yes

<To open the Hosts File>
In Notepad
Go to File > Open.
Navigate to C:/Windows/System32/drivers/etc which will appear empty
Change the file type filter at bottom right from "Text Documents (*.txt)" to "All Files"
Select the "hosts" file that appears and click "Open"

<Edit the hosts File>
On a fresh line at the bottom, type

#Rosetta@home
128.95.160.156 boinc-files.bakerlab.org
128.95.160.156 bwsrv1.bakerlab.org

Save the file with no extension - simply 'hosts' not 'hosts.txt'

That should be it - no need to reboot.
Return to Boinc manager, select Rosetta and click the "Update" button

---

Got tasks, thank you very much!