LHC@home

There is a problem with several projects where the system creates a new host id every time the user's computer connects to the project. From my reading of the thread on the Rosetta forum ( http://www.boinc.bakerlab.org/rosetta/forum_thread.php?id=1669 ), a patch can be installed to fix this.

Is it possible to install the patch on the LHC servers?

At least we can merge hosts on LHC in the meantime - Rosetta has the merge facility turned off until the Autumn :-)

---

There is a problem with several projects where the system creates a new host id every time the user's computer connects to the project. From my reading of the thread on the Rosetta forum ( http://www.boinc.bakerlab.org/rosetta/forum_thread.php?id=1669 ), a patch can be installed to fix this.

Is it possible to install the patch on the LHC servers?

At least we can merge hosts on LHC in the meantime - Rosetta has the merge facility turned off until the Autumn :-)

There are no Admins at LHC at present. An update to the server side code is unlikely for the time being.

The problem seems to relate to those people using account managers like BAM. Maybe one should stick with the manual way of doing things until the bugs are ironed out and all the projects are updated.

---

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

The problem seems to relate to those people using account managers like BAM. Maybe one should stick with the manual way of doing things until the bugs are ironed out and all the projects are updated.

No, maybe this project should stop taking the crunching community for granted and get someone in there to work on things that need doing. I don't think that is asking too much in return. Beside, account managers have been in the works for the better part of a year and they should not have been taken unawares.

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

The problem seems to relate to those people using account managers like BAM. Maybe one should stick with the manual way of doing things until the bugs are ironed out and all the projects are updated.

No, maybe this project should stop taking the crunching community for granted and get someone in there to work on things that need doing. I don't think that is asking too much in return. Beside, account managers have been in the works for the better part of a year and they should not have been taken unawares.

And maybe the crunchers themselves should be more realistic. BOINC has had release after release of bug-ridden software - both server and client. It comes as no surprise that account managers don't work. With the ever increasing number of projects is it realistic to expect every project to update its servers immediately to introduce new features that it doesn't need and which don't work?

And just to make matters worse we have this 'open-source' ideal, with any number of individuals of varying levels of competence producing optimised 'this' and high-performance 'that', and add-ons that work only when they feel like it.

What BOINC needs is someone to take real control of quality assurance for client, server, and add-ons. Then we might see fewer of these problems, and less whining from the inconvenienced participants.

I have great respect for Rom Walton and what he has achieved. The time has come to recognise the scale of the project and apply appropriate resources.

If David Anderson isn't careful the whole edifice he has built will sink, maybe deservedly, into the swamp.


...and that's my rant for the week ;-)

---

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

Account managers do work I'm attached to several other projects and the account mangaer works correctly for them. So don't go blaming the inadequacies of LHC on the account managers. Oh and I think there is a brown spot forming on your nose in regard to this project!

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

Account managers do work I'm attached to several other projects and the account mangaer works correctly for them. So don't go blaming the inadequacies of LHC on the account managers. Oh and I think there is a brown spot forming on your nose in regard to this project!

"Look not for the splinter in my eye, but the plank in your own"

Have a good weekend, Steve :)

---

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

Have a good weekend, Steve :)

Thanx, you too. And the last sentence of my last post was supposed to come across as good natured gentle ribbing ;)

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

I just looked at my computers and was alarmed to see 18+ of the same computers all formed within the past 2 days...

I've had the same problem over at xtremlab, they are working on a patch to fix this...

None of this was occuring before I joined BAM account manager, I've had too many problems with it so I've discontinued its use...

---

I also having the same issue that my computers are listed again and again, Iam using BAM also, but havent not seen this issue on other project. I check most of them and there isnt a issue. So is it a LHC issue or a BOINC issue, or BAM, does anyone knows?

---

I also having the same issue that my computers are listed again and again, Iam using BAM also, but havent not seen this issue on other project. I check most of them and there isnt a issue. So is it a LHC issue or a BOINC issue, or BAM, does anyone knows?

The problem is that the LHC servers are running out dated Boinc software. And to make matters worse, there is no one there to do the upgrade! From what I can see there have been no updates since last summer. They even list boinc v4.45 as the latest version on the d/l page.

And I have decided that it is no longer my responsibility to keep merging hosts to try and keep the database small. Wonder how many hosts I will have by the time they fix it or they run out of space for all these redundant hosts?
:)

P.S. If they like us to do the work for them the least they can do is keep the infrastructure up to date. Just my opinion!

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

The BOINC version installed on my machine here is 5.2.13.

I don't use anything else, and it manages all my projects adequately....

---

must not be BAM causing the duplicate hosts, i have some machines that havent been added to BAM, but still is creating duplicate host on LHC, and these hosts are using BOINC 5.13. O well hopefully it will be fixed in 2006. LOL!

imho - this problem (or any other i'm aware of) is not on any other project because of (or in spite of) bam. so we're left we a few choices:

1: don't use an account manager
2: wait for lhc to upgrade the server software
3: wait for lhc to have a more host entries than they have server space
4: don't work for lhc (which isn't hard since there's so little work anyhow)

---

I don't believe that BAM in and of itself is a culprit, either. Your #2 choice is the best one, though.

---

And #2 won't likely happen until #3 happens.
And from looking at my host list, which i stopped merging 2 weeks ago, it looks like we are gaining ~100,000 hosts every two weeks, lol.

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

I figured out what the problem is, at least in my case and how to correct it. This may work for you too. In my case the computer host ID # is not getting passed to the client.

1) You can verify that this is your problem too by checking your client_state.xml file. Look for the section for LHCathome then find the line that states the <hostid>xxxxxx</hostid>. If you have value of 0 for the ID# then this is what causes it to keep making new hosts. Now exit the text editor without saving!
2) If you want to fix this shut down Boinc.
3) Go to your account page here at the project and click on View computers then write down the host number from the most recent one there.
4) Go back and open client_state.xml.file with a text editor and replace the 0 with the number that you wrote down.
5) Save the file.
6) Restart Boinc

Hope this helps, it worked for me.
Now I have to find something else to do on this boring rainy saturday. This did not take but a few minutes to figure out, lol.
:)

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

You couldn't have thought of this two or three weeks ago, could you?

Fixed my two host generators.

Good, clear, easy to follow tip!

Thanks Buckets!

---

You couldn't have thought of this two or three weeks ago, could you?

Fixed my two host generators.

Good, clear, easy to follow tip!

Thanks Buckets!

You are welcome. One small point to make. Hope you made sure to use different numbers for the two computers by checking the details to make sure they match the computer. Forgot about people that have more than one computer when making the instructions.
:)

---

98SE XP2500+ @ 2.1 GHz Boinc v5.8.8

yup.

did a merge of all the copies for each computer and used the appropriate result for each one.

---

Great.
It worked for me too. I also noticed that my team was empty and fixed it also.

Thanks for the tip.

---

I am Homer of Borg. Prepare to be ...ooooh donuts!