Unable to merge computers
26 Feb 2006 10:35:57 UTC
Topic 190831
(moderation:
For last few days I'm unable to merge computers. The problem is that clicking on merge this computer doesn't give me any possibilities.
I just can't see why these two computers are not treated mergeable.
edit: well, the cache size reported is different, could this be it?
edit 2: nope, that wasn't it
Metod ... 
Unable to merge computers
)
There is open WUs on them both. This is why.
RE: There is open WUs on
)
If this is it then it's a new policy. I used to be able to merge hosts even with open WUs before.
Metod ...
RE: There is open WUs on
)
That's when you try to delete a host. Merging two hosts doesn't care if they have work units in the list, yes or no.
Metod, the only thing way off that I see is the benchmark on the new hostID. Very low for a P4 3.6GHz. So you may want to try to re-run the benchmarks, then Update on the Einstein project and then try to merge them.
...deleted wrong post...
)
...deleted wrong post...
The same problem was reported
)
The same problem was reported at S@H.
seti thread
Solution was a MySQL update.
Michael
Team Linux Users Everywhere
RE: For last few days I'm
)
It's because one host reported to the scheduler AFTER the other host was created. See the last four lines of this function:
// return true if it's possible that the two host records // correspond to the same host // function hosts_compatible($host1, $host2) { // we screwed around with Intel processor names, // so count them as compatible if both contain "Intel" and "Pentium", // and don't have conflicting clock rate info // $p1 = "$host1->p_vendor $host1->p_model"; $p2 = "$host2->p_vendor $host2->p_model"; if (strstr($p1, "Pentium") && strstr($p1, "Intel") && strstr($p2, "Pentium") && strstr($p2, "Intel") ) { $g1 = ghz($p1); $g2 = ghz($p2); if ($g1 && $g2 && ($g1!=$g2)) return false; } else { if ($host2->p_vendor != $host1->p_vendor) return false; if ($host2->p_model != $host1->p_model) return false; } if ($host2->os_name != $host1->os_name) return false;// one host must strictly precede the other
//
if ($host1->rpc_time create_time) return true;
if ($host2->rpc_time create_time) return true;
return false;
}
Director, Einstein@Home
RE: It's because one host
)
That would explain why I can't merge my two installations on obiwan.
Does it matter if we delete the old hosts or just leave them cluttering up the database?
Ben
RE: It's because one host
)
Bruce,
Is there any chance that some time in the future the critera may not be so tight? I have a tendency to upgrade CPU's on my PC's and sometimes OS's.
Or should I wonder over to the BOINC boards and hound them there?
It just stikes me as a bit strange that I can't upgrade a whole PC and keep the results flowing to the PC with the same name.
Join the #1 Aussie Alliance on Einstein
RE: Bruce, Is there any
)
As long as you stick to the same brand of OS (so that the same BOINC binary still runs), then you should be able to replace all of the hardware and still use the same host ID. And continue your work for projects as well.
The only real problem (which happens to me from time to time) is if the machine is not that stable. If it crashes and corrupts the client_state.xml, then BOINC will re-attach to projects, creating new host IDs for the same host. If you manage to change hardware at the same time (eg. install faster CPU), then you're unable to merge the two computers.
In my particular case, as I was uanble to merge the two hosts, I somehow reconstructed client_state.xml of the older host registration in order to make host data of both installations identical (I did temporarily change CPU with a faster one). I was not aware of timing constraints :(
After that I was able to finish all outstanding work allocated to the 'old' host. The only reason I'd rather merge the hosts instead of just deleting the old one after all the tasks are out of database is to keep the host credit.
One can't have it all, can (s)he?
[edit] typoes
Metod ...
RE: As long as you stick to
)
I switched from Windows to Linux. No problem. Just save/restore the client_state.xml
Okay, you cannot continue unfinished WU's ... this does not work.