Cant upload completed work... Server error: feeder not running

Rosetta@home 12/21/2025 18:10:03 update requested by user
Rosetta@home 12/21/2025 18:10:04 Sending scheduler request: Requested by user.
Rosetta@home 12/21/2025 18:10:04 Reporting 1 completed tasks
Rosetta@home 12/21/2025 18:10:04 Not requesting tasks: don't need ()
Rosetta@home 12/21/2025 18:10:06 Scheduler request completed
Rosetta@home 12/21/2025 18:10:06 Server error: feeder not running
Rosetta@home 12/21/2025 18:10:06 Project requested delay of 3600 seconds

As of 21 Dec 2025, 20:02:27 UTC [ Scheduler running ]
Total queued jobs: 325,343

We've got a fresh boost!

And now up to 574k - looks like an extra 500k to the 250k we got the previous day
Christmas has come early, which is good as I'm struggling to make space clearing out WCG tasks on my laptop to grab a decent share for Rosetta

---

Cant upload completed work... Server error: feeder not running

Rosetta@home 12/21/2025 18:10:03 update requested by user
Rosetta@home 12/21/2025 18:10:04 Sending scheduler request: Requested by user.
Rosetta@home 12/21/2025 18:10:04 Reporting 1 completed tasks
Rosetta@home 12/21/2025 18:10:04 Not requesting tasks: don't need ()
Rosetta@home 12/21/2025 18:10:06 Scheduler request completed
Rosetta@home 12/21/2025 18:10:06 Server error: feeder not running
Rosetta@home 12/21/2025 18:10:06 Project requested delay of 3600 seconds

No sign of upload issues there- that's the symptom for IPv6 issues, that the hosts file entry deals with.

---

Grant
Darwin NT

As of 21 Dec 2025, 20:02:27 UTC [ Scheduler running ]
Total queued jobs: 325,343

We've got a fresh boost!

And now up to 574k - looks like an extra 500k to the 250k we got the previous day
Christmas has come early, which is good as I'm struggling to make space clearing out WCG tasks on my laptop to grab a decent share for Rosetta

Now 854k queued and all my WCG and SiDock cleared out, so 100% Rosetta on the machines I'm close to
I'll get to my remote two tomorrow
I can't ask a lot more than that - fingers crossed new tasks continue to pile up

---

Seems like we passed the peak, but we have a nice reserve of tasks for Christmas. In the meantime, I added a brand new Ryzen 7 5825U to by BOINC farm yesterday as well as a Motorola g32 which is doing surprisingly well when it actually uses the CPU.

---

Cant upload completed work... Server error: feeder not running

Rosetta@home 12/21/2025 18:10:03 update requested by user
Rosetta@home 12/21/2025 18:10:04 Sending scheduler request: Requested by user.
Rosetta@home 12/21/2025 18:10:04 Reporting 1 completed tasks
Rosetta@home 12/21/2025 18:10:04 Not requesting tasks: don't need ()
Rosetta@home 12/21/2025 18:10:06 Scheduler request completed
Rosetta@home 12/21/2025 18:10:06 Server error: feeder not running
Rosetta@home 12/21/2025 18:10:06 Project requested delay of 3600 seconds

No sign of upload issues there- that's the symptom for IPv6 issues, that the hosts file entry deals with.

My internet provider doesn't handle IPv6 properly, How can I get the IPv4 address?

Add the following two lines to the end of your hosts file.

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

The file might be *hidden, system and/ or read only* and is located as noted below (Change all the / to ).

C:/Windows/System32/Drivers/etc/hosts

You might need to disable anti-virus and/or anti-malware software (Norton's, Microsoft's built-in Anti-virus; etc; temporarily to edit it.

*To change the file attributes, open a "DOS prompt" command line "C:>" and type (without the quotes)
"Attrib -h -s -r C:/Windows/System32/Drivers/etc/hosts"

Now to edit the file.. At the same command prompt type (without the quotes)
"Notepad C:/Windows/System32/Drivers/etc/hosts"

Or Use a text editor such as NOTEPAD.exe to edit the file, save it with "all extensions *.*" as plain text.

As of 21 Dec 2025, 20:02:27 UTC [ Scheduler running ]
Total queued jobs: 325,343

We've got a fresh boost!

And now up to 574k - looks like an extra 500k to the 250k we got the previous day
Christmas has come early, which is good as I'm struggling to make space clearing out WCG tasks on my laptop to grab a decent share for Rosetta

Now 854k queued and all my WCG and SiDock cleared out, so 100% Rosetta on the machines I'm close to
I'll get to my remote two tomorrow
I can't ask a lot more than that - fingers crossed new tasks continue to pile up

All PCs going full tilt on Rosetta now, but it's unlikely we'll see any more tasks over the holiday period.
I'd expect us to run out some time over the weekend

---

Based on the speed at which tasks are disappearing here, we have about 48 hours worth of supply plus whatever everyone has cached (1-2 days realistically). Oh and any potential resends of timeouts. All in all, I expect to crunch mostly Rosetta throuth the 29th, possibly on the 30th as well. Then it's back to SiDock, WCG and LHC.

On the other hand, I got 1-2 non-beta tasks dated 25th so there might be a very small non-beta trickle even after the beta batch runs out.

---

Based on the speed at which tasks are disappearing here, we have about 48 hours worth of supply plus whatever everyone has cached (1-2 days realistically). Oh and any potential resends of timeouts. All in all, I expect to crunch mostly Rosetta throuth the 29th, possibly on the 30th as well. Then it's back to SiDock, WCG and LHC.

On the other hand, I got 1-2 non-beta tasks dated 25th so there might be a very small non-beta trickle even after the beta batch runs out.

Likely some non-zero number of non-Beta tasks, but aside from these bigger batches being put out, it was so few that I don't think I had any arrive here
My guess is the last tasks to download will be ~ 00:00 UTC Saturday nightSunday morning, then it's down to the size of the cache people hold

---

My bet is ~08:00 UTC on Sunday. We shall soon see.

---

My bet is ~08:00 UTC on Sunday. We shall soon see.

14hrs after my post, I'm more inclined to agree with you than with what I wrote.
That's good news.

---

I've been following the big magic number for a few days and it seems that the "consumption" is around 23-25k tasks every 4 hours, with very low variations, so theoretically every 6k tasks in the queue should last for an hour.

---

As of 27 Dec 2025, 20:04:03 UTC [ Scheduler running ]
                                   Total queued jobs:  75,217
                                  Successes last 24h: 140,990

So around 12 hrs worth left.

---

Grant
Darwin NT

As of 27 Dec 2025, 20:04:03 UTC [ Scheduler running ]
                                   Total queued jobs:  75,217
                                  Successes last 24h: 140,990

So around 12 hrs worth left

As of 28 Dec 2025, 0:03:31 UTC [ Scheduler running ]
Total queued jobs: 50,523

It is remarkably consistent, isn't it! I hadn't appreciated that before.
I've had the misfortune today to have to do a 220-mile round-trip for work, one advantage of which was adding an extra day of cache to my 2 remote PCs, so I've greedily added to my share of the remainder.
I'm not sorry...

---

Got my last new task at 09:22 UTC, only some resends after that moment.

I still have over 600 tasks cached (630-650 was the normal interval while there was a constant supply) but I don't expect resends to be able to hold the line for long. Was a nice run though, let's hope there will be more in the new year. Until then I'm moving over to SiDock and WCG as secondary.

---

What a nice surprise: there was a batch of non-beta tasks dropped about an hour ago. Managed to restock some of my rigs that were soon going to run out of all Rosetta work.

---

What a nice surprise: there was a batch of non-beta tasks dropped about an hour ago. Managed to restock some of my rigs that were soon going to run out of all Rosetta work.

---

Got my last new task at 09:22 UTC, only some resends after that moment.

I still have over 600 tasks cached (630-650 was the normal interval while there was a constant supply) but I don't expect resends to be able to hold the line for long. Was a nice run though, let's hope there will be more in the new year. Until then I'm moving over to SiDock and WCG as secondary.

Yes, just a little longer than expected.
The number of tasks you have seems like a lot, so I took a look to see you have several PCs running, but the majority are running tasks for barely more than 2hrs, for which you're getting very little credit, while using up tasks faster than expected.
I don't mean to drag you into the discussion we're having elsewhere, but it will make an enormous difference to how long batches of tasks last if you change your Rosetta Target CPU runtime explicitly to 8 hours here, matching the time Boinc schedules unstarted tasks for, and limit your cache to 2-2.5 days at most to ensure they complete within their deadlines.
The limited number of tasks we get at a time will last a lot longer and can be shared out among more users, while you'll see a massive credit boost per task and a smaller credit boost overall.

---

Got my last new task at 09:22 UTC, only some resends after that moment.

I still have over 600 tasks cached (630-650 was the normal interval while there was a constant supply) but I don't expect resends to be able to hold the line for long. Was a nice run though, let's hope there will be more in the new year. Until then I'm moving over to SiDock and WCG as secondary.

Yes, just a little longer than expected.
The number of tasks you have seems like a lot, so I took a look to see you have several PCs running, but the majority are running tasks for barely more than 2hrs, for which you're getting very little credit, while using up tasks faster than expected.
I don't mean to drag you into the discussion we're having elsewhere, but it will make an enormous difference to how long batches of tasks last if you change your Rosetta Target CPU runtime explicitly to 8 hours here, matching the time Boinc schedules unstarted tasks for, and limit your cache to 2-2.5 days at most to ensure they complete within their deadlines.
The limited number of tasks we get at a time will last a lot longer and can be shared out among more users, while you'll see a massive credit boost per task and a smaller credit boost overall.

Right now I have set all PCs to run tasks for 4 hours because some PCs behave unpredictably and may actually run tasks for longer (mainly the i7-1165G7 and, somewhat surprisingly, the Ultra 5 125H). The Ryzen 5285Us should be fine running regular 8 hour tasks (with a somewhat reduced cache for safety), but the first two would probably need an even smaller cache, under 2 days. I will try messing around with the setting but until the next large wave of work I won't really be able to stress test the setup.

I did read parts of the discussion you mentioned but will admit that I also didn't put in the effort to properly read and assimilate everything.

Either way, thanks for the tip! I'm making changes right now.

---