Why is it so hard to get SETI BOINC work?

[earthman]

It seems like there's hardly ever any work available.

 

[Rattledagger]

There's been ocassional outages for various reasons, but it shouldn't currently be any problem getting enough wu to crunch.

Are you getting any error-messages, like too old client if you're not running v4.13, or "daily quota exceeded" or "too recent" or "not enough disk space".
Maybe a firewall-problem, can you access http://setiboincdata.ssl.berkeley.edu/boinc_alpha/ and http://setiweb.ssl.berkeley.edu/
One user over at BBR had problems one computer didn't manage connecting, but re-starting his router apparently fixed this problem...

 

[earthman]

No, it doesnt' seem to be a connection problem, I just get the message about no work available alot.

 

[Rattledagger]

Most times you'll get a reason listed of why "no work available". This reason is listed in the lines above, so are you getting "out of work" or something else?

 

[zaph]

9 PC's here, and all have full cache's.
Do you have your boinc preferences set at the website to keep multiple days worth of work?

I have mine set to keep between 7 and 10 days worth on each box.
That way, if there is a short outage for maintainence/upgrades, you have more than enough to get you through.

 

[Rattledagger]

You can only supply one preference now, "Connect to network about every N days ", and this should give you between N & 2N days of work, so recommended not to set this higher than 5 due to deadline.

 

[earthman]

2004-11-14 22:19:14 [SETI@home] No work from project
2004-11-14 22:19:14 [SETI@home] Deferring communication with project for 1 days, 0 hours, 0 minutes, and 0 seconds
2004-11-14 23:19:14 [SETI@home] Deferring communication with project for 23 hours, 0 minutes, and 0 seconds
2004-11-15 00:19:14 [SETI@home] Deferring communication with project for 22 hours, 0 minutes, and 0 seconds
2004-11-15 01:19:14 [SETI@home] Deferring communication with project for 21 hours, 0 minutes, and 0 seconds
2004-11-15 02:19:14 [SETI@home] Deferring communication with project for 20 hours, 0 minutes, and 0 seconds
2004-11-15 03:19:14 [SETI@home] Deferring communication with project for 19 hours, 0 minutes, and 0 seconds
2004-11-15 04:19:14 [SETI@home] Deferring communication with project for 18 hours, 0 minutes, and 0 seconds
2004-11-15 05:19:14 [SETI@home] Deferring communication with project for 17 hours, 0 minutes, and 0 seconds
2004-11-15 06:19:14 [SETI@home] Deferring communication with project for 16 hours, 0 minutes, and 0 seconds
2004-11-15 07:19:14 [SETI@home] Deferring communication with project for 15 hours, 0 minutes, and 0 seconds

 

[Rattledagger]

The reason is listed BEFORE the "no work from project"-message, but seeing you're deferred 24 hours this indicates you're trying to use a too old client, and will therefore never get any more work before upgrading.

To upgrade, download the new v4.13 from http://boinc.berkeley.edu/download.php (don't download v4.55)
Stop the old version, and install the new. 🙂

 

[earthman]

It was version 4.13, however, it seems to have work now.