Cloned Clients

[dkelly84]

Hi,

I have around 150 clients folding, using Win 10 with version 7.6.8

However the stats show work coming from just 3 clients. I'm assuming I've managed to accidentally clone a unique ID in the deployment of the software - does anyone know what I need to delete to get it to reset?

Thanks

[parkut]

assuming they are all folding under the same user name, for more than a few days?
what to you see here: https://apps.foldingathome.org/cpu

[Joe_H]

The client downloads an unique Assignment ID the first time it connects to a server after installation. So you should not clone the client after installation except if you installed on a system not connected to the internet.

As for what exactly to delete, I am not certain where the ID number is stored. You could set the client to Finish any current work, and see if deleting the AppData directory completely and restarting up gets you back to a "new" install status.

Not having unique ID numbers under normal circumstances can lead to occasionally having the same WU downloaded to different machines. Depends on when the requests come in.

[dkelly84]

assuming they are all folding under the same user name, for more than a few days?
what to you see here: https://apps.foldingathome.org/cpu

Hi,

That's correct, same username, for a week or so.

https://i.imgur.com/LuM8bcF.png

[Joe_H]

So each machine with a CPU slot and 2 GPUs? Yeah, looks like the ID was cloned across all.

[dkelly84]

OK, thanks all for confirming. I have an idea to sort it - I'll try it and let it run for a bit to confirm, and let you know if it worked.

[bruce]

It's a well known fact: You cannot clone the client. You can clone the installation, but each client must make its own first connection to the server and obtain it's own unique UserID. You can install the client, including config.xml PROVIDED you don't let the client connect to the servers.

[dkelly84]

It's a well known fact: You cannot clone the client. You can clone the installation, but each client must make its own first connection to the server and obtain it's own unique UserID. You can install the client, including config.xml PROVIDED you don't let the client connect to the servers.

Oh, it's a much more ugly solution than that I'm afraid haha.

As i'm only running it from the command line and didn't want to push out a full client install each time, I deployed the portableapps version - robocopy'd the folder to a temporary directory on the machine and triggered the process from there. I must have accidentally cloned the working copy from my test client rather than a "fresh" copy.

Anyway, all's well that end's well - I just deleted the whole data folder and let it recreate it, and surprise surprise, it's all working now. Thanks everyone.

[Joe_H]

Looking a lot different now, but it looks like a few did not get the team number updated.