3 of my machines have developed neuroses :) over the last months.

It seems they change ID intermittently during a shutdown/reboot. Not every time though (~10-20%)

All 3 machines are running 6.10.58 but different OS (1x Win7-64, 2x XP-32)

I have not found any other threads about this problem so is it just me?

---

Flying high with Team Sicituradastra.

3 of my machines have developed neuroses :) over the last months.

It seems they change ID intermittently during a shutdown/reboot. Not every time though (~10-20%)

All 3 machines are running 6.10.58 but different OS (1x Win7-64, 2x XP-32)

I have not found any other threads about this problem so is it just me?

I have seen the ID's change if the IP of that computer changes. If you are using DHCP and the lease expires which causes the machine to get a new IP.

---

3 of my machines have developed neuroses :) over the last months.

It seems they change ID intermittently during a shutdown/reboot. Not every time though (~10-20%)

All 3 machines are running 6.10.58 but different OS (1x Win7-64, 2x XP-32)

I have not found any other threads about this problem so is it just me?

I have seen the ID's change if the IP of that computer changes. If you are using DHCP and the lease expires which causes the machine to get a new IP.

Hmmm ... They are using DHCP, but I am fairly certain they are still using their originally allocated IP's.

But thanks, that is certainly something to check next time it happens.

---

Flying high with Team Sicituradastra.

It seems they change ID intermittently during a shutdown/reboot. Not every time though (~10-20%)

My observation is that ID only changes when client and server disagree about number of connections made.

On the client side that number is in client_state.xml in line

<rpc_seqno>xxx</rpc_seqno>

and on server side it's in line

Number of times BOINC has contacted server: xxx

Note that client_state.xml bears information about all projects that host participates in so you need to find project section for correct project (if there are multiple).
Client ID only gets changed when client thinks it contacted server fewer times than server thinks it did. It's fine if client thinks it contacted server more times than server does.

If there are no problems with connection from client to server, then these two numbers won't differ. However, they could if BOINC client crashes or is forcibly stopped and doesn't refresh information in client_state.xml. I guess it could happen if shutdown procedure doesn't give enough time for BOINC to stop its clients and then refresh the state file.
State file only gets written now and then and is not in sync with client's internal state all the time. It could also happen that status of a task (or upload or report status) gets out of sync, but I guess that would be handled a bit more gracefully by upload and/or scheduling server.

All other information (OS type, IP address, BOINC version, coprocessor/GPU type, ...) is irrelevant in this scope.

---

Metod ...

It seems they change ID intermittently during a shutdown/reboot. Not every time though (~10-20%)

My observation is that ID only changes when client and server disagree about number of connections made.

On the client side that number is in client_state.xml in line

<rpc_seqno>xxx</rpc_seqno>

and on server side it's in line

Number of times BOINC has contacted server: xxx

Note that client_state.xml bears information about all projects that host participates in so you need to find project section for correct project (if there are multiple).
Client ID only gets changed when client thinks it contacted server fewer times than server thinks it did. It's fine if client thinks it contacted server more times than server does.

If there are no problems with connection from client to server, then these two numbers won't differ. However, they could if BOINC client crashes or is forcibly stopped and doesn't refresh information in client_state.xml. I guess it could happen if shutdown procedure doesn't give enough time for BOINC to stop its clients and then refresh the state file.
State file only gets written now and then and is not in sync with client's internal state all the time. It could also happen that status of a task (or upload or report status) gets out of sync, but I guess that would be handled a bit more gracefully by upload and/or scheduling server.

All other information (OS type, IP address, BOINC version, coprocessor/GPU type, ...) is irrelevant in this scope.

Interesting ... but wouldn't that apply to all boinc versions?
I have only had the issue with 6.10.58, and never with any of the other versions I am running.

---

Flying high with Team Sicituradastra.

...All other information (OS type, IP address, BOINC version, coprocessor/GPU type, ...) is irrelevant in this scope.

Interesting ... but wouldn't that apply to all boinc versions?
I have only had the issue with 6.10.58, and never with any of the other versions I am running.

Are you speaking about the hostID (as Metod, S56RKO does) or about the host CPID? The latter indeed seems to be changed by 6.10.58 on every IP address change, but that only affect statistics history and doesn't produce double host entries in the project database.

Gruß,
Gundolf
[edit]CPID = Cross Project ID
There are account CPIDs and host CPIDs[/edit]

You mean your machine has the same problem with CPID like my laptop since update to 6.10.58 (or actually in my case first to 6.10.56)?

---

Are you speaking about the hostID (as Metod, S56RKO does) or about the host CPID? The latter indeed seems to be changed by 6.10.58 on every IP address change, but that only affect statistics history and doesn't produce double host entries in the project database.

Gruß,
Gundolf
[edit]CPID = Cross Project ID
There are account CPIDs and host CPIDs[/edit]

AHAA ... must be the host CPID, I think. (Confusing isn't it)

I am fairly sure the ID shown on the project page doesn't change.

The ID shown on stats sites certainly does, and as the comp reports in to each project, the stats site transfers existing credit tallys over to the new ID until the old ID disappears (when credit reaches zero?) (When this happens it seems variable amounts of credit just dissappear into a black hole).

6.10.58 has been around for quite awhile, and this seems to be only affecting that version and hasn't been fixed. (Oh, 6.10.56 as well)

I think I will just roll-back to an earlier version than 6.10.56, as it is driving me crazy when I go to a stats site and see that my computer only "appeared" a couple of days before, and the total BOINC credit shown is considerably less than the the sum of the totals for each project.

Thanks to all for your input.

@Link - Yep, same problem on 3 of my machines. 2x 6.10.58, 1x 6.10.56 Interesting that one of my 6.10.56 hosts is changing ID's and the other hasn't (yet).

---

Flying high with Team Sicituradastra.

Are you speaking about the hostID (as Metod, S56RKO does) or about the host CPID? The latter indeed seems to be changed by 6.10.58 on every IP address change, but that only affect statistics history and doesn't produce double host entries in the project database.

Let's hope it will be fixed with the next release, it's kind of annoying...

---