apologies for what may be an ignorant question but ive run into this problem on two hosts:
7291 Einstein@Home 12/9/2012 10:31:29 [error] Unable to verify einsteinbinary_BRP4_1.32_windows_x86_64__opencl-ati.exe using certificates
7292 Einstein@Home 12/9/2012 10:31:29 [error] Checksum or signature error for einsteinbinary_BRP4_1.32_windows_x86_64__opencl-ati.exe
7308 Einstein@Home 12/9/2012 10:31:38 [error] Unable to verify einsteinbinary_BRP4_1.00_graphics_windows_intelx86.exe using certificates
7309 Einstein@Home 12/9/2012 10:31:38 [error] Checksum or signature error for einsteinbinary_BRP4_1.00_graphics_windows_intelx86.exe
4291 Einstein@Home 12/9/2012 10:31:30 [error] Unable to verify einsteinbinary_BRP4_1.32_windows_intelx86__BRP4cuda32nv301.exe using certificates
4292 Einstein@Home 12/9/2012 10:31:30 [error] Checksum or signature error for einsteinbinary_BRP4_1.32_windows_intelx86__BRP4cuda32nv301.exe
4298 Einstein@Home 12/9/2012 10:31:32 [error] Unable to verify cudart_xp32_32_16.dll using certificates
4299 Einstein@Home 12/9/2012 10:31:32 [error] Checksum or signature error for cudart_xp32_32_16.dll
4315 Einstein@Home 12/9/2012 10:31:45 [error] Unable to verify einsteinbinary_BRP4_1.00_graphics_windows_intelx86.exe using certificates
4316 Einstein@Home 12/9/2012 10:31:45 [error] Checksum or signature error for einsteinbinary_BRP4_1.00_graphics_windows_intelx86.exe
4319 Einstein@Home 12/9/2012 10:31:46 [error] Unable to verify dbhs.dev.win.154c6c4 using certificates
4320 Einstein@Home 12/9/2012 10:31:46 [error] Checksum or signature error for dbhs.dev.win.154c6c4
4323 Einstein@Home 12/9/2012 10:31:47 [error] Unable to verify db.dev.win.154c6c4 using certificates
4324 Einstein@Home 12/9/2012 10:31:47 [error] Checksum or signature error for db.dev.win.154c6c4
4327 Einstein@Home 12/9/2012 10:31:48 [error] Unable to verify EULA.txt using certificates
4328 Einstein@Home 12/9/2012 10:31:48 [error] Checksum or signature error for EULA.txt
4333 Einstein@Home 12/9/2012 10:31:50 [error] Unable to verify cufft_xp32_32_16.dll using certificates
4334 Einstein@Home 12/9/2012 10:31:50 [error] Checksum or signature error for cufft_xp32_32_16.dll
on both hosts, the actual wu all download fine (as an example on host 2):
...
4666 Einstein@Home 12/9/2012 10:34:46 Finished download of p2030.20111208.G192.45-04.30.C.b6s0g0.00000_1301.bin4
4667 Einstein@Home 12/9/2012 10:34:46 Started download of p2030.20111208.G192.45-04.30.C.b6s0g0.00000_1303.bin4
4668 Einstein@Home 12/9/2012 10:34:47 Finished download of p2030.20111208.G192.45-04.30.C.b6s0g0.00000_1302.bin4
4669 Einstein@Home 12/9/2012 10:34:47 Finished download of p2030.20111208.G192.45-04.30.C.b6s0g0.00000_1303.bin4
4670 Einstein@Home 12/9/2012 10:34:47 Started download of p2030.20111208.G192.45-04.30.C.b6s0g0.00000.zap
4671 Einstein@Home 12/9/2012 10:34:47 Started download of p2030.20110129.G193.72-01.11.C.b4s0g0.00000_3320.bin4
...
in fact, all the wu files would download without error and when a project update is issued, they are deleted. makes sense since they dont have executables to run.
host two used to actually run e@h and now gets this error so i thought this was strange.
when seting up host 1 initially, i got a different error about the boinc client version so i upgraded it to 7.0.28. that issue was solved but now i get this problem.
ive been looking for a way to solve this. initially, i thought it was a permissions issue but checked that. been looking around the forums and even google returns no results.
ive tried uninstalling and reinstall the client, no luck. ive also tried detaching and reattaching the project with the same results.
additionally, each time it fails in this way, i have to wait an entire day due to the way e@h relegates the hosts into a max quota mode.
any ideas would be appreciated, ill have to wait until tomorrow to try them out of course.
thanks for the help.
Copyright © 2024 Einstein@Home. All rights reserved.
Checksum errors on download of project executables
)
I'm guessing but "Unable to verify einsteinbinary_BRP4_1.00_graphics_windows_intelx86.exe using certificates " suggests to me that you may have a corrupted public certificate.
I'm not sure what the least intrusive way to do this would be but I'm pretty sure deleting the project and the BOINC directory and the attaching to the project again will do it.
If you don't get any wu's then I think it's worth trying. If some come through and verify OK then I would suspect a hardware problem like memory problems.
Joe
RE: I'm guessing but
)
ya, seems hard to tell. currently im running down the caches on those two hosts for s@h, then im going to retry a clean boinc installation on both.
i did do this previously once and it didnt seem to fix the issue so im not overly optimistic about the results this time around.
cya.