7/21/2005 1:20:24 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
7/21/2005 1:20:24 PM|SETI@home|Requesting 0 seconds of work, returning 0 results
7/21/2005 1:20:25 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

I'm about to run out of work units, after finally successfully uploading all but the current work unit. Is this a server-side problem?

---

I love your silences, they are like mine.
Radio News America

I have also finnaly been able to upload all work done but now I have no work left at all to do and it will not download any further work, What is going on ?

---

Be proud! Be a Steam Roller driver!

"Requesting 0 seconds" might be the uptime problem.

Stop BOINC and check your client_state.xml (with Notepad or so)

In the section "time_stats" you will find the 3 entries

on_frac, connected_frac and active_frac

If their values are way less than 1, set them all to 0.99 or so


The server seems to be low on (but not out of) work units at the moment but your client didn't request work.

So it's either this uptime thing or a client setting, like "connect to network every xxx days" set to 0 or you told the project to run empty.

Requesting 0 seconds of work can be caused by:

A host that has too much work to handle.

A project that has enough work and a host that has enough to get by.

A project that has used more than its share of the CPU time recently, and needs to wait for a bit to download some more.

Since the second case is not true (you claim to have no S@H work on hand) it must be one of the other two cases.

---

BOINC WIKI

This must be new in 4.4x I guess? My 4.19 tries to have at least one WU for each project in the cache.

John, you must be right, Coolavin's PC downloaded 7 Einstein WUs within the past 2 days.

So it will download SETI WUs again when the SETI project on the PC has a deficit in time shares.