Edit: In progress just updated to 162k with 4674 showing ready to send.
Edit 2: And validation backlog down to just 11k
Could everything really be fixed, or is it just a false dawn?

I'm thinking false dawn.
The Assimilators appeared to do OK early on as the Validation backlog was cleared. And the amount of work In progress climbed nicely as there were Tasks Ready to Send- for a while.
But now the In progress work appears to have plateaued and is dropping again as the Tasks Ready to Send is pretty much back to 0 again, and the assimilator backlog continues to grow, again.

---

Grant
Darwin NT

Ready to send is still pretty much 0, In progress continues to decline, Assimilator backlog continues to grow.
It's still borked.

---

Grant
Darwin NT

I can't report my finished and uploaded work
message: Rosetta@home 27.03.2025 12:19:56 (CET) Server error: feeder not running

Project status tells feeder is running

---

Matthias

Consider me confused. Here are the properties of the last Rosetta that I downloaded, hopefully the formatting isn't terrible, it says it wants 8 hours of processing time.

Application Rosetta Beta 6.06
Name 11mrredo_11_hallucinated_138_30_SAVE_ALL_OUT_3013178_65
State Ready to start
Received Wed 26 Mar 2025 10:07:34 AM MST
Report deadline Sat 29 Mar 2025 10:07:34 AM MST
Estimated computation size 80,000 GFLOPs
Executable rosetta_beta_6.06_x86_64-pc-linux-gnu

I looked at another computer and it's pretty much a mirror of this also. In the mean time this computer is running WCG jobs that appear to have been downloaded 3 days ago.

What Grant said is right.
Before the task is started the runtime shown to Boinc is hard-coded to be 8hrs. That's what you're showing us above.
But the moment the task starts running the Rosetta Beta task's own internal runtime, mistakenly imo, is set to 3hrs and takes over.
Look at a running task to confirm that - as it progresses the remaining runtime veers toward 3hrs.
That's the <only> reason you don't miss deadlines.
Which is why I make the suggested changes to Target CPU runtime that I have.
Your tasks all run too short, you grab more tasks than you should, and if it wasn't for the large queue we currently have, which is an anomaly tbh, we'd all run out much quicker than we should.

---

Edit: In progress just updated to 162k with 4674 showing ready to send.
Edit 2: And validation backlog down to just 11k
Could everything really be fixed, or is it just a false dawn?

I'm thinking false dawn.
The Assimilators appeared to do OK early on as the Validation backlog was cleared. And the amount of work In progress climbed nicely as there were Tasks Ready to Send- for a while.
But now the In progress work appears to have plateaued and is dropping again as the Tasks Ready to Send is pretty much back to 0 again, and the assimilator backlog continues to grow, again.

I'm now agreeing with you.
In progress has dropped back to currently 133k, Assimilator backlog increasing again and ready to send dropping nearer to zero <sigh>
It's the hope that kills you...
Thanks for explaining Assimilators - I never really understood that. More the project's problem than ours, so I'll stop caring about that one and leave it to them.
Except to the extent that it indicates an ongoing problem everywhere.
Nice while it lasted (a few hours)

---

I can't report my finished and uploaded work
message: Rosetta@home 27.03.2025 12:19:56 (CET) Server error: feeder not running

Project status tells feeder is running

I have the exact same issue with 2 of my 3 computers (all running Linux).
Oddly enough, the third one is reporting its work without any problem.

All my three computers are behind the same router.
--
Bye, Lem

I can't report my finished and uploaded work
message: Rosetta@home 27.03.2025 12:19:56 (CET) Server error: feeder not running

Project status tells feeder is running

Me too. Running Linux.

---

'cmon guys of Rosetta, there are over 9 milions wus to crunch.
Open the floodgates and let if flow

---

9 mill? I don't see that. Be sure to subtract what is going to their AI system.
We just used up 1.33+ million tasks
With current total users with credit there is barely 9 tasks per user that were processed.


And for the system...well what else is new? seriously...SOS if you know what I mean and not the distress symbol.

9 mill? I don't see that

Home page.

Be sure to subtract what is going to their AI system.

Their AI system is internal, so, no, you can't see the queue.

---

Linux guys, I don't think you OS is the issue. If you can't get into the RAH feeder, which as far as I know sends out both OS type tasks, it's once your inside the feeder it figures out which OS is asking and will send work.
I am Windows and I get the same error as you. So it's not OS.

Linux guys, I don't think you OS is the issue. If you can't get into the RAH feeder, which as far as I know sends out both OS type tasks, it's once your inside the feeder it figures out which OS is asking and will send work.
I am Windows and I get the same error as you. So it's not OS.

Surely not. One of my machines is reporting and getting work flawlessly. It has the same OS, same version, same software, same everything of the others.
Even the connection is the same: the ok machine has a wired connection to one of the ko machines, and the latter is wirelessly connected to the router.

I don't know how to set the logs, and what to look for... Trying something, I see when connecting (I don't know if these logs are meaningful):

OK machine:

ven 28 mar 2025, 00:49:20 | | [work_fetch] No project chosen for work fetch
ven 28 mar 2025, 00:50:20 | Rosetta@home | rsc type 0 last MC limit time 345351.303849 total buf 371520.000000
ven 28 mar 2025, 00:50:20 | | [work_fetch] ------- start work fetch state -------
ven 28 mar 2025, 00:50:20 | | [work_fetch] target work buffer: 25920.00 + 345600.00 sec
ven 28 mar 2025, 00:50:20 | | [work_fetch] --- project states ---
ven 28 mar 2025, 00:50:20 | Rosetta@home | [work_fetch] REC 3611.800 prio -1.927 can request work
ven 28 mar 2025, 00:50:20 | | [work_fetch] --- state for CPU ---
ven 28 mar 2025, 00:50:20 | | [work_fetch] shortfall 66825.57 nidle 0.00 saturated 346899.60 busy 204796.13
ven 28 mar 2025, 00:50:20 | Rosetta@home | [work_fetch] share 1.000
ven 28 mar 2025, 00:50:20 | | [work_fetch] ------- end work fetch state -------
ven 28 mar 2025, 00:50:20 | Rosetta@home | choose_project: scanning
ven 28 mar 2025, 00:50:20 | Rosetta@home | can fetch CPU
ven 28 mar 2025, 00:50:20 | | [work_fetch] No project chosen for work fetch

KO machine:

ven 28 mar 2025, 00:44:17 | | [work_fetch] No project chosen for work fetch
ven 28 mar 2025, 00:45:18 | Rosetta@home | rsc type 0 last MC limit time 73122.227706 total buf 302400.000000
ven 28 mar 2025, 00:45:18 | Rosetta@home | rsc type 1 last MC limit time 0.000000 total buf 302400.000000
ven 28 mar 2025, 00:45:18 | | [work_fetch] ------- start work fetch state -------
ven 28 mar 2025, 00:45:18 | | [work_fetch] target work buffer: 95040.00 + 207360.00 sec
ven 28 mar 2025, 00:45:18 | | [work_fetch] --- project states ---
ven 28 mar 2025, 00:45:18 | Rosetta@home | [work_fetch] REC 8430.172 prio -0.017 can't request work: scheduler RPC backoff (2573.28 sec)
ven 28 mar 2025, 00:45:18 | | [work_fetch] --- state for CPU ---
ven 28 mar 2025, 00:45:18 | | [work_fetch] shortfall 2598075.15 nidle 0.00 saturated 74184.51 busy 28873.15
ven 28 mar 2025, 00:45:18 | Rosetta@home | [work_fetch] share 0.000
ven 28 mar 2025, 00:45:18 | | [work_fetch] --- state for AMD/ATI GPU ---
ven 28 mar 2025, 00:45:18 | | [work_fetch] shortfall 302400.00 nidle 1.00 saturated 0.00 busy 0.00
ven 28 mar 2025, 00:45:18 | Rosetta@home | [work_fetch] share 0.000
ven 28 mar 2025, 00:45:18 | | [work_fetch] ------- end work fetch state -------
ven 28 mar 2025, 00:45:18 | Rosetta@home | choose_project: scanning
ven 28 mar 2025, 00:45:18 | Rosetta@home | skip: scheduler RPC backoff
ven 28 mar 2025, 00:45:18 | | [work_fetch] No project chosen for work fetch

I have bolded some differences.

Please HELP!
--
Bye, Lem

Linux guys, I don't think you OS is the issue. If you can't get into the RAH feeder, which as far as I know sends out both OS type tasks, it's once your inside the feeder it figures out which OS is asking and will send work.
I am Windows and I get the same error as you. So it's not OS.

I didn't understand the report earlier as I couldn't see the issue on my main PC (W10) or my laptop (W11).
Then today I couldn't see it at work either (W10).

But I've just returned to where I stay in London and the PC I keep here (W10) has been reporting it for 17hrs.
I don't understand why but finally I'm seeing what some of you guys have been reporting.
Very odd. No idea what the solution is, but I'm going to do a reboot now after a windows update (clue?)

---

And:

Ok machine:

ven 28 mar 2025, 01:11:45 | Rosetta@home | update requested by user
ven 28 mar 2025, 01:11:48 | Rosetta@home | Sending scheduler request: Requested by user.
ven 28 mar 2025, 01:11:48 | Rosetta@home | Requesting new tasks for CPU
ven 28 mar 2025, 01:11:50 | Rosetta@home | Scheduler request completed: got 1 new tasks
ven 28 mar 2025, 01:11:50 | Rosetta@home | Project requested delay of 31 seconds
ven 28 mar 2025, 01:11:52 | Rosetta@home | Started download of 13mrredo_13_hallucinated_97_232.zip
ven 28 mar 2025, 01:11:52 | Rosetta@home | Started download of 13mrredo_13_hallucinated_97_232.flags
ven 28 mar 2025, 01:11:53 | Rosetta@home | Finished download of 13mrredo_13_hallucinated_97_232.zip (3886 bytes)
ven 28 mar 2025, 01:11:53 | Rosetta@home | Finished download of 13mrredo_13_hallucinated_97_232.flags (1018 bytes)

KO machine:

ven 28 mar 2025, 01:09:38 | Rosetta@home | update requested by user
ven 28 mar 2025, 01:09:40 | Rosetta@home | Sending scheduler request: Requested by user.
ven 28 mar 2025, 01:09:40 | Rosetta@home | Reporting 88 completed tasks
ven 28 mar 2025, 01:09:40 | Rosetta@home | Requesting new tasks for CPU and AMD/ATI GPU
ven 28 mar 2025, 01:09:42 | Rosetta@home | Scheduler request completed: got 0 new tasks
ven 28 mar 2025, 01:09:42 | Rosetta@home | Server error: feeder not running

--
Bye, Lem

Very odd. No idea what the solution is, but I'm going to do a reboot now after a windows update (clue?)

That didn't fix anything.
I'm now out of ideas - if anyone wants to suggest something, go right ahead. I'm all ears

---

I did disable IPv6 from Win10 and Linux hosts and all tasks were reported and no "feeder not running" error. I didn't get any new tasks but maybe out of tasks?

Try to disable IPv6, see if that helps.

I did disable IPv6 from Win10 and Linux hosts and all tasks were reported and no "feeder not running" error. I didn't get any new tasks but maybe out of tasks?

Try to disable IPv6, see if that helps.

We suspect there are issues with the bwsrv1 host, which is responsible for the Feeder (along with other processes).
It's just the luck of the draw when you request work if you will get any or not, as most of the time there is no work ready to Send (19:20 to 22:30 UTC yesterday there were a few thousand ready to send, and 06:00 to 07:00UTC today there were a few thousand ready to send. Othe than those times, it's between 6 and zero ready to send).

---

Grant
Darwin NT

Linux guys, I don't think you OS is the issue. If you can't get into the RAH feeder, which as far as I know sends out both OS type tasks, it's once your inside the feeder it figures out which OS is asking and will send work.
I am Windows and I get the same error as you. So it's not OS.

I didn't understand the report earlier as I couldn't see the issue on my main PC (W10) or my laptop (W11).
Then today I couldn't see it at work either (W10).

But I've just returned to where I stay in London and the PC I keep here (W10) has been reporting it for 17hrs.
I don't understand why but finally I'm seeing what some of you guys have been reporting.
Very odd. No idea what the solution is, but I'm going to do a reboot now after a windows update (clue?)

Sid - its inside Baker Labs system. I have been getting feeder errors for a few days now. Not surprising given how they kind of orphaned this project.

Grant has some more detailed information in this thread https://boinc.bakerlab.org/rosetta/forum_thread.php?id=6893&postid=112315

Times shown at GMT+1 or CET (Central European Time)

3/28/2025 8:57:05 AM | Rosetta@home | update requested by user
3/28/2025 8:57:05 AM | Rosetta@home | Sending scheduler request: Requested by user.
3/28/2025 8:57:05 AM | Rosetta@home | Reporting 5 completed tasks
3/28/2025 8:57:05 AM | Rosetta@home | Not requesting tasks: don't need (CPU: ; NVIDIA GPU: )
3/28/2025 8:57:07 AM | Rosetta@home | Scheduler request completed
3/28/2025 8:57:07 AM | Rosetta@home | Server error: feeder not running
3/28/2025 8:57:07 AM | Rosetta@home | Project requested delay of 3600 seconds

I did disable IPv6 from Win10 and Linux hosts and all tasks were reported and no "feeder not running" error. I didn't get any new tasks but maybe out of tasks?

Try to disable IPv6, see if that helps.

Thanks a lot! It worked.

And that is obviously the difference that I forgot between my systems, too. The one working was configured to use just IPv4!
Thanks again.
--
Bye, Lem