LHC@home

Hello,

Just to be sure, the news page states it\'s better to use 5.10.x version of BOINC, but on their webpage there\'s a 6.x version to download. Is that right?

I did not upgraded on my work machine yet (Windows), but I was planning to. If that\'s the case I will keep this version.

I upgraded BOINC on my home machine, on the Windows boot, but it blew up the climateprediction work unit it was crunching, so I was going to research before upgrading it on work. (In the end I uninstalled it there altogether, I was barely booting on Windows at home anyway.)



eks

6.2 is the latest stable BOINC release from Berkley. Howevere, LHC@home has a problem with people using these clients.
If you want to use 6.2, make sure you\'re not asking for work from LHC@home. If you want to crunch for LHC, for now, you must be on 5.10

---

If you want to use 6.2, make sure you\\\'re not asking for work from LHC@home. If you want to crunch for LHC, for now, you must be on 5.10

This is unbelievable ! I had calculated already some WUs up to 3.Sept. using the newest BOINC Version. So where could I get the old version from ? With the last upgrade the directories for all my other BOINC projects were shifted. Is there any de-installation routine which will shift them back to where BOINC 5.10 will expect them ?

My last WUs were:
\'Redundant result - Cancelled by server\'.
Is that the sign of using the wrong BOINC ?
Who is able to correct this towabohu ?
thanks for help
Dr.Mabuse

---

Snip...

[quote]
So where could I get the old version from ? With the last upgrade the directories for all my other BOINC projects were shifted. Is there any de-installation routine which will shift them back to where BOINC 5.10 will expect them ?

My last WUs were:
'Redundant result - Cancelled by server'.
Is that the sign of using the wrong BOINC ?
Who is able to correct this towabohu ?
thanks for help
Dr.Mabuse

I recently stepped back to the earlier BOINC version, dr mabuse. You can go to http://boinc.berkeley.edu/download_all.php to download the appropriate version. In my case, I simply closed the running BOINC manager program, and executed the downloaded installer for version 5.10.45. This didn't wipe out any of the work units I had. I suppose that any finished work units should be reported first, but both the pending and the running WU's continued smoothly and without problems on a Vista and XP machine here.

I hope this helps.

Kibble

In my case, I simply closed the running BOINC manager program, and executed the downloaded installer for version 5.10.45. This didn\\\'t wipe out any of the work units I had. I suppose that any finished work units should be reported first, but both the pending and the running WU\\\'s continued smoothly and without problems on a Vista and XP machine here.

I hope this helps.

Kibble

No, it doesn\\\'t. I have WUs from climateprediction.net which will finish in the beginning of 2009. Could you explain us or give a hint to another expert what is the problem with the BOINC 6 version ? And has the last message I got \\\'Redundant result - Cancelled by server\\\' anything to do with this incompatibility ?
Thanks for further help.
Dr.Mabuse

Down=versioning isn\'t really an option. I have other work running (long jobs) and the change from Version 6.x.x back to Version 5.x.x will likely trash all the work already done. I have taken this route in the past and seen it happen before.

If downgrading will cause you problems on other projects, just set LHC@home to \"No new work\" until the problems here aare fixed.

---

Down=versioning isn\\\'t really an option. I have other work running (long jobs) and the change from Version 6.x.x back to Version 5.x.x will likely trash all the work already done. I have taken this route in the past and seen it happen before.

I went from 6.2.xx to 5.10.xx and it worked fine. It took a little more time but I didn\'t loose my cpdn @ 86% complete and 749hrs.

EDIT: Don't forget to set U'r manager to SNOOZE before you start the downgrade!

---

A clear conscience is usually the sign of a bad memory

Down=versioning isn\\\\\\\'t really an option. I have other work running (long jobs) and the change from Version 6.x.x back to Version 5.x.x will likely trash all the work already done. I have taken this route in the past and seen it happen before.

I went from 6.2.xx to 5.10.xx and it worked fine. It took a little more time but I didn\\\'t loose my cpdn @ 86% complete and 749hrs.

EDIT: Don\'t forget to set U\'r manager to SNOOZE before you start the downgrade!

I stick with 5.8.16 for a reason... ;-)

Maybe Mr. Anderson should try fixing his software before worrying about his other pet peeves?

I would think that downversioning is not an option. Like many other issues this specific issue should be resolved not with a workaround but with a solution. It may take some time, it may take some of my credits. But in the end I want to see real progress. We are here to support the project (a fascinating project imho) and not just to earn credits. If credits are your major concern there are many other projects which are much more suitable for your interests. But if you are really interested in the project and its progress, give the team a chance (and the time) to come up with a real solution.


Whenever you find yourself on the side of the majority, it is time to pause and reflect.
-Mark Twain-

I went from 6.2.xx to 5.10.xx and it worked fine. It took a little more time but I didn't loose my cpdn @ 86% complete and 749hrs.
EDIT: Don't forget to set U'r manager to SNOOZE before you start the downgrade!

Another good revert here without losing any ongoing work. The reversion from 6.2 to 5.10 just worked fine on my Windows XP machine. However, I won't be reverting on my Linux PC, since the upgrade to 6.2 was a bit of a problem here.

I would think that downversioning is not an option. Like many other issues this specific issue should be resolved not with a workaround but with a solution. It may take some time, it may take some of my credits. But in the end I want to see real progress. We are here to support the project (a fascinating project imho) and not just to earn credits. If credits are your major concern there are many other projects which are much more suitable for your interests. But if you are really interested in the project and its progress, give the team a chance (and the time) to come up with a real solution.


Whenever you find yourself on the side of the majority, it is time to pause and reflect.
-Mark Twain-

Just read a post over at CPDN and they also recommend the 5.10.xx downgrade because of some issues with the 6.2.xx version

---

A clear conscience is usually the sign of a bad memory

what about those of us who MUST use the 6.x client for the other projects simply cannot run on any 5.x?

---

It is possible to run 2 different versions of BOINC, though it requires manually starting up and exiting each to get some time on both.

This said, recommendation does not mean requirement. And depending on the bug (I\'m not going to pretend to have experienced this); one could try getting a WU, and just micromanage BOINC a little to force it to run LHC when one\'s there for a WU and see if it goes. If it does, great, if it doesn\'t; then address it. If it works, one can activate their other projects and let it run confident one hadn't run into a problem. Just check it periodically then to make sure all remains OK. First sign of trouble, then address it, the advice was given to alert people to the possibility.

The lattest news items

06.09.2008 12:30 BST -


Hi,
Further to yesterday\'s news item, we are recommending that you download/use the 5.10.X version of the BOINC client for your opertaing system. We hope to have this sorted as soon as possible but with LHC turn on in 4 days everyone is busy preparing for that.

Later days,
Neasan

05.09.2008 10:40 BST -

Hi,
Alex has been doing some tweaking in the background this week so some issues have been resolved. We are looking into the others and fixing them as we find solutions. Also the SixTrack application and the newest version of the BOINC client (6.2.X) don\'t seem to like each other. The developers are looking into this problem and it will be fixed as soon as possible.

Later days,
Neasan

are not specifically saying whether EVERYONE would or would not have a problerm. There a recomendation based on various things that have been noted. Those without the problem in already crunched WUs might have just been lucky. But it doesn\'t follow that it will not work for anyone (wasn\'t mentioned wholy incompatible in the note).

Just be aware, and sort it among the projects as each person sees best. Some might find it more prudent to downgrade, others might not have upgraded, some might be seeing no problem at all, and until they do.... Still others might need to temporarily run 2 dif BOINcs and swap between them for their various projects, or skip one or more projects for a time.

---

thx. Hope they get things up to date ;)

---

Caspr said

Just read a post over at CPDN and they also recommend the 5.10.xx downgrade because of some issues with the 6.2.xx version

Caspr, you probably read this CPDN News thread or this one.

Just yesterday I went around the 5 CPDN forums deleting that announcement dated 6 Aug about the public release of that first general release BOINC6 version. In the first news thread I linked to I seem to have accidentally reposted my announcement instead of deleting it, so sorry about that. I've now removed that old announcement which is obsolete.

You'll see that further down the same news threads there's a much more recent announcement about BOINC6 giving useful links to information about it eg in the BOINC FAQs.

Sorry about that confusion. The problem that occurred with that first BOINC6 public release version only affected some computers. This bug was fixed in the next public release.

On CPDN we are recommending the current versions of BOINC6. But we do recommend that members should read the FAQ about the installation modes before they install it. And stick with BOINC 5.10.45 if they don't want to upgrade to BOINC6 at the moment.

If anyone wants to run WUs that turn out to be incompatible with BOINC6, just go back to 5.10.45 until the project's produced BOINC6-compliant applications.

Well, regardless of how good BOINC version 6 is, after dropping back to 5.10.45 problems with SETI@home work units cleared up. Now that we have work from LHC, I see that earlier problems there seem to have cleared up also. (Out of the 12 I got, created on the 11th, only one was cancelled by the server.)

The work keeps coming. Wonder how long it will last?

I\'m a bit confused here. I upgraded to 6.2.18 since I was having some vista issues with 5.x, and as we speak it seems to be happily churning on LHC WU\'s (I\'ve even completed a few and gotten credits for them). What exactly is the problem with 6.2.x?

I'm a bit confused here. I upgraded to 6.2.18 since I was having some vista issues with 5.x, and as we speak it seems to be happily churning on LHC WU's (I've even completed a few and gotten credits for them). What exactly is the problem with 6.2.x?

Some people have been having problems as reported here. If 6.2.x is working okay for you, then I wouldn't worry about it.

Hope this helps

Michael