| Author |
Message |
|
|
|
Just noticed Boinc trying to download version 6.08 from the server. I've got this error
21-1-2009 5:57:48|SETI@home|21-1-2009 5:57:48|SETI@home|Finished download of setiathome_6.08_windows_intelx86__cuda.exe
21-1-2009 5:57:48|SETI@home|[error] Signature verification failed for setiathome_6.08_windows_intelx86__cuda.exe
21-1-2009 5:57:48|SETI@home|[error] Checksum or signature error for setiathome_6.08_windows_intelx86__cuda.exe
I'm running stock everything so does anyone have any ideas??
Edit: This results in failed downloads of new WU's!
____________
|
|
|
|
|
|
Same thing for me.
Thierry
____________
|
|
|
|
|
|
Snap,
I am unable to download new work units.
21/01/2009 07:06:18||Starting BOINC client version 6.4.5 for windows_intelx86
21/01/2009 07:06:18||log flags: task, file_xfer, sched_ops
21/01/2009 07:06:18||Libraries: libcurl/7.19.0 OpenSSL/0.9.8i zlib/1.2.3
21/01/2009 07:06:18||Data directory: E:\Utilities\Web\Bionic\xxdata
21/01/2009 07:06:18||Running under account Jonathan
21/01/2009 07:06:18||Processor: 2 GenuineIntel Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz [x86 Family 6 Model 15 Stepping 2]
21/01/2009 07:06:18||Processor features: fpu tsc pae nx sse sse2 mmx
21/01/2009 07:06:18||OS: Microsoft Windows XP: Home x86 Editon, Service Pack 3, (05.01.2600.00)
21/01/2009 07:06:18||Memory: 1.99 GB physical, 3.84 GB virtual
21/01/2009 07:06:18||Disk: 72.72 GB total, 52.89 GB free
21/01/2009 07:06:18||Local time is UTC +0 hours
21/01/2009 07:06:18||Not using a proxy
21/01/2009 07:06:18||CUDA devices found
21/01/2009 07:06:18||Coprocessor: GeForce 9600 GT (1)
21/01/2009 07:15:04|SETI@home|Sending scheduler request: To fetch work. Requesting 5522 seconds of work, reporting 1 completed tasks
21/01/2009 07:15:09|SETI@home|Scheduler request completed: got 1 new tasks
21/01/2009 07:15:11|SETI@home|Started download of setiathome_6.08_windows_intelx86__cuda.exe
21/01/2009 07:15:11|SETI@home|Started download of 10dc08aa.27153.19295.11.8.25
21/01/2009 07:15:14|SETI@home|Finished download of 10dc08aa.27153.19295.11.8.25
21/01/2009 07:15:17|SETI@home|Finished download of setiathome_6.08_windows_intelx86__cuda.exe
21/01/2009 07:15:17|SETI@home|[error] Signature verification failed for setiathome_6.08_windows_intelx86__cuda.exe
21/01/2009 07:15:17|SETI@home|[error] Checksum or signature error for setiathome_6.08_windows_intelx86__cuda.exe
|
|
|
|
|
|
You're not alone, i have the same problem..... Probably a bad file or the main .exe has been damaged.... Hope they fix it quick.
/Will
____________
|
|
|
|
|
|
You could always try a driect download from http://boinc2.ssl.berkeley.edu/sah/download_fanout/setiathome_6.08_windows_intelx86__cuda.exe and place it in the seti folder.
____________
|
|
|
|
|
|
If that's the file that fails the verification in the first place, I'm not so sure I want to do that. I'll wait for the admins to check and correct.
Another thing, firing up my "slower" laptop, it started to process Cuda WU's again. It's not using the 6.08 though, but 6.06.
Speculating I would say:
1. The slower machines that weren't allowed Cuda WU's for the last few days, are now allowed new 6.06 WU's.
2. The faster machines that in the last days kept on using Cuda now try to use 6.08.
I don't get it, the slower machines were cut of of 6.06 WU's in the first place 'cause 6.06 was causing errors on those machines. Why allowing it now?
____________
|
|
|
|
|
|
I have this:
21/01/2009 07:58:45|SETI@home|Started download of setiathome_6.08_windows_intelx86__cuda.exe
21/01/2009 07:58:45|SETI@home|Started download of cudart.dll
21/01/2009 07:58:49|SETI@home|Finished download of setiathome_6.08_windows_intelx86__cuda.exe
21/01/2009 07:58:49|SETI@home|Finished download of cudart.dll
21/01/2009 07:58:49|SETI@home|[error] Signature verification failed for setiathome_6.08_windows_intelx86__cuda.exe
21/01/2009 07:58:49|SETI@home|[error] Checksum or signature error for setiathome_6.08_windows_intelx86__cuda.exe
21/01/2009 07:58:49|SETI@home|[error] Signature verification failed for cudart.dll
21/01/2009 07:58:49|SETI@home|[error] Checksum or signature error for cudart.dll
I tried resetting the seti project - didn't help.
I tried detaching from seti, stopping and restarting bionc, reattaching to seti - idn't help.
I downloaded setiathome_6.08_windows_intelx86__cuda.exe directly using firefox and compared (fc /b) it agains the copy bionc had downloaded and they are the same.
I'm not that sure what to do next! |
|
|
|
|
|
Same with me, but had to go to work so cant fix yet. only on one machine at the moment, all rest using 6.03 but not 6.06
Mike GM3EIY |
|
|
|
|
|
Same here, countless automatic download attempts of 6.08 all failed, WUs for 6.08 fail to download, no new 6.06 WUs downloaded. Not good.
Looks like I'm not going to be offered any more 6.06 units so no harm trying the manual download, CUDA will be idle otherwise.
Edit - well the 6.08 exe is already there is the directory, so that didn't help... |
|
|
RaistmerVolunteer developer Volunteer tester
 Send message
Joined: 16 Jun 01 Posts: 2626 Credit: 26,637,339 RAC: 35,649

|
|
Try to use app_info.xml file.
It should stop CRC checking and will allow to use downloaded 6.08 |
|
|
|
|
|
Dang, I miss out on all the fun. Mine hasn't even tried to download the new 608s and is happily crunching along on the 607s.
Could it be because I'm running Raistmer's V6?
Yep, just checked my app_info No 608 mentioned. Guess I'll keep crunching 607s till they get the 608 fixed.
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
|
It's still downloading the bad copy of 6.08 and still broke.
Did anyone actually test this release?
Is it going to be fixed any time soon, or do we have to figure it out ourselves?
Is there life on Mars?... |
|
|
|
|
Dang, I miss out on all the fun. Mine hasn't even tried to download the new 608s and is happily crunching along on the 607s.
Could it be because I'm running Raistmer's V6?
Yes. If you're using Raistmer's app, then by definition you're using an app_info.xml file - and that means you have to do your updating manually. You won't get v6.08 automatically - which seems like a good thing, given the reports here.
Since you've got an app_info already, you could download setiathome_6.08_windows_intelx86__cuda.exe (1,412 KB) manually, and edit your existing file to replace all references to Raistmer's file with references to setiathome_6.08_windows_intelx86__cuda.exe. |
|
|
|
|
|
I'm running BOINC 6.6.0 and having the same check sum issue with 6.08 EXE, along with countless failed Seti CUDA 6.08 work units on all five of my cuda eligible machines. GPUGRID (just attached to this project yesterday) and Seti CUDA 6.06 are proccessing correctly though, as far as I can tell.
____________
|
|
|
|
|
It's still downloading the bad copy of 6.08 and still broke.
Did anyone actually test this release?
Is it going to be fixed any time soon, or do we have to figure it out ourselves?
Is there life on Mars?...
There may be life on Mars, but there probably is little life in the labs in Berkeley right now :-)
Time difference between UTC and Berkeley is, if I remember correctly, 8 hours. So it's now approx 6:36 AM in Berkeley (15:36 in the Netherlands, UTC+1). So it will probably be at least a couple of hours before someone over there notices that something is wrong ...
Regards,
John.
|
|
|
|
|
|
Is there anyplace else we should post this problem?
____________
|
|
|
|
|
|
I've posted in Technical News and the Staff Blog, linking back to this thread.
Not much else we can do, really, since there's no official place for posting bug reports except here.
Unless a passing Mod has a back-channel they could press into service? |
|
|
|
|
|
As was said earlier, right now it is only 7:30 in Berkeley right now. They should be coming in to work shortly. I'm sure they will hear about it as soon as they get in. Another great start to a beautiful day. :)
____________
PROUD MEMBER OF Team Starfire World BOINC |
|
|
|
|
|
You mean that they don't have a 24hr help line for Insomniacs?
____________
|
|
|
|
|
You mean that they don't have a 24hr help line for Insomniacs?
Yes they do - we're it! |
|
|