LHC@home

I get Downloading failed everytime I try downloading a workunit.....

Does anyone know why?

---

Some stupid thing the project admins decided to implement between the recent alpha testing and going public. BOINC V4.22 worked a treat prior to going public and now using it you get

signature verification error
Checksum or signature error

Until you hit your daily download quota for that host.

However if you using V4.19 then just reset or dettach and reattach and it should work OK, but if your using V4.22 (development) then it doesn't help other than to waste wu's.

Rediculous really, why change something between testing and public!!!

---

Paul
(S@H1 8888)
BOINC/SAH BETA

We have used a new set of sign keys on the new server right from the beginning. This was done to enhance security of the users.

Boinc CC v4.22 should still work with the linux client because it has only one file which is signed. Windows version has multiple files but only the executable is signed, so CC v4.22 should have never worked with it.

Stupid thing here is that we didn't test the key update mechanism and so we had a bad key signature in place. But this should be fixed today, and we intend to sign all the client files so even CC v4.22 should start working.

---

Markku Degerholm
LHC@home admin

Remember that the official release is CC 4.19

All further releases of CC 4.6x and 4.2x are beta or even alpha version and are not intended to be used by general public.

Whoever is not in alpha or beta can use them but should not whine if something goes wrong.
It's very boring reading about those CC not working on boards of all projects.

There is a simple solution, which will probably resolve all problems.
If it's not working go back to official CC version.

Tony

> Whoever is not in alpha or beta can use them but should not whine if something
> goes wrong.
> It's very boring reading about those CC not working on boards of all
> projects.
>
Most of the people complaining about it though are Alpha or Beta testers.
Yet even the official CC 4.19 needed a detach/reattach, so it's correct that people complained.

And unless LHC 2005 is now out of beta, meaning people from all over the world can go to account creation and sign up, it's valid to check with all the present alpha and beta versions of BOINC to see if they work.

---

Jord

BOINC FAQ Service

Well then, don't read the posts from us who are using the 4.2x and 4.6x clients. Simply skip over those posts. We who are using the above mentioned clients deserve the right to ask for help also. We are asking for help from the others of us who are also using those clients. If you chose to use the 4.19 client then the questions pertaining to the 4.2x and 4.6x clients probably don't apply to you, therefore you can safely ignore those posts.



Jim

>
> Remember that the official release is CC 4.19
>
> All further releases of CC 4.6x and 4.2x are beta or even alpha version and
> are not intended to be used by general public.
>
> Whoever is not in alpha or beta can use them but should not whine if something
> goes wrong.
> It's very boring reading about those CC not working on boards of all
> projects.
>
> There is a simple solution, which will probably resolve all problems.
> If it's not working go back to official CC version.
>
> Tony
>

---

> Well then, don't read the posts from us who are using the 4.2x and 4.6x
> clients. Simply skip over those posts. We who are using the above mentioned
> clients deserve the right to ask for help also. We are asking for help from
> the others of us who are also using those clients. If you chose to use the
> 4.19 client then the questions pertaining to the 4.2x and 4.6x clients
> probably don't apply to you, therefore you can safely ignore those posts.
>
>
>
> Jim
>
> >
> > Remember that the official release is CC 4.19
> >
> > All further releases of CC 4.6x and 4.2x are beta or even alpha version
> and
> > are not intended to be used by general public.
> >
> > Whoever is not in alpha or beta can use them but should not whine if
> something
> > goes wrong.
> > It's very boring reading about those CC not working on boards of all
> > projects.
> >
> > There is a simple solution, which will probably resolve all problems.
> > If it's not working go back to official CC version.
> >
> > Tony
> >
>

well done Jim, that's my opinion too. Thanx!

---

Synergy means the whole is greater than the sum of its parts.

> we had a bad key signature in place. But this should be fixed today, and we
> intend to sign all the client files so even CC v4.22 should start working.
>
>
Good to see you are on both problems.
Nice also that we helped verify 4.22 security measures works as it should.
Rebirth of LHC@home has been lotsa fun.

---

Markku said.....
> We have used a new set of sign keys on the new server right from the
> beginning. This was done to enhance security of the users.
>
> Boinc CC v4.22 should still work with the linux client because it has only one
> file which is signed. Windows version has multiple files but only the
> executable is signed, so CC v4.22 should have never worked with it.
>
> Stupid thing here is that we didn't test the key update mechanism and so we
> had a bad key signature in place. But this should be fixed today, and we
> intend to sign all the client files so even CC v4.22 should start working.
>

I'm 100% sure I was using the BOINC V4.22 on the recent alpha testing and all I did was detach from the alpha url and reattach to the main url this morning just prior going to work. Only then did I get the errors described previously.

> I'm 100% sure I was using the BOINC V4.22 on the recent alpha testing and all
> I did was detach from the alpha url and reattach to the main url this morning
> just prior going to work. Only then did I get the errors described
> previously.

Well, then I don't understand why it worked before. If 4.22 requires all files to be signed, it shouldn't have worked because the .tga files certainly weren't signed before 15.xx UTC today.

---

Markku Degerholm
LHC@home admin

>
> > I'm 100% sure I was using the BOINC V4.22 on the recent alpha testing and
> all
> > I did was detach from the alpha url and reattach to the main url this
> morning
> > just prior going to work. Only then did I get the errors described
> > previously.
>
> Well, then I don't understand why it worked before. If 4.22 requires all files
> to be signed, it shouldn't have worked because the .tga files certainly
> weren't signed before 15.xx UTC today.
>
>
If you download the files with an earlier version then upgrade to 4.2x then they will still work. The problem only comes up when new files have to be downloaded.

---

BOINC WIKI

BOINCing since 2002/12/8