Questions and Answers : Sixtrack : LHC@home - 2005-02-22 02:47:14 - 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.
Message board moderation

To post messages, you must log in.

AuthorMessage
Brbe

Send message
Joined: 28 Sep 04
Posts: 9
Credit: 11,354,557
RAC: 103
Message 5771 - Posted: 22 Feb 2005, 1:50:13 UTC

what it means?????
ID: 5771 · Report as offensive     Reply Quote
DeMatt

Send message
Joined: 27 Sep 04
Posts: 4
Credit: 37,216
RAC: 0
Message 5778 - Posted: 22 Feb 2005, 2:30:44 UTC

A "code verification key" is a long block of characters that the BOINC server "signs" programs with, to ensure their authenticity. It is automatically given to a client when that client first signs up with a project.

What that message means is that the key your client has is old. It's possible that the server may send programs to your client with a new key, which doesn't match the key the client has, and therefore the client will reject the programs as fake.

If this happens, simply detach your client from LHC@Home, then re-attach to it. Your client will be forced to "forget" the old key and obtain a new one.
ID: 5778 · Report as offensive     Reply Quote
Tony Pinches

Send message
Joined: 28 Sep 04
Posts: 1
Credit: 2,184
RAC: 0
Message 5793 - Posted: 22 Feb 2005, 8:29:17 UTC - in response to Message 5778.  

> A "code verification key" is a long block of characters that the BOINC server
> "signs" programs with, to ensure their authenticity. It is automatically
> given to a client when that client first signs up with a project.
>
> What that message means is that the key your client has is old. It's possible
> that the server may send programs to your client with a new key, which doesn't
> match the key the client has, and therefore the client will reject the
> programs as fake.
>
> If this happens, simply detach your client from LHC@Home, then re-attach to
> it. Your client will be forced to "forget" the old key and obtain a new one.
>
I have this error message. When I detach the project I get the following:

-FILE_INFO::~FILE_INFO(): removing FILE_INFO when a pers_file_xfer still points to me
-Can't delete file projects\lhcathome.cern.ch\sixtrack_4.63_windows_intelx86.exe
-LHC@home - 2005-02-22 08:28:37 - Can't delete project directory: -110

And when I reattach, I still have the same problem. Any ideas what this might be about?


ID: 5793 · Report as offensive     Reply Quote
Profile Keck_Komputers

Send message
Joined: 1 Sep 04
Posts: 275
Credit: 2,652,452
RAC: 0
Message 5794 - Posted: 22 Feb 2005, 8:35:39 UTC - in response to Message 5778.  

> A "code verification key" is a long block of characters that the BOINC server
> "signs" programs with, to ensure their authenticity. It is automatically
> given to a client when that client first signs up with a project.
>
> What that message means is that the key your client has is old. It's possible
> that the server may send programs to your client with a new key, which doesn't
> match the key the client has, and therefore the client will reject the
> programs as fake.
>
> If this happens, simply detach your client from LHC@Home, then re-attach to
> it. Your client will be forced to "forget" the old key and obtain a new one.
>
Try to reset first. That will sometimes get the new key also. If you are running the 4.2x version wait until tomorrow to try anything that version requires all files to be signed.
BOINC WIKI

BOINCing since 2002/12/8
ID: 5794 · Report as offensive     Reply Quote

Questions and Answers : Sixtrack : LHC@home - 2005-02-22 02:47:14 - 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.


©2024 CERN