On all projects I know (OK, not that many, but anyway), if the server does not send any WUs to the requesting machine an additional message with the reason for that is sent in the scheduler reply, for example "project has no tasks available" or "This computer has reached a limit on tasks in progress" or whatever the reason is, so the user does not need to spend lots of time figuring out by him self why he don't get any tasks.

Currently the message "Feeder not running." would make it unnecessary for the users to check the server status page just to find out, that the feeder is not running. The current message is completely useless, we know that we didn't get any tasks from the previous line: "Scheduler request completed: got 0 new tasks".

---

.

It's probably because they are running an older version of BOINC server, which I believe is no easy task to upgrade. I'm sure they'll restart it when they come in for work this morning. It's still early on the west coast.

---

Since our recent filesystem upgrade, our work unit feeder has been offline. We are currently working on fixing the issue.