The feeder is shown as running but is presumably not working correctly.

For all we know it is- but until there is work to actually send out it doesn't matter if it is or isn't working.
rah_make_work1 also shows as working, but as there is no work being produced you can be sure that isn't really the case.

---

Grant
Darwin NT

Where do you see lots of jobs in queue?

Home page of Rosetta:

Total queued jobs: 11,148,825

On server status page:

Tasks ready to send: 0

---

The feeder is shown as running but is presumably not working correctly.

For all we know it is- but until there is work to actually send out it doesn't matter if it is or isn't working.
rah_make_work1 also shows as working, but as there is no work being produced you can be sure that isn't really the case.

OK, I’d assumed that the feeder was the unit that fed work from the output of the generator to the ready to be sent queue.

As the saying goes, assume makes an ass of u and me

That's part of he problem.
It shows it's working, but nothing is happening.
It would be easier to see if all the information was on the one page, but it isn't.

There are some daemons to queue jobs, like

./bin/xadd

sudo a2enmod cgi

or

/bin/update_versions

and others
Maybe there is some problems in these steps....

---

For all we know it is- but until there is work to actually send out it doesn't matter if it is or isn't working.

./bin/stop

./bin/start

With these 2 commands you can restart ALL daemons. 5 seconds of work and you can see if the problem is here...

---

it would also help if the server status was updated more often than every few hours- and that's when it is being updated

AFAICT it is pretty regular: the front page gets updated every four hours (around 4, 8 and 12 Pacific time), and on the status page the Server status and Computing status get updated every ≈62 minutes (separately, at different offsets).

For all we know it is- but until there is work to actually send out it doesn't matter if it is or isn't working.

./bin/stop

./bin/start

With these 2 commands you can restart ALL daemons. 5 seconds of work and you can see if the problem is here...

But you are assuming someone is there, or at home, to do the work...there isn't! They do not work on weekends unless they have in lab stuff to do or Server updates or something that can't be done during the week. They take the weekends off because for them it's a 9 to 5 5 day a week job not a hobby as it is for us, sure they enjoy their work but so did you when you were working, but did YOU go in on weekends to do stuff knowing you weren't going to get paid for it and knowing if things got worse no one was there to help fix it. I know I didn't, I took every day off to it's fullest and spent it with my family and friends and then come the day I had to go back to work I started worrying about work stuff again. At one of my jobs they even had it set up so that most people could NOT go in to work because they disabled the access badges on weekends, you couldn't even get in the front door let alone do any work. In fact when I had to work late one night they had to have a Security Guard babysit me so I could get to the different places I needed to be as his badge worked and mine didn't.

But you are assuming someone is there, or at home, to do the work...there isn't! They do not work on weekends unless they have in lab stuff to do or Server updates or something that can't be done during the week. They take the weekends off because for them it's a 9 to 5 5 day a week job not a hobby as it is for us, sure they enjoy their work but so did you when you were working, but did YOU go in on weekends to do stuff knowing you weren't going to get paid for it and knowing if things got worse no one was there to help fix it.

Ehi, ehi, i'm NOT angry with admins. I KNOW they have their vacations and it's right.
Mine are only considerations about Boinc server and his daemons.
As i wrote some days ago, i hope these days someone can have time to see problems and not wait until the middle of January....

---

12/28/2020 12:07:54 AM | Rosetta@home | Sending scheduler request: To fetch work.
12/28/2020 12:07:54 AM | Rosetta@home | Requesting new tasks for CPU
12/28/2020 12:07:56 AM | Rosetta@home | Scheduler request completed: got 0 new tasks
12/28/2020 12:07:56 AM | Rosetta@home | No tasks sent
12/28/2020 12:07:56 AM | Rosetta@home | Project requested delay of 31 seconds
12/28/2020 9:37:22 AM | | Suspending computation - CPU is busy
12/28/2020 9:37:32 AM | | Resuming computation
12/28/2020 2:32:40 PM | Rosetta@home | Sending scheduler request: To fetch work.
12/28/2020 2:32:40 PM | Rosetta@home | Requesting new tasks for CPU
12/28/2020 2:32:42 PM | Rosetta@home | Scheduler request completed: got 0 new tasks
12/28/2020 2:32:42 PM | Rosetta@home | No tasks sent
12/28/2020 2:32:42 PM | Rosetta@home | Project requested delay of 31 seconds
12/28/2020 2:49:55 PM | | Suspending computation - CPU is busy
12/28/2020 2:50:05 PM | | Resuming computation
what gives?

12/28/2020 2:32:42 PM | Rosetta@home | Scheduler request completed: got 0 new tasks

what gives?

There is a problem on the server such that it is not sending out any new tasks to anybody. It is probably temporary, but might not be rectified until after the holiday.

Still 0

12/28/2020 2:32:42 PM | Rosetta@home | Scheduler request completed: got 0 new tasks

what gives?

There is a problem on the server such that it is not sending out any new tasks to anybody. It is probably temporary, but might not be rectified until after the holiday.

Still 0

Still holiday

Still 0

Still holiday

Maybe not even until after the 1st ie the 4th since the 1st is a Friday. Lots of other fish in the sea, catch what you can elsewhere and keep checking back here so you can get some when they have some.

Still 0

Still holiday

Maybe not even until after the 1st ie the 4th since the 1st is a Friday. Lots of other fish in the sea, catch what you can elsewhere and keep checking back here so you can get some when they have some.

Running a ton of other projects so no loss of crunch time, just rosie time.

Really?

Yes, as you've amply demonstrated.

I returned because I did a manual update, out of random hope, and managed to grab 3 tasks on my laptop, so tried on my PC and found 23 tasks. A 2nd attempted update on each was unsuccessful though.
I wondered if anything had changed - apparently not. Maybe just timed out tasks, re-issued. Oh well...

This comment still applies

The week of Monday 4th January is favourite now - and not the beginning of that week either

Until then, you might consider pondering the difference between being plain, honest and accurate and being rude
And whether receiving news you'd prefer to be different, even if it's plain, honest and accurate, constitutes being pro- or anti- "community"

Don't mind me. I can scroll past a page of repetitive, impotent guff as easily as the next person. Doesn't change when tasks will come down - at which point the apparent "community" will be satisfied and united again. Lol

---

It looks like a few items need to be added to the server status page to help with discussions like this one:

Tasks sent in the last 24 hours
Number of computer requests for tasks in the last 24 hours
Which server program or programs converts queued tasks to tasks ready to send
Amount of disk space that can hold more tasks ready to send once they are created

Remind me what the issue is again? Because I couldn't see one at all.

Actually, the issue is a bit obscure because I have not stated it clearly yet. It is not the day-to-day operations that I am concerned with. We can change easily.
But long term, I am interested in using my computer resources efficiently. So if Rosetta can do twice (or ten times) the work using AI, then they really don't need me so much. I can put my PC resources elsewhere. And if I know when that change is coming, I can do it in a more timely manner.

You have multiple PCs, have set up multiple alternative projects and Boinc uses "debts" to determine if some projects run because others can't, for any reason, the shortfall gets made up over time. Why do feel you need to manually intervene beyond that?

Since informing me does not necessarily do Rosetta much good, they probably don't feel much reason to keep me informed.
But for that matter, I don't need to make any assumptions about the work continuing in the normal manner either. I can make worst-case assumptions if I want to.

You can, but only if you think the decisions you already made were wrong in some way.

I can imagine, if in future any project stops issuing tasks permanently, you might take their resource share down to zero perhaps. An amendment that takes maybe 30 seconds.
I wouldn't give it a moment's thought until after it happened. As you rightly said at the start, we can change easily.
A complete non-issue.

---

I just told you what the issue is.

---

I just told you what the issue is.

To the extent you did (?!) the only "cost" would be you'd run a bit more of projects you've already decided to run, you'll spot any change quickly enough if it ever happens, which there's no indication of, and it'll take 30-seconds to change.
You (and I) have already wasted more time typing about something that doesn't exist than it would ever take to "fix" this non-existent and imaginary thing.
Way to go...

Meanwhile, after completing the few rb tasks that snuck through to me yesterday, I took a look at In Progress tasks to see if anything had changed and instead of going down they increased from a paltry 20k to a marginally less paltry 30k. It seems some work is going through, while the bulk isn't shifting at all, which makes me think it's not a blanket stop on work being issued but something a lot weirder, though I have no idea what.
We may find out next week.
Or not, as no-one will be interested once sufficient tasks come through again

---

Looks like there is a small number of new Robetta tasks going out