| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
Fab!en
Cruncher Joined: Aug 2, 2022 Post Count: 1 Status: Offline Project Badges:
|
Hello :)
I've just created an account on WCG, but i'm on BOINC since years. It seems my BOINC Cross Project IDentifier is not updated correctly on WGC. I've added my WCG account on two clients that already have others projects configured, all my boinc accounts have the same email address, but WCG keep a freshly generated rather than the good one. https://boinc.berkeley.edu/wiki/Cross-project_identification Any idea ? Thanks in advance. |
||
|
|
Unixchick
Veteran Cruncher Joined: Apr 16, 2020 Post Count: 1298 Status: Offline Project Badges:
|
It is important to know that WCG isn't fully operational at this time. It is in a testing phase. I think it is good that you reported the issue, but just be aware that the solution may be on the project side and not your side.
|
||
|
|
LumenDan
Cruncher Joined: Jun 22, 2022 Post Count: 8 Status: Offline Project Badges:
|
Issues with CPID synchronisation can affect any BOINC project as the BOINC manager doesn't synchronise CPIDs between projects immediately.
When you join any new BOINC project a CPID will be created that is unique to that project. As you receive work units for the new project your BOINC Manager will detect that the project CPIDs aren't synchronised between projects and negotiate an update with the newer project. If you are only running one or two projects concurrently on your PCs the BOINC Manager may not be able to decide which project has the definitive CPID. If the CPID doesn't automatically correct itself after you have returned work units for the WCG project then you could search for "CPID fragmentation" to find some other useful forum discussions that address the causes and remedies for the issue. |
||
|
|
|