LHC@home

The recommended BOINC core client no longer works with your project.

I know you probably have lots of important work to do, but hopefully you could get around to upgrading (or at least modifying) the server back end to support version 5 clients.

Thanks. :)

---

Anybody there in Genève ?

---

Best greetings from Belgium
Thierry

<blockquote>Anybody there in Genève ?
</blockquote>

Chrulle was last heard of in Denmark, heading north...

---

Gaspode the UnDressed
http://www.littlevale.co.uk

Surely it can't be that hard to patch the servers to accept the V5 clients. Is it a big and complicated job to upgrade or something? all the other Boinc projects upgraded ages ago.

---

keep boinc cc4.72 on one computer, run lhc until the project upgrades or runs out of work. if the latter, you can still run other projects with 4.72. best of both worlds.

When Predictor upgraded, the site was down for the better part of 4 days. A server side upgrade is always trickier than a client upgrade.

Guy

---

[img src="http://www.boincstats.com/signature/user_10138.gif"]

<blockquote>When Predictor upgraded, the site was down for the better part of 4 days. A server side upgrade is always trickier than a client upgrade.
</blockquote>

Apples and oranges. There is a brief patch available to allow V5 clients to talk to the V4 server. That would take minimal work, from what I understand.

What Predictor did was upgrade to the V5 server code. That would be a more substantial job.

---

Well, i am back in switzerland. Strangely the weather was much better in Denmark.

All that the "talk" patch does is allow version 5 clients to not fail when connecting, but they will still not get any jobs, so it is pretty useless.

I am in the process of installing the new server version on the alpha test server.
It is always a lot trickier than one would think, for now i have discovered that i am obviously not supposed to use the stable branch of cvs because that is only stable for the client and not for the server. Then i found out that i needed newer versions of automake and -conf.

Now i am ready to upgrade the database which i hope will not crash everything but we shall see. :-)

If everything works out we will install v.5 on the normal server soon.

---

Chrulle
Research Assistant &amp; Ex-LHC@home developer
Niels Bohr Institute

woohoo!

Thank you for the update Chrulle, and welcome back.

---

Indian Summer in Denmark has broken. Raining today, outlook for the next 7 days, wet, windy, typical Denmark weather in fact. Had our first frosts this week as well, more forecast. Was good while it lasted.

Will be good to have v5 support. I only run the versions I do now because of LHC. The fixes are becoming mandatory at some of the projects, so a crunch point is not far away.

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

<blockquote>Indian Summer in Denmark has broken. Raining today, outlook for the next 7 days, wet, windy, typical Denmark weather in fact. Had our first frosts this week as well, more forecast. Was good while it lasted.

Will be good to have v5 support. I only run the versions I do now because of LHC. The fixes are becoming mandatory at some of the projects, so a crunch point is not far away.</blockquote>

You think Denmark's weather is bad? You should try living in Scotland for a while. :-d

---

It's varied from project to project. Predictor was down for sometime while upgrading, whereas Rosseta was back up latter that day and in business.

Anyhow, 5.2.2 has just become the recommended version recently, and sounds as if the servers will be ready in the near future. A note on the projects front page would be good when it's done, so users can see this. ;)

In the interum, I've got 5.2.1 on my home PC, and should upgrade to 5.2.2. It's been mid-terms week, so I've been swamped :D I pulled some LHC WUs at school, and a couple have got processed this week (they're still under 4.43 for Linux). BOINC Manager under 4.43/Linux does seem to have a few issues however, as when I shut down X Windows it leaves error messages about bad Windows parameters and what not. If some others aren't seeing this however, it might be some interaction with BOINC and Slackware 10.2. That said, other then error messages about bad parameters in the code and what not, it does do what it's supposed to, though the graphics in LHC won't display as they do on Windows. Haven't had time to search that out to see if it's just an under Linux thing, or if perhaps there's something going on, on my boxes there. To much in my own class projects there, to spend time on something of lower priority such as this...

---

version 5 should be up and running on the alpha site, so if we have any v.5 client users here who used to do alpha reattach and tell me how it works.

---

Chrulle
Research Assistant &amp; Ex-LHC@home developer
Niels Bohr Institute

I just upgraded to BOINC Ver 5.2.2 but can't attach to LHC project :( getting
"10/21/2005 6:35:42 AM||Missing account key"
MrJeep

---

<blockquote>version 5 should be up and running on the alpha site, so if we have any v.5 client users here who used to do alpha reattach and tell me how it works.
</blockquote>
Hello Chrulle,

This might be of an interest for you.

Best regards,
Thierry

<blockquote>
You think Denmark's weather is bad? You should try living in Scotland for a while. :-d</blockquote>

The first thing I learned during my holiday in Scotland was:
"There's no bad weather, only bad clothing"

Same as in Jamaica, down there they have *no* rain, it's simply liquid sunshine :-))

scsimodo

---

Yeah, when I reinstalled my comp following the upgrade, I had the reverse of what they describe in that thread. Tried Account mgr to add projects, and even with a password, they wouldn't attatch. Had to downgrade, add, and then re-upgrade. Now SETI won't let people attach with the account key anymore, hmm...

As to testing it on LHC Alpha, I'm not able to as I don't have access. Perhaps someone else does who can get ahold of churle on this...

---

<blockquote>Now SETI won't let people attach with the account key anymore, hmm...</blockquote>
This problem is meanwhile under investigation as attaching using the account key should work. The issue is to be seen as a small 'bug' of Boinc v5.2.2.

---

Best greetings from Belgium
Thierry

Bionics works great with Einstein@Home - LHC@home and Rosetta@home and Seti@home and Predictor@home all need to talk to the Einstein developers or managers and find out what they are doing so well. I've virtually had zero problems from Einstein@home since day one. The rest of the Bionic locations need to take a lesson from these guys/gals!

---

BOINC works very well with all projects. I've had no problems with BOINC (5.2.2) for ages and the new attach to project wizard works extremely easily for both new accounts and re-attaching with an existing account.

Live long and crunch.

---

Paul
(S@H1 8888)
BOINC/SAH BETA