My uncredited Validate Errors have dropped to only 1 across all my PCs, but I note Tom M has suffered 15, losing ~6600 credits and his average has dropped from 115k to 106k - still 11% higher than before, but much lower than it initially jumped up to.

Otherwise, steady as she goes

I just swapped the MB into a Mining Rack and added back the three Titan V's I used to run on it. Then had to troubleshoot for hours and had a brief house power outage so my RAC has suffered. Based on Free-DC, I am hopeful I will get back up past 103K and maybe as high as 117K on my RAC.

I wonder what I did which caused validate errors?

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

Crossing Fingers

Weirdly, I'm glad to read that. If nothing was going on with your system and these problems appeared I'd worry because you'd never know when it was going to reappear.
Tasks seem to be sensitive to things like a power outage, so whatever happened there is likely to have resulted in the validation errors.
Plus, I imagine, downtime during that period will have resulted in your credit loss and, yes, consistent running should boost you back up.
If not, that is, for the severe lack of tasks atm - down to under 59k in progress.
I see you're down to 133 tasks for your 128 threads, so you're on the brink of idle threads - not for anything you've done, just a lack of tasks for everyone.

So frustrating when there are still 4.8 million tasks queued on the front page, but not made ready for downloading.

---

Sid:
I did just as you suggested. Copied everything into Notepad.
It's still there at the bottom of the list. I updated Rosetta like you said.
But nothing happened that I could perceive. I hit the Update tab several times per day, with similar results (i.e., nothing).
Later, AMD did send two error messages which then went away.

I have checked the typing of my Notepad entry to make sure it is exactly as you wrote it in your response. So I don't know why your patch didn't work. Maybe it's another example of my digital dolthood.

You made the change and you double-checked it's still there.
That's good - you can't do any more than that.

As one very final check, do another Rosetta update, then look at your Event log.
It should look like this

27/05/2025 12:26:01 | Rosetta@home | Sending scheduler request: To fetch work.
27/05/2025 12:26:01 | Rosetta@home | Requesting new tasks for CPU
27/05/2025 12:26:09 | Rosetta@home | Scheduler request completed: got 0 new tasks
27/05/2025 12:26:09 | Rosetta@home | No tasks sent
27/05/2025 12:26:09 | Rosetta@home | Project requested delay of 31 seconds

That is, you asked for tasks and you "got 0 new tasks"
Because there are so few to send to anyone right now.

What it would've said in the past is something like 'error in server feed' (forgot the exact wording but something to do with errors and servers)
That is, it couldn't ask for tasks in the first place. That's the problem your hosts edit fixed and why you received nothing for months.

That you got nothing through straight away isn't a surprise. When I check my own log I see multiple attempts and it's 'got 0 new tasks' most of the time.
But over maybe 24hrs, after multiple attempts, the occasional task does slip through. That's what I'd hope you see soon.

---

But over maybe 24hrs, after multiple attempts, the occasional task does slip through. That's what I'd hope you see soon.

As an example, minutes after my last post, this happened on the machine I'm posting from atm

27/05/2025 12:47:36 | Rosetta@home | Sending scheduler request: To fetch work.
27/05/2025 12:47:36 | Rosetta@home | Reporting 2 completed tasks
27/05/2025 12:47:36 | Rosetta@home | Requesting new tasks for CPU
27/05/2025 12:47:41 | Rosetta@home | Scheduler request completed: got 3 new tasks
27/05/2025 12:47:41 | Rosetta@home | Project requested delay of 31 seconds

I have no idea how I keep getting sufficient tasks on all my PCs when there are so few to grab.
I'm having some kind of miracle-run atm

Edit: and now this. It's inexplicable tbh

27/05/2025 13:11:59 | Rosetta@home | Sending scheduler request: To fetch work.
27/05/2025 13:11:59 | Rosetta@home | Reporting 1 completed tasks
27/05/2025 13:11:59 | Rosetta@home | Requesting new tasks for CPU
27/05/2025 13:12:03 | Rosetta@home | Scheduler request completed: got 2 new tasks
27/05/2025 13:12:03 | Rosetta@home | Project requested delay of 31 seconds

Edit 2: Checking further, 26 grabbed in the last 14hrs running on a 16-thread PC with 12hr runtimes.
8 of them already running and 8 more due to start in the next hour or two - I'm only running a relatively small offline cache

---

I haven't received any Rosetta tasks in a month or so.

I'm about ready to give up on Rosetta. It's become too unstable and unreliable for me.

I just want to download tasks and let BOINC and my computer process them with little input required from me.

You guys suggested some fixes and work-arounds. But I can't implement any of those because I am a digital dolt.

S. Gaber
Oldsmar, FL

This computer is already running WCG, Einstein, Milky Way and Asteroids, in addition to Rosetta. It has been crunching them for some time without problems. I try not to let it overheat by keeping it under 190 degrees F.

This computer: AuthenticAMD AMD Ryzen 7 5700G with Radeon Graphics [Family 25 Model 80 Stepping 0]
(16 processors) AMD AMD Radeon(TM) Graphics (6227MB) OpenCL: 2.0 Microsoft Windows 11
Core x64 Edition, (10.00.26100.00)

This is the fifth computer that I have used in crunching BOINC projects, starting with SETI@Home almost at its inception. I run them 24/7/365 until they expire from exhaustion.

You were correct that I was not able to find the two lines of which you speak. As i said, I am a digital dolt with little experience or patience for that sort of thing. I can do mechanical and electronic assembly -- I put this computer together from parts purchased online. But manipulating lines of software are not in my skill set. After more than 20 years, I can still only do the basics of BOINC.

But I appreciate you reaching out to assist clueless me.

Thank you
S. Gaber

I thought I posted this days ago, but maybe I didn't send it for some reason.

It looks like you'd be happy to continue if you had some dolt-proof instructions to follow.
I tried to write something like that a while back, so see If this is straightforward enough to follow

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

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

Sid:
I did just as you suggested. Copied everything into Notepad.
It's still there at the bottom of the list. I updated Rosetta like you said.
But nothing happened that I could perceive. I hit the Update tab several times per day, with similar results (i.e., nothing).
Later, AMD did send two error messages which then went away.

I have checked the typing of my Notepad entry to make sure it is exactly as you wrote it in your response. So I don't know why your patch didn't work. Maybe it's another example of my digital dolthood.

But I'm not bothered by the lack of Rosetta tasks (aside from not contributing to the research).
The computer is very happily crunching Milky Way, Einstein, Asteroids and WCG.

To be honest, Rosetta's 3-day completion requirement sometimes posed problems trying to keep up with all of those.

But I thank you for the attempt.

Sincerely,
S.Gaber

I believe that after you make changes to the hosts file on ANY operating system you need to restart the whole system for the changes to take effect. I know it works on both my Linux and Windows systems.

---

Proud member of the O.F.A. (Old Farts Association)

I believe that after you make changes to the hosts file on ANY operating system you need to restart the whole system for the changes to take effect. I know it works on both my Linux and Windows systems.

I run Red Hat Enterprise Linux release 8.10 (Ootpa) and when I changed my /etc/hosts file, it took effect immediately. No need to restart the system or even the Boinc client.

---

I believe that after you make changes to the hosts file on ANY operating system you need to restart the whole system for the changes to take effect. I know it works on both my Linux and Windows systems.

I run Red Hat Enterprise Linux release 8.10 (Ootpa) and when I changed my /etc/hosts file, it took effect immediately. No need to restart the system or even the Boinc client.

I will admit, I am basing my Linux results on when I changed system names in the hosts file. I had to either run some exotic linux command or restart the system. Based on the Windows results mentioned above I suspect windows only reads it's hosts file during startup.

Respectfully,

---

Proud member of the O.F.A. (Old Farts Association)

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

My cache is down to 92 tasks. And my WCG with resource "0" is currently running about 22 tasks.

I have started up my update script to see if I can suck down some more.

---

Proud member of the O.F.A. (Old Farts Association)

I believe that after you make changes to the hosts file on ANY operating system you need to restart the whole system for the changes to take effect. I know it works on both my Linux and Windows systems.

I run Red Hat Enterprise Linux release 8.10 (Ootpa) and when I changed my /etc/hosts file, it took effect immediately. No need to restart the system or even the Boinc client.

Yes, Windows users reported this too.
I guess it's possible it may not work that way for everyone, so by all means reboot if the Event Log error message related to servers persists, but otherwise it's reportedly fine straight away.

---

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

My cache is down to 92 tasks. And my WCG with resource "0" is currently running about 22 tasks.

I have started up my update script to see if I can suck down some more.

Ugh. This is where having a larger cache than the barest minimum helped, and longer than default 8hr (or borked 3hr) runtimes too, for a while, but it's still not sufficient.
The rate your 128 threads plough through Rosetta tasks makes it hard to keep up.
Meanwhile my 16-thread PC has grabbed 11 tasks in the last 40 minutes - I'm leading a charmed life atm.
In progress tasks are down further to 55k.

One more appeal to those still using default runtimes that turn out to only last 3hrs to explicitly set it to 8hrs in their online Rosetta settings

---

I believe that after you make changes to the hosts file on ANY operating system you need to restart the whole system for the changes to take effect.

Nope.
Although you can ipconfig /flushdns to clear the cache.

---

Grant
Darwin NT