Problem with download WU

Author	Message
PlaNed Send message Joined: 19 Jul 01 Posts: 28 Credit: 321,251 RAC: 0	Message 11936 - Posted: 24 Jul 2004, 14:28:11 UTC SETI@home - 2004-07-24 17:04:58 - Finished download of 21se03ab.9366.3104.1009650.25 SETI@home - 2004-07-24 17:04:58 - Approximate throughput 110.440632 bytes/sec SETI@home - 2004-07-24 17:04:58 - verify_downloaded_file(): projects\\setiathome.berkeley.edu\\21se03ab.9366.3104.1009650.25: MD5 check failed SETI@home - 2004-07-24 17:04:58 - expected 6b8255f43501284f901fd8713ef7ec03, got 7576c6fab689ed4803020563b2ed0d35 SETI@home - 2004-07-24 17:04:58 - Checksum or signature error for 21se03ab.9366.3104.1009650.25 SETI@home - 2004-07-24 17:04:58 - Unrecoverable error for result 21se03ab.9366.3104.1009650.25_5 (file transfer error: couldn't get input files: 21se03ab.9366.3104.1009650.25: ) Idea? ID: 11936 ·

nyctalopyman Send message Joined: 15 Apr 03 Posts: 4 Credit: 20,893 RAC: 0	Message 11945 - Posted: 24 Jul 2004, 15:01:54 UTC I have the same problem when running my linux version of boinc . . . boinc is trying to download setiathome_3.08_i686-pc-linux-gnu but the checksum is wrong... ID: 11945 ·

ralic Volunteer tester Send message Joined: 6 Jan 00 Posts: 308 Credit: 274,230 RAC: 0	Message 11946 - Posted: 24 Jul 2004, 15:05:39 UTC > SETI@home - ... {snip} ... MD5 check failed Have a look in the BOINC FAQ here. Search for What does MD5 check failed mean? ID: 11946 ·

ralic Volunteer tester Send message Joined: 6 Jan 00 Posts: 308 Credit: 274,230 RAC: 0	Message 12437 - Posted: 26 Jul 2004, 19:06:01 UTC - in response to Message 11946. Last modified: 26 Jul 2004, 19:11:11 UTC > Search for What does MD5 check failed mean? Ok, things seem to have changed a little in my absence. nyctalopyman, as far as I know, your problem can only be solved with a project reset. This is because the binary is the file with bad MD5 checksum. However, PlaNed, there may yet be hope for you, depending on the situation. If this is the only WU being downloaded, then try a project update and see what happens. If more than one was being downloaded, then processing should continue as per normal. This is because it is the WU that has a bad MD5. It seems that a project reset is now only required if an MD5 is experienced on the application binary, or one of its support files. I will mention to Paul, and ask him to update the FAQ accordingly. ID: 12437 ·

nyctalopyman Send message Joined: 15 Apr 03 Posts: 4 Credit: 20,893 RAC: 0	Message 12794 - Posted: 27 Jul 2004, 16:19:22 UTC - in response to Message 12437. I'm sorry but I already made a reset of the project three times, but it still doesn't work. Boinc says that it can't update the code signing key . . . ID: 12794 ·

ralic Volunteer tester Send message Joined: 6 Jan 00 Posts: 308 Credit: 274,230 RAC: 0	Message 12795 - Posted: 27 Jul 2004, 16:24:04 UTC - in response to Message 12794. > Boinc says that it can't update the code signing key . . . Sorry, not familiar with that one. Perhaps the people in the linux forums can assist? ID: 12795 ·

ralic Volunteer tester Send message Joined: 6 Jan 00 Posts: 308 Credit: 274,230 RAC: 0	Message 13027 - Posted: 28 Jul 2004, 8:53:21 UTC - in response to Message 12795. > > Boinc says that it can't update the code signing key . . . Did you try detach from the project and reattach? ID: 13027 ·

©2025 University of California

SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.