Event log today:
5/29/2025 2:10:57 PM | Rosetta@home | Server error: feeder not running
5/29/2025 2:10:57 PM | Rosetta@home | Project requested delay of 3600 seconds

Steve, take a look at kotenok2000's message above
The lines I've extracted from your log tell me the change you've made in your hosts file isn't being read by your PC.
"hosts" can't have any extension at all, such as hosts.txt. hosts.doc, hosts.bak or hosts.old
It has to simply be "hosts"

When you showed us the hosts edit you made, it looked good to me, but if the filename is wrong, that's the only explanation I can see for "Server error: feeder not running" still being reported in your log file.
That's the line we have to get rid of.

---

Event log today:
5/29/2025 2:10:57 PM | Rosetta@home | Server error: feeder not running
5/29/2025 2:10:57 PM | Rosetta@home | Project requested delay of 3600 seconds

Steve, take a look at kotenok2000's message above
The lines I've extracted from your log tell me the change you've made in your hosts file isn't being read by your PC.
"hosts" can't have any extension at all, such as hosts.txt. hosts.doc, hosts.bak or hosts.old
It has to simply be "hosts"

When you showed us the hosts edit you made, it looked good to me, but if the filename is wrong, that's the only explanation I can see for "Server error: feeder not running" still being reported in your log file.
That's the line we have to get rid of.

Sid, Tom, et al:

Guess what??

Today I initially got two Rosetta tasks!!

Then a few hour later, lo and behold, I got NINE tasks!

All due by June 3, but running between 183 -187 degrees F. My cut-off temp is 190 F.

So it looks like things have returned to something resembling normality.

We'll see how long it last.

I want to express my sincere thanks to you both and all the others who helped me get through these tribulations.

S. Gaber
Oldsmar, FL

Tom:

You said "5/28/2025 9:48:51 AM | Rosetta@home | Not requesting tasks: don't need (CPU: ; AMD/ATI GPU: )
Usually this means you have other projects that have filled your cache up. So you might want to No New Task all your other CPU projects until you start getting some Rosetta downloads."

I have paused other projects or requested no new tasks for a day or two. And still didn't get any Rosetta tasks. That's why I said I was ready to give up on Rosetta.

Event log today:
5/29/2025 2:10:43 PM | Asteroids@home | project suspended by user
5/29/2025 2:10:47 PM | Einstein@Home | project suspended by user
5/29/2025 2:10:48 PM | Universe@Home | Sending scheduler request: To fetch work.
5/29/2025 2:10:48 PM | Universe@Home | Requesting new tasks for CPU
5/29/2025 2:10:49 PM | Milkyway@home | project suspended by user
5/29/2025 2:10:50 PM | Universe@Home | Scheduler request completed: got 0 new tasks
5/29/2025 2:10:50 PM | Universe@Home | Project has no tasks available
5/29/2025 2:10:50 PM | Universe@Home | Project requested delay of 11 seconds
5/29/2025 2:10:53 PM | World Community Grid | project suspended by user
5/29/2025 2:10:55 PM | Rosetta@home | Sending scheduler request: To fetch work.
5/29/2025 2:10:55 PM | Rosetta@home | Requesting new tasks for CPU and AMD/ATI GPU
5/29/2025 2:10:57 PM | Rosetta@home | Scheduler request completed: got 0 new tasks
5/29/2025 2:10:57 PM | Rosetta@home | Server error: feeder not running
5/29/2025 2:10:57 PM | Rosetta@home | Project requested delay of 3600 seconds
5/29/2025 2:10:59 PM | Rosetta@home | update requested by user
5/29/2025 2:11:02 PM | Rosetta@home | Sending scheduler request: Requested by user.
5/29/2025 2:11:02 PM | Rosetta@home | Requesting new tasks for CPU and AMD/ATI GPU
5/29/2025 2:11:03 PM | Rosetta@home | Scheduler request completed: got 0 new tasks
5/29/2025 2:11:03 PM | Rosetta@home | Server error: feeder not running
5/29/2025 2:11:03 PM | Rosetta@home | Project requested delay of 3600 seconds

S. Gaber
Oldsmar, FL

I have only been able to get rid of that message by NNT tasks on other projects for extended periods so your total tasks in cache goes down significantly. A day or two may not be long enough.

---

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

Sid,

Saying that, and poking my nose in where it isn't wanted yet again, is your cache of Einstein tasks too high?
I note that several tasks were cancelled before starting, despite a 2-week deadline.
Or was that period a while ago, and have you already resolved it?

The deadline I am seeing is currently June 2. So I believe I am getting 3 day deadlines.

===edit== And dropped the cpu tasks allowed for Rosetta (in the Pandora config file) to 200.

For a while, a cache under 300 seemed to not be producing expired tasks.
And I don't want to have tasks being expired.

The problem is to keep more than 120 processing at once while not taking more than 3 days (I think) to get them done.

Your previous calculations seem to think that 12 hour tasks should manage to do that for a cache of 300 or under. 3 x 120 = 360.

I started up my polling script when I hit some 90 Rosetta tasks processing and my backup cpu project started downloading tasks.

<scratch head>

:)

===edit==
I looked at the list of canceled by server tasks. They were all canceled the same day they were sent. So they were not even getting to the 3 day deadline and being canceled.

---

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