LHC@home

I've been trying to merge one of my boxes and it won't let me!! help!!! Am I doing something wrong? I connect the dots and follow instructions well, and keep getting an "cannot connect" page on my browser?? DUH???

---

A clear conscience is usually the sign of a bad memory

I've been trying to merge one of my boxes and it won't let me!! help!!! Am I doing something wrong? I connect the dots and follow instructions well, and keep getting an "cannot connect" page on my browser?? DUH???

Have you tried since the site came back on just now?

I had that happen the other day when the server was down and it didn't work but when it came back on it worked first try.

I was just checking here and figured since nobody was on the boards yet that it must have just came back.

---

Volunteer Mad Scientist For Life

Appologies...
Database problems over the weekend.
Quick fix inplace and working on permenant fix.

Alex

Appologies...
Database problems over the weekend.
Quick fix inplace and working on permenant fix.

Alex

Yes,I figured it was a weekend thing and decided since it is even monday morning here (PT) that I better get on here and see if the site was running again and check the status.

Good morning Alex (PT)

---

Volunteer Mad Scientist For Life

Nope, still not working. Getting the same thing, just tryed again.

---

A clear conscience is usually the sign of a bad memory

Nope, still not working. Getting the same thing, just tryed again.

If there is a big enough difference in the version of boinc that you used on the old machine ID and the new machine ID, it may not merge. They've done some updates with the way BOINC identifies the processors in the computer, therefore the server may not recognize the machine as being the same one.

---

Thanks Jim, but I pretty much stay on top up of keeping my managers updated. That particular box hasen't even done a wu yet and it's listed.....I think, if I remember right, 187 times! Would it work if I detached that box and tryed to reattach it? And do you know if I could take care of this through bam or is bam the problem?
OK, the only way I can do it is to detatch that box 187 times! I'll just wait for someone to fix the problem!

---

A clear conscience is usually the sign of a bad memory

Alex, I'm getting this message when I try to merge one of my boxes...




WARNING: Cannot modify header information - headers already sent by(output started at/srv/httpd/lhcathome.cern.ch/lhcathome/html/inc/util.inc:105) in/srv/httpd/lhcathome.cern.ch/lhcathome/html/inc/util.inc on line 98


Any info would be great! Thanks!

---

A clear conscience is usually the sign of a bad memory

Thanks Jim, but I pretty much stay on top up of keeping my managers updated. That particular box hasen't even done a wu yet and it's listed.....I think, if I remember right, 187 times! Would it work if I detached that box and tryed to reattach it? And do you know if I could take care of this through bam or is bam the problem?
OK, the only way I can do it is to detatch that box 187 times! I'll just wait for someone to fix the problem!

You may be a victim of the ghost host problem. I know it has been discussed in other threads. I'm not familiar with the problem other than to know that it exists. Sorry I can't be of more help.

Jim

---

Thanks Jim, but I pretty much stay on top up of keeping my managers updated. That particular box hasen't even done a wu yet and it's listed.....I think, if I remember right, 187 times! Would it work if I detached that box and tryed to reattach it? And do you know if I could take care of this through bam or is bam the problem?
OK, the only way I can do it is to detatch that box 187 times! I'll just wait for someone to fix the problem!

You may be a victim of the ghost host problem. I know it has been discussed in other threads. I'm not familiar with the problem other than to know that it exists. Sorry I can't be of more help.

Jim

The solution is to merge all of the hosts on the web site. Once you have one copy of it left you need to edit the client_state.xml file on that host and change the hostID to match the one remaining on the web. There are more detailed instructions here somewhere.

---

BOINC WIKI

BOINCing since 2002/12/8

Thanks Jim, but I pretty much stay on top up of keeping my managers updated. That particular box hasen't even done a wu yet and it's listed.....I think, if I remember right, 187 times! Would it work if I detached that box and tryed to reattach it? And do you know if I could take care of this through bam or is bam the problem?
OK, the only way I can do it is to detatch that box 187 times! I'll just wait for someone to fix the problem!

You may be a victim of the ghost host problem. I know it has been discussed in other threads. I'm not familiar with the problem other than to know that it exists. Sorry I can't be of more help.

Jim

The solution is to merge all of the hosts on the web site. Once you have one copy of it left you need to edit the client_state.xml file on that host and change the hostID to match the one remaining on the web. There are more detailed instructions here somewhere.

The problem is that they don't STAY fixed. If anything causes the host id to split again, it goes off into never never land again.

---

BOINC WIKI

Thanks Jim, but I pretty much stay on top up of keeping my managers updated. That particular box hasen't even done a wu yet and it's listed.....I think, if I remember right, 187 times! Would it work if I detached that box and tryed to reattach it? And do you know if I could take care of this through bam or is bam the problem?
OK, the only way I can do it is to detatch that box 187 times! I'll just wait for someone to fix the problem!

You may be a victim of the ghost host problem. I know it has been discussed in other threads. I'm not familiar with the problem other than to know that it exists. Sorry I can't be of more help.

Jim

The solution is to merge all of the hosts on the web site. Once you have one copy of it left you need to edit the client_state.xml file on that host and change the hostID to match the one remaining on the web. There are more detailed instructions here somewhere.

The problem is that they don't STAY fixed. If anything causes the host id to split again, it goes off into never never land again.

I also had a host with no credits yet and 200+ ghost-hosts. Merging them took some trouble, 'select all' didn't work but selecting say 30 at a time and then merging them went OK. And do remember to merge the old ones with the latest one, not the other way around (I found out the hard way)...
The host is now happily in the DB all by itself, just checked and still the ghost-hosts are gone. The host was effectively retired by the way (hostname changed after owner had W*dows reinstalled), I'm gonna delete it soon.

I also had a host with no credits yet and 200+ ghost-hosts. Merging them took some trouble, 'select all' didn't work but selecting say 30 at a time and then merging them went OK. And do remember to merge the old ones with the latest one, not the other way around (I found out the hard way)...
The host is now happily in the DB all by itself, just checked and still the ghost-hosts are gone. The host was effectively retired by the way (hostname changed after owner had W*dows reinstalled), I'm gonna delete it soon.



@WimTea, WOW! THANKS! I never would have thought of that but it worked GREAT!
First I merged 10 then 20 and then all! What can I say I'm lazy!:)

---

A clear conscience is usually the sign of a bad memory

Thanks Jim, but I pretty much stay on top up of keeping my managers updated. That particular box hasen't even done a wu yet and it's listed.....I think, if I remember right, 187 times! Would it work if I detached that box and tryed to reattach it? And do you know if I could take care of this through bam or is bam the problem?
OK, the only way I can do it is to detatch that box 187 times! I'll just wait for someone to fix the problem!

You may be a victim of the ghost host problem. I know it has been discussed in other threads. I'm not familiar with the problem other than to know that it exists. Sorry I can't be of more help.

Jim

The solution is to merge all of the hosts on the web site. Once you have one copy of it left you need to edit the client_state.xml file on that host and change the hostID to match the one remaining on the web. There are more detailed instructions here somewhere.

The problem is that they don't STAY fixed. If anything causes the host id to split again, it goes off into never never land again.

I also had a host with no credits yet and 200+ ghost-hosts. Merging them took some trouble, 'select all' didn't work but selecting say 30 at a time and then merging them went OK. And do remember to merge the old ones with the latest one, not the other way around (I found out the hard way)...
The host is now happily in the DB all by itself, just checked and still the ghost-hosts are gone. The host was effectively retired by the way (hostname changed after owner had W*dows reinstalled), I'm gonna delete it soon.

I just noted an interesting phenomon. I seem to have stopped getting ghost clients about the end of May. I believe that there may be a bug fix in the most recent version of the client.

BTW, you can merge something over 100 at a time.

---

BOINC WIKI

I just noted an interesting phenomon. I seem to have stopped getting ghost clients about the end of May. I believe that there may be a bug fix in the most recent version of the client.

BTW, you can merge something over 100 at a time.




I just merged 10 then 20 and then all.....I had over 180 so you can merge at least 150 at a time.

---

A clear conscience is usually the sign of a bad memory

I just noted an interesting phenomon. I seem to have stopped getting ghost clients about the end of May. I believe that there may be a bug fix in the most recent version of the client.

Thats good to hear.

BTW, you can merge something over 100 at a time.

When i had to do it i believe my best was 136 at a time.

Larry

---

Hello, I recently re-connected to the project after new-installing my Windows. Since it is still the same Machine, I like to merge the two computers in my account. When I tried to do that, there was no pc listed after selecting "merge this computer" in the window of the old entry. So I was not able to select the other one to merge them. Same at Einstein, posted there too. Any idea?

Happy crunching, Christoph

---

Christoph

Well since it is on both I assume it is a BOINC issue not and LHCathome specific issue
BOINC wiki says:

Merging Duplicate Host Records

Other actions can also give rise to multiple Host IDs, including:

* Detaching and re-attaching to a Project.
* Running a new Version of the BOINC Client Software that changes the way that CPU names are identified. (cannot be merged)
* Adding a service pack update to Microsoft Windows�. (cannot be merged)
* Adding an additional Operating System to the computer and using multi-boot (e.g.: Microsoft Windows� and Linux).
* An update to the BIOS that changes the CPU identification. (cannot be merged)
* Extreme Over-Clocking that the CPU is mis-identified. (cannot be merged)
* Attempting to run the BOINC Client Software in Windows 2000� mode under Microsoft Windows XP�
* Significant changes to the computer's hardware configuration (CPU chip, adding Physical Memory, etc.) (cannot be merged)

I think it is one of the two highlighted options as the listings under "CPU types" are slightly different.

Hello, I recently re-connected to the project after new-installing my Windows. Since it is still the same Machine, I like to merge the two computers in my account. When I tried to do that, there was no pc listed after selecting "merge this computer" in the window of the old entry. So I was not able to select the other one to merge them. Same at Einstein, posted there too. Any idea?

What version of BOINC did you have before?
From your results, it appears it was an old one. Since BOINC 5.4.x (I think) the CPU Type now has more info (and even more in BOINC 5.8.x), so that's probably what is preventing the merger.
You really only have one option, wait for the results to get deleted and then delete the host.

(Or maybe in the future some newer server software will take care better of this problem)

---

Professor Desty Nova
Researching Karma the Hard Way

I first also thought it's a problem with the CPU ID. Until I merged successful with SETI and ufluids. Ok, maybe it's depending to the server - Version? No idea how to find out which Version is in use by the projects.

@Professor Desty Nova: As you can see, there are a few month between the last contact and now. Had have a harddrive crash, so since I did not have the old files, I downloaded and installed the latest version. Which it had been on the old disk, I don't remember.

Christoph

---

Christoph