Installation of BOINC 5.2.13 went fine, as far as I could tell. I configured with the account key given to me for transferring my seti@home classic account.

Since then, I've attached only the seti@home project and rebooted. It's been a few hours, but BOINC has so far failed to download any work units.

Below is a display since the last reboot, about 1/2 hour ago. The "MD5 check failed..." and the next 3 messages are red.

I am running Win2K w/ latest SP on a small home LAN with a hardware router. I am also running Norton Antivirus, but no software firewall.

Thanks for any help,

Ken




12/5/2005 11:22:12 AM||Starting BOINC client version 5.2.13 for windows_intelx86
12/5/2005 11:22:12 AM||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
12/5/2005 11:22:12 AM||Data directory: E:\\Program Files\\BOINC
12/5/2005 11:22:13 AM||Processor: 2 GenuineIntel x86 Family 6 Model 7 Stepping 3 601MHz
12/5/2005 11:22:13 AM||Memory: 1023.53 MB physical, 5.33 GB virtual
12/5/2005 11:22:13 AM||Disk: 10.07 GB total, 5.88 GB free
12/5/2005 11:22:13 AM|SETI@home|Computer ID: 1898599; location: home; project prefs: default
12/5/2005 11:22:13 AM||General prefs: from SETI@home (last modified 2005-12-05 05:54:09)
12/5/2005 11:22:13 AM||General prefs: no separate prefs for home; using your defaults
12/5/2005 11:22:14 AM||Remote control not allowed; using loopback address
12/5/2005 11:22:14 AM|SETI@home|Started download of 21mr05ab.11361.29408.484658.189
12/5/2005 11:22:49 AM|SETI@home|Temporarily failed download of 21mr05ab.11361.29408.484658.189: error 400
12/5/2005 11:22:49 AM|SETI@home|Backing off 1 minutes and 0 seconds on download of file 21mr05ab.11361.29408.484658.189
12/5/2005 11:23:49 AM|SETI@home|Started download of 21mr05ab.11361.29408.484658.189
12/5/2005 11:24:52 AM|SETI@home|Temporarily failed download of 21mr05ab.11361.29408.484658.189: error 400
12/5/2005 11:24:52 AM|SETI@home|Backing off 1 minutes and 0 seconds on download of file 21mr05ab.11361.29408.484658.189
12/5/2005 11:25:52 AM|SETI@home|Started download of 21mr05ab.11361.29408.484658.189
12/5/2005 11:26:27 AM|SETI@home|Temporarily failed download of 21mr05ab.11361.29408.484658.189: error 400
12/5/2005 11:26:27 AM|SETI@home|Backing off 1 minutes and 0 seconds on download of file 21mr05ab.11361.29408.484658.189
12/5/2005 11:27:27 AM|SETI@home|Started download of 21mr05ab.11361.29408.484658.189
12/5/2005 11:28:30 AM|SETI@home|Temporarily failed download of 21mr05ab.11361.29408.484658.189: error 400
12/5/2005 11:28:30 AM|SETI@home|Backing off 2 minutes and 20 seconds on download of file 21mr05ab.11361.29408.484658.189
12/5/2005 11:30:51 AM|SETI@home|Started download of 21mr05ab.11361.29408.484658.189
12/5/2005 11:31:55 AM|SETI@home|Temporarily failed download of 21mr05ab.11361.29408.484658.189: error 400
12/5/2005 11:31:55 AM|SETI@home|Backing off 6 minutes and 38 seconds on download of file 21mr05ab.11361.29408.484658.189
12/5/2005 11:36:05 AM|SETI@home|Started download of setiathome_4.18_windows_intelx86.pdb
12/5/2005 11:37:08 AM|SETI@home|Temporarily failed download of setiathome_4.18_windows_intelx86.pdb: error 400
12/5/2005 11:37:08 AM|SETI@home|Backing off 1 hours, 18 minutes, and 11 seconds on download of file setiathome_4.18_windows_intelx86.pdb
12/5/2005 11:38:34 AM|SETI@home|Started download of 21mr05ab.11361.29408.484658.189
12/5/2005 11:39:00 AM|SETI@home|Finished download of 21mr05ab.11361.29408.484658.189
12/5/2005 11:39:00 AM|SETI@home|Throughput 14501 bytes/sec
12/5/2005 11:39:01 AM|SETI@home|MD5 check failed for 21mr05ab.11361.29408.484658.189
12/5/2005 11:39:01 AM|SETI@home|expected ac49500be1bce48d931d6c7151dc25c6, got b08901ebfb038e005145be7f34b38d2e
12/5/2005 11:39:01 AM|SETI@home|Checksum or signature error for 21mr05ab.11361.29408.484658.189
12/5/2005 11:39:02 AM|SETI@home|Unrecoverable error for result 21mr05ab.11361.29408.484658.189_0 (WU download error: couldn't get input files:<file_xfer_error> <file_name>21mr05ab.11361.29408.484658.189</file_name> <error_code>-119</error_code> <error_message>MD5 check failed</error_message></file_xfer_error>)
12/5/2005 11:40:06 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
12/5/2005 11:40:06 AM|SETI@home|Reason: To fetch work
12/5/2005 11:40:06 AM|SETI@home|Requesting 17280 seconds of new work, and reporting 1 results
12/5/2005 11:40:11 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
12/5/2005 11:40:13 AM|SETI@home|Started download of 13au01aa.6597.23410.92334.0
12/5/2005 11:40:44 AM|SETI@home|Finished download of 13au01aa.6597.23410.92334.0
12/5/2005 11:40:44 AM|SETI@home|Throughput 12021 bytes/sec
12/5/2005 11:42:24 AM|SETI@home|Started download of 15oc03aa.1719.24002.361092.105
12/5/2005 11:43:02 AM|SETI@home|Temporarily failed download of 15oc03aa.1719.24002.361092.105: error 400
12/5/2005 11:43:02 AM|SETI@home|Backing off 2 hours, 8 minutes, and 9 seconds on download of file 15oc03aa.1719.24002.361092.105

---

I do believe that Berkeley has a server problem at this time...

---

BOINC Wiki

Yes, SETI is effectively totally down, partly due to network problems, then made worse by the crush of new users trying to connect. Even the web pages are incredibly slow to load, and uploading/downloading/attaching just isn't happening. This is where BOINC's ability to give time to other projects becomes very useful. I would hit "suspend" on SETI and just try it again in a couple of days. Meanwhile, there's Einstein, and Rosetta, and Predictor, and Climateprediction... :-)

---

Yes, SETI is effectively totally down, partly due to network problems, then made worse by the crush of new users trying to connect. Even the web pages are incredibly slow to load, and uploading/downloading/attaching just isn't happening. This is where BOINC's ability to give time to other projects becomes very useful. I would hit "suspend" on SETI and just try it again in a couple of days. Meanwhile, there's Einstein, and Rosetta, and Predictor, and Climateprediction... :-)

---

Yes, SETI is effectively totally down, partly due to network problems, then made worse by the crush of new users trying to connect. Even the web pages are incredibly slow to load, and uploading/downloading/attaching just isn't happening. This is where BOINC's ability to give time to other projects becomes very useful. I would hit "suspend" on SETI and just try it again in a couple of days. Meanwhile, there's Einstein, and Rosetta, and Predictor, and Climateprediction... :-)

I was about to suspend SETI when I spotted BOINC was downloading a new work unit, so perhaps it's up and running again.

---

I've heard the same, Jim, that the Seti server has been almost continuously overwhelmed, and that the situation is not likely to improve until after the migration from SetiClassic is completed.

(edit) @KenD, It sounds as it your download was interrupted numerous times, and eventually resulted in a corrupted datafile.

---

"The arc of history is long, but it bends toward Justice"

Installation of BOINC 5.2.13 went fine, as far as I could tell. I configured with the account key given to me for transferring my seti@home classic account.

Since then, I've attached only the seti@home project and rebooted. It's been a few hours, but BOINC has so far failed to download any work units.

Below is a display since the last reboot, about 1/2 hour ago. The "MD5 check failed..." and the next 3 messages are red.

I am running Win2K w/ latest SP on a small home LAN with a hardware router. I am also running Norton Antivirus, but no software firewall.

Thanks for any help,

Ken

Thank y'all. Subsequent efforts on my part adds corroboration to the "Seti@home is down" explanation.

In the midst of the failing downloads, I attached another project (Einstein@home). Sure enough, E@H broke out of its shell, found its legs, stood up, and has been ambling along ever since. Seti@home is still reporting "Temporarily failed download."

I'm presuming that I don't have to do anything re S@H other than wait. For example, Michael R's suggestion of a corrupted datafile doesn't require any action on my part, does it?

Thanks again, folks,

Ken

---

Ken,

I'm happy to hear that you've picked up Einstein, that's where I do my crunching, and I think you'll like it there.

---

"The arc of history is long, but it bends toward Justice"

[I'm presuming that I don't have to do anything re S@H other than wait. For example, Michael R's suggestion of a corrupted datafile doesn't require any action on my part, does it?

Ken,

No. The MD5 error message says that the download trial failed.

You can look up most messages in the Wiki (in the messages section strangely enough) to get a little better understanding of what is happening. Of course if the explanation doesn't, let me know and I can try to fix that ...

Even after SETI@Home is "fixed" expect at least 24 hours before it will work reliably. Though, we have added many more participants that time may be longer now ... :(

---

Yes SETI is having problems with uploading/downloading certain files. See:

http://setiathome.ssl.berkeley.edu/

for more information.

Adagio

---

After upgrading BOINC Manager from 5.2.6 to 5.2.13 on Windows XP last night I received MD5 checksum errors downloading new WUs not only from SETI, but also rosetta and CPDN.

The problem started after my notebook (accidently) got into stand-by mode after the upgrade. Logging on again with my restricted account all cached WUs showed computation errors, followed by attempts to download new WUs which all failed because of checksum errors. I switched to my admin account (logged off the other user) and there download attempts where successful and the projects started to crunch. Once more changing to the restriced user I again received only checksum errors at WU download of rosetta and SETI - CPDN had already exceeded the daily WU quota with download errors :(

BM 5.2.13 was installed in shared mode as I did before with 5.2.6 , but I haven't had neither computation nor download errors at upgrade from 4.45 to 5.2.6 on the same system. Now I downgraded to 5.2.6 again and since this alone did not resolve the problem for the restriced user I restored the BOINC directory from the backup before upgrading, this finally helps.

Has anybody an idea what caused these problems and how I could prevent them from happening at the next upgrade trial? Since only the restricted user was affected I presume it'll have to do with file permissions, but I could not find any hint on such errors in relation to BM version upgrade in the BOINC Wiki, project FAQs or message boards.

Thanks and greetings,
anja