LHC@home

I tried to attach a new computer to this project earlier today. All the files had checksum errors so the work had unrecoverable errors.

It may be related to the newer client. I seem to recall a mention of signatures being required for more files.

CC4.22 winxp home.

---

BOINC WIKI

BOINCing since 2002/12/8

A similar thing happened on one of my machines as well. Not checksum errors, but the app wouldn't run giving a "text busy" error or something like that. Doing a reset on the project resolved the problem, but still, it is a sign of something wrong.

---

> I tried to attach a new computer to this project earlier today. All the files
> had checksum errors so the work had unrecoverable errors.
>
> It may be related to the newer client. I seem to recall a mention of
> signatures being required for more files.
>
> CC4.22 winxp home.
>
4.22 requires all of the project application files (not the WU files) to be signed.

---

BOINC WIKI

I reset the project on another working computer and now it is giving the checksum errors and cannot get more work.

CC4.22 winxp pro

---

BOINC WIKI

BOINCing since 2002/12/8

> I reset the project on another working computer and now it is giving the
> checksum errors and cannot get more work.
>
> CC4.22 winxp pro

I have no experience on 4.22 but if it requires all files to be signed then the windows client certainly won't work.

---

Markku Degerholm
LHC@home admin

I am running BOINC 4.66 on a P4 3.2 prescott and server 2003. After detaching and reattaching this project, my checksum error went away, as did the message about "invalid keys"

~Keith

---

I never detached from LHC since last fall, but couldn't get work. did get the "key" message. I tried Resetting, did nothing. I detached and reattached, and after several reattach efforts I downloaded the files and 6 WUs, they all failed Checksum.

WINXP Boinc V4.22

tony

---

Formerly
mmciastro. Name and avatar changed for a change

The New Online Helpsytem help is just a call away.

> > I reset the project on another working computer and now it is giving the
> > checksum errors and cannot get more work.
> >
> > CC4.22 winxp pro
>
> I have no experience on 4.22 but if it requires all files to be signed then
> the windows client certainly won't work.
>
>

Looks like CC4.22 needs all *.tga s to be signed

Chris

> I am running BOINC 4.66 on a P4 3.2 prescott and server 2003. After detaching
> and reattaching this project, my checksum error went away, as did the message
> about "invalid keys"
>
> ~Keith
>

Thanks Keith, tried it and it seems to have worked. Am running 4.62 on 2.07 AMD Athlon XP
WXP SP2

---

<img src="http://www.boincstats.com/stats/banner.php?cpid=162d855da85b4ee993029a39cfeed63a">

I changed one puter back to 4.19 from 4.22. It's now downloading.... we shall see.

tony

As said in news and here , there is a problem in sign key update. It can be worked around by resetting the project, but if that disturbs you (it should), please wait until we manage to sign the new keys properly.

The "Invalid key" error occurred when the bad key signature file was in place on the server. Now it's not so the client won't try to check the key authenticity, it just checks the autheticity of the binaries (which fails unless the project is reset).

---

Markku Degerholm
LHC@home admin

> 4.22 requires all of the project application files (not the WU files) to be
> signed.
>
And what is about CC 4.62?

I got some work with it after reattaching, but run-time was/is verry short (12,4,4,1,26,4 minutes), predicted is 11 hours.

CC 4.19 seems to work as it should.

---

Doesn't seem to be a problem with the 4.19 clients, after resetting.

[Edit] Although now looking back at my WU list, the LHC WU is still downloading, eventhough everything has finished downloading. Hrmm... [/edit]

---

well bummer. My one computer that I reset for LHC tried to download the WU's and related files, but because of the checksum errors it failed. So, it tried another one and of course it failed, too. Now I am over my alloted quota for the day. I guess I'll wait until tomorrow to reset my other computers.

---

I'm getting a checksum error for the sixtrack 4.63 client.

LHC@home - 2005-02-22 05:10:17 - signature verification error for sixtrack_4.63_windows_intelx86.exe
LHC@home - 2005-02-22 05:10:17 - Checksum or signature error for sixtrack_4.63_windows_intelx86.exe

---

The 4.22 client definetly has a problem with all the files. I attached a new machine and all the downloads failed with signature verification errors. I reset and detached/reatached another machine and got the exact same error. Now I've hit my daily Quota for the machines and have no wu. I am using Win XP Home SP2.

---

OK, the 4.22 client that checksum failed earlier, has been converted to 4.19 and is now crunching two WUs. On to puter #3.

tony

> Doesn't seem to be a problem with the 4.19 clients, after resetting.
>
> [Edit] Although now looking back at my WU list, the LHC WU is still
> downloading, eventhough everything has finished downloading. Hrmm... [/edit]
>
4.19 client, LHC left over from previous runs, checksum error on the new .exe the first time.
Reset project as suggested, exited and restarted boinc, another checksum error.
Detached and re-attached, download successful, three to process.

We'll see how the first workunits go. --Don

Markku ellucidated.....
> As said in news and <a> href="http://lxfsrk4101.cern.ch/forum_thread.php?id=1123"> here [/url], there is
> a problem in sign key update. It can be worked around by resetting the
> project, but if that disturbs you (it should), please wait until we manage to
> sign the new keys properly.
>
> The "Invalid key" error occurred when the bad key signature file was in place
> on the server. Now it's not so the client won't try to check the key
> authenticity, it just checks the autheticity of the binaries (which fails
> unless the project is reset).
>

But not with BOINC V4.22!

> Markku ellucidated.....

Ellucidated???? I needed a dictionary for that one. LOL