Two machines, one Computer ID

Donald A. Tevault
Donald A. Tevault
Joined: 17 Feb 06
Posts: 439
Credit: 73,516,529
RAC: 0
Topic 193816

Here's another of my famous mysteries. . .

Here, what seems to be one machine with four tasks is actually two machines that registered under the same Computer ID. They're both identical machines that I set up with Debian 4.1. I assigned different hostnames to both, but that didn't make a difference.

When I attached the second of these to the project, it caused the workunits from the first one to show a "Client detached" status, even though the workunits are still running on both machines.

Both are running BOINC 5.8.16, the newest version that will run with Debian.

I've set up identical machines with the same operating system before, but I've never had this happen.

Any clues?

Mike Hewson
Mike Hewson
Moderator
Joined: 1 Dec 05
Posts: 6,551
Credit: 289,340,552
RAC: 98,488

Two machines, one Computer ID

Quote:

Here's another of my famous mysteries. . .

Here, what seems to be one machine with four tasks is actually two machines that registered under the same Computer ID. They're both identical machines that I set up with Debian 4.1. I assigned different hostnames to both, but that didn't make a difference.

When I attached the second of these to the project, it caused the workunits from the first one to show a "Client detached" status, even though the workunits are still running on both machines.

Both are running BOINC 5.8.16, the newest version that will run with Debian.

I've set up identical machines with the same operating system before, but I've never had this happen.

Any clues?


I think that's a server side flub. Bernd?

Cheers, Mike.

I have made this letter longer than usual because I lack the time to make it shorter ...

... and my other CPU is a Ryzen 5950X :-) Blaise Pascal

Donald A. Tevault
Donald A. Tevault
Joined: 17 Feb 06
Posts: 439
Credit: 73,516,529
RAC: 0

RE: RE: Here's another of

Message 83616 in response to message 83615

Quote:
Quote:

Here's another of my famous mysteries. . .

Here, what seems to be one machine with four tasks is actually two machines that registered under the same Computer ID. They're both identical machines that I set up with Debian 4.1. I assigned different hostnames to both, but that didn't make a difference.

When I attached the second of these to the project, it caused the workunits from the first one to show a "Client detached" status, even though the workunits are still running on both machines.

Both are running BOINC 5.8.16, the newest version that will run with Debian.

I've set up identical machines with the same operating system before, but I've never had this happen.

Any clues?


I think that's a server side flub. Bernd?

Cheers, Mike.

Yeah, appears so. I was thinking about compiling a custom kernel for one machine, just so it would have something different to register. But, I'll wait to hear from Bernd and crew before I do that. It could be that I've uncovered a bug in the server software.

Mike Hewson
Mike Hewson
Moderator
Joined: 1 Dec 05
Posts: 6,551
Credit: 289,340,552
RAC: 98,488

RE: Yeah, appears so. I

Message 83617 in response to message 83616

Quote:
Yeah, appears so. I was thinking about compiling a custom kernel for one machine, just so it would have something different to register. But, I'll wait to hear from Bernd and crew before I do that. It could be that I've uncovered a bug in the server software.

Yup, it's a weirdo all right. I've just emailed the mod's list on that, stay tuned.

Cheers, Mike.

I have made this letter longer than usual because I lack the time to make it shorter ...

... and my other CPU is a Ryzen 5950X :-) Blaise Pascal

John McLeod VII
John McLeod VII
Moderator
Joined: 10 Nov 04
Posts: 547
Credit: 632,255
RAC: 0

RE: Here's another of my

Quote:

Here's another of my famous mysteries. . .

Here, what seems to be one machine with four tasks is actually two machines that registered under the same Computer ID. They're both identical machines that I set up with Debian 4.1. I assigned different hostnames to both, but that didn't make a difference.

When I attached the second of these to the project, it caused the workunits from the first one to show a "Client detached" status, even though the workunits are still running on both machines.

Both are running BOINC 5.8.16, the newest version that will run with Debian.

I've set up identical machines with the same operating system before, but I've never had this happen.

Any clues?


Did you copy the client_state.xml file during the setup of the newer of these computers?

Did you copy the account_*.xml files?

Donald A. Tevault
Donald A. Tevault
Joined: 17 Feb 06
Posts: 439
Credit: 73,516,529
RAC: 0

RE: RE: Here's another of

Message 83619 in response to message 83618

Quote:
Quote:

Here's another of my famous mysteries. . .

Here, what seems to be one machine with four tasks is actually two machines that registered under the same Computer ID. They're both identical machines that I set up with Debian 4.1. I assigned different hostnames to both, but that didn't make a difference.

When I attached the second of these to the project, it caused the workunits from the first one to show a "Client detached" status, even though the workunits are still running on both machines.

Both are running BOINC 5.8.16, the newest version that will run with Debian.

I've set up identical machines with the same operating system before, but I've never had this happen.

Any clues?


Did you copy the client_state.xml file during the setup of the newer of these computers?

Did you copy the account_*.xml files?

No, I didn't. I did a clean install of BOINC on both machines.

Donald A. Tevault
Donald A. Tevault
Joined: 17 Feb 06
Posts: 439
Credit: 73,516,529
RAC: 0

RE: RE: Here's another of

Message 83620 in response to message 83618

Quote:
Quote:

Here's another of my famous mysteries. . .

Here, what seems to be one machine with four tasks is actually two machines that registered under the same Computer ID. They're both identical machines that I set up with Debian 4.1. I assigned different hostnames to both, but that didn't make a difference.

When I attached the second of these to the project, it caused the workunits from the first one to show a "Client detached" status, even though the workunits are still running on both machines.

Both are running BOINC 5.8.16, the newest version that will run with Debian.

I've set up identical machines with the same operating system before, but I've never had this happen.

Any clues?


Did you copy the client_state.xml file during the setup of the newer of these computers?

Did you copy the account_*.xml files?

I just looked in the client_state.xml files for both machines. They both have different CPUID numbers, so you would think that everything would work. The only thing I see that might keep everything from working properly, is that the older BOINC clients have a bad habit of registering all machines with a hostname of "localhost", regardless of how I set up the machine. (Both of these are "localhost", although I set up one machine as "debian-2" and the other as "debian-3".) That's never been a problem before, probably because the other two machines on which I have to run an older client both have different versions of the Linux kernel.

Anyway, I'll keep things as they are for a while longer, in case anyone has more questions. Then, I'll either compile a custom kernel for one machine to see if that helps, or install some other Linux distro that can run a newer BOINC client.

Gundolf Jahn
Gundolf Jahn
Joined: 1 Mar 05
Posts: 1,079
Credit: 341,280
RAC: 0

RE: I just looked in the

Message 83621 in response to message 83620

Quote:
I just looked in the client_state.xml files for both machines. They both have different CPUID numbers, so you would think that everything would work. The only thing I see that might keep everything from working properly, is that the older BOINC clients have a bad habit of registering all machines with a hostname of "localhost", regardless of how I set up the machine. (Both of these are "localhost", although I set up one machine as "debian-2" and the other as "debian-3".) That's never been a problem before, probably because the other two machines on which I have to run an older client both have different versions of the Linux kernel...


I vaguely remember a post somewhere about that naming problem. If I recall correctly, it depends on the sequence of "localhost" and "real hostname" in the etc/hosts file (behind 127.0.0.1).

Hope that helps.

Gruß,
Gundolf

Computer sind nicht alles im Leben. (Kleiner Scherz)

Donald A. Tevault
Donald A. Tevault
Joined: 17 Feb 06
Posts: 439
Credit: 73,516,529
RAC: 0

RE: RE: I just looked in

Message 83622 in response to message 83621

Quote:
Quote:
I just looked in the client_state.xml files for both machines. They both have different CPUID numbers, so you would think that everything would work. The only thing I see that might keep everything from working properly, is that the older BOINC clients have a bad habit of registering all machines with a hostname of "localhost", regardless of how I set up the machine. (Both of these are "localhost", although I set up one machine as "debian-2" and the other as "debian-3".) That's never been a problem before, probably because the other two machines on which I have to run an older client both have different versions of the Linux kernel...

I vaguely remember a post somewhere about that naming problem. If I recall correctly, it depends on the sequence of "localhost" and "real hostname" in the etc/hosts file (behind 127.0.0.1).

Hope that helps.

Gruß,
Gundolf

Sounds like a possibility. I'll check on that when I get the chance.

Metod, S56RKO
Metod, S56RKO
Joined: 11 Feb 05
Posts: 135
Credit: 812,185,280
RAC: 68,185

RE: They're both identical

Quote:
They're both identical machines that I set up with Debian 4.1.

snip

Quote:
Both are running BOINC 5.8.16, the newest version that will run with Debian

Huh, BOINC software as provided by Berkeley and compiled for Ubuntu, runs fine on my 4.1 (Lenny) boxes. 3.1 (sarge), however, is a different story. It is not too difficult to compile your own BOINC client, the only problem is with version of libcurl on sarge. As I don't use proxy (old libcurl had problems with some of proxy implementations) I simply decided to hack autoconf to require lower version than available. My sarge systems happily run 6.2.14 ATM.

Metod ...

Donald A. Tevault
Donald A. Tevault
Joined: 17 Feb 06
Posts: 439
Credit: 73,516,529
RAC: 0

RE: RE: They're both

Message 83624 in response to message 83623

Quote:
Quote:
They're both identical machines that I set up with Debian 4.1.

snip

Quote:
Both are running BOINC 5.8.16, the newest version that will run with Debian

Huh, BOINC software as provided by Berkeley and compiled for Ubuntu, runs fine on my 4.1 (Lenny) boxes. 3.1 (sarge), however, is a different story. It is not too difficult to compile your own BOINC client, the only problem is with version of libcurl on sarge. As I don't use proxy (old libcurl had problems with some of proxy implementations) I simply decided to hack autoconf to require lower version than available. My sarge systems happily run 6.2.14 ATM.

My boxes are running Debian Etch, and they don't have a new enough version of glibc to run the newer BOINC clients.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.