I upgraded my BOINC client to 4.05. Both of my systems attempted to download the SETI 4.02 client. Both failed:

2004-08-29 15:56:11 [SETI@home] Giving up on download of setiathome_4.02_i686-pc-linux-gnu: File downloaded was not the correct file or was garbage from bad URL
md5_file: can't open projects/setiathome.berkeley.edu/setiathome_4.02_i686-pc-linux-gnu
md5_file: No such file or directory
error: verify_file: md5_file error -108
2004-08-29 15:56:11 [SETI@home] verify_downloaded_file(): projects/setiathome.berkeley.edu/setiathome_4.02_i686-pc-linux-gnu: internal error
2004-08-29 15:56:11 [SETI@home] Checksum or signature error for setiathome_4.02_i686-pc-linux-gnu


The site lists the version, but doesn't provide a download, I imagine for security reasons or something (although the sources are there... whatever).

The client noticed that the download failed, but hasn't made any attempt to re-download the SETI client. It got all the WUs it wanted, and will now never finish them, so it won't notice it needs a client, right?

So... now what?

OK, so, in desperation, I went hunting for the #)$)@##! SETI "core."

It apparently lives here:

http://setiboincdata.ssl.berkeley.edu/sah/download_fanout/setiathome_4.02_i686-pc-linux-gnu


Alright. So you could try to download it. When the BOINC client tried (in vain) to download it, it looked like it was planning on putting it in the projects/setiathome.berkeley.edu directory under my boinc directory. Go wget it:

lmm@saopaolo:~/boinc/projects/setiathome.berkeley.edu$ wget http://setiboincdata.ssl.berkeley.edu/sah/download_fanout/setiathome_4.02_i686-pc-linux-gnu

--21:16:34-- http://setiboincdata.ssl.berkeley.edu/sah/download_fanout/setiathome_4.02_i686-pc-linux-gnu
=> `setiathome_4.02_i686-pc-linux-gnu'
Resolving setiboincdata.ssl.berkeley.edu... 66.28.250.125
Connecting to setiboincdata.ssl.berkeley.edu[66.28.250.125]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7,375,729 [application/octet-stream]

OK. Got it. But the boinc client doesn't find it when I restart it. GAHHHHHH!!!!

Anyone else (assuming anyone ever reads these posts) got an idea?

I got lots of these errors in the early hours of 4.05. I found that if I restarted the program it would re-attempt the failed download next time it contacted Berkeley.

Fetching it yourself wont help on its own because you need the appropriate data in client_state.xml as well.

Thanks to Phil for his help!

I finally got it to download by repeatedly resetting the client. Before you do this, set your cache values to something low, like 0.5 to 0.6, to avoid having the core module download slowed down by WU downloads (and I NEVER thought I'd be worried about THAT! :)

I have 2 similar Althon W/S. One is merrily crunching away. The other one won't start due to an error -144, see this thread:

http://setiweb.ssl.berkeley.edu/sah/forum_thread.php?id=3516