|
21)
Message boards :
Number crunching :
jiiippeee the first WU from LHC!
(Message 5692)
Posted 21 Feb 2005 by  [SETI.USA]Tank_Master
Post: I detached and reattached the project like the last error message said to do, after 3 attempts to reattach, it finally did, and the checksum error did NOT reappear. All files downloaded ok. Both work units are now in "ready to run" status. Its computing for other projects at the moment. ~Keith |
|
22)
Message boards :
Number crunching :
jiiippeee the first WU from LHC!
(Message 5691)
Posted 21 Feb 2005 by [SETI.USA]Tank_Master
Post: I am running a P4 3.2 on boinc 4.66 and server 2003 (w/ SP1) I have gotten the following messages 3 times, all for the same file (sixtrack_4.63_windows_intelx86.exe). Times are in Pacific Time: 2/21/2005 10:25:39 AM|LHC@home|Finished download of sixtrack_4.63_windows_intelx86.exe 2/21/2005 10:25:39 AM|LHC@home|Throughput 54142 bytes/sec 2/21/2005 10:25:39 AM|LHC@home|signature verification error for sixtrack_4.63_windows_intelx86.exe 2/21/2005 10:25:39 AM|LHC@home|Checksum or signature error for sixtrack_4.63_windows_intelx86.exe 2/21/2005 10:25:39 AM|LHC@home|Unrecoverable error for result v64boince6ib1-15s18_20660_1_sixvf_719_9 (app_version download error: couldn't get input files: sixtrack_4.63_windows_intelx86.exe -120 signature verification error) 2/21/2005 10:25:39 AM|LHC@home|Unrecoverable error for result v64boince6ib1-21s10_12660_1_sixvf_939_8 (app_version download error: couldn't get input files: sixtrack_4.63_windows_intelx86.exe -120 signature verification error) 2/21/2005 10:25:40 AM|LHC@home|Deferring communication with project for 59 seconds In between each one, I got the error "project is down" (most likely do to the database overload) After the third fail of the "checksum error" I got for 2 times in a row (I forced an update about 5 min after this failed attempt and got the same message): 2/21/2005 10:30:07 AM|LHC@home|Message from server: You may have an outdated code verification key. This may prevent you from accepting new executables. If the problem persists, detach/attach the project. 2/21/2005 10:30:07 AM|LHC@home|No work from project 2/21/2005 10:30:07 AM|LHC@home|Deferring communication with project for 1 hours, 0 minutes, and 0 seconds ~Keith |
Previous 20
©2024 CERN