>
> I think you will find that email addresses ONLY are checked on creation
> (though I am not even 100% sure of that). Name is certainly NOT UNIQUE with
> MANY multiple named people in the SETI Database... especially of names like
> "Dave" etc.
>
> Personally I dont think Name SHOULD be unique... but that I can leave up to
> the BOINC developers to argue about *evil grin*... of course when the email
> comes up on the developers list I will have my say *cackle*
>
Yes, you are right.
To go back to the original problem, now it's clear there is something "wrong" when joining Einstein project. I started with CPDN, it assigned me a CPID. Then I joined SETI and Predictor project, assigning me the SAME CPID. Which was consistent with my expectations. Now (despite the fact I requested two account with 2 differents email address) when joining Einstein, it assigned me an other CPID........ using the right email account
So why?
I did look at client_state.xml, looked at email hash values and they are the same on a PC with CPDN & Einstein compared to one who has only Einstein.
Ideas?
Now I tested something different and I am able to change the CPID:
environement 2 PCs.
One is running only Einstein
The other is running Einstein & Climate.
If I update the project (via the GUI interface) from the PC running ONLY Einstein the CPID is "new".
If I update the project on the other PC (running Einstein & Climate) the cPID goes back to the "unique" one for multiple projects.
(I am refreshing simply the homepage of eintein and read the CPID (the one used in exported data).
I haven't looked into that code yet, but there should be some flag on the client side that tells the server either "take this CPID for my account" or "I don't have a CPID yet - give me one". Apparently this flag somehow is broken on the Einstein-only machine, so every contact of each of the clients tells the server to take the CPID of the client. Maybe that's because the Einstein-only client was using the "wrong" account before and got a CPID for the wrong email address?
Try to stop the client on the Einstein-only PC, delete the line of the client_state.xml file (and maybe also from the sched_reply.xml, too), start the client again and see if the problem persists.
>
> Try to stop the client on the Einstein-only PC, delet the line of the
> client_state.xml file (and maybe also from the sched_reply.xml, too), start
> the client again and see if the problem persists.
>
> BM
>
>
What line? email hash? cpid?
On some PCs, I had to copy/paste the CPID from other xml files because it was creating again the wrong CPID.
Is it something which will be fixed by you in a future release?
> > Just edited the posting - the brackets were lost...
> >
> > BM
> >
>
> It seems to be working correctly. I will do the same on other PC with the
> problem. For info, I deleted lines of both xml files.
>
>
This is a problem of BOINC, either the Core Client or the Client/Server communication. The Einstein@Home developers try to help the BOINC team if possible, but we curretly have our hands full with E@H specific stuff. I don't know enough of the BOINC code involved there myself, so if this will be fixed, then probably not by me. Also I think this would be hard to track down and doesn't affect many users anyway, so I doubt that has a high priority on the BOINC todo list.
> On some PCs, I had to copy/paste the CPID from other xml files because it was
> creating again the wrong CPID.
>
> Is it something which will be fixed by you in a future release?
>
The only time I had this problem, the email addresses were different. At that time, the client did not make the CPIDs match.
> The only time I had this problem, the email addresses were different. At that
> time, the client did not make the CPIDs match.
>
Sure. I was mixing 2 problems. One coming from the fact I installed PC with wrong account key (on an other email address), the other coming from the fact that after reinstalling with the right account key the generared CPID (on some PC only) was not the correct one. Where should I report this issue?
I know at least one other person with the same issue as me. (And he is running only CPDN and Eintein, again on several PC).
>
> > The only time I had this problem, the email addresses were different. At
> that
> > time, the client did not make the CPIDs match.
> >
> Sure. I was mixing 2 problems. One coming from the fact I installed PC with
> wrong account key (on an other email address), the other coming from the fact
> that after reinstalling with the right account key the generared CPID (on some
> PC only) was not the correct one. Where should I report this issue?
>
> I know at least one other person with the same issue as me. (And he is running
> only CPDN and Eintein, again on several PC).
>
Bugs can be reported at bbugs.axpr.net. Make certain that you read the bugs already there to avoid creating a duplicate.
> > I think you will find
)
>
> I think you will find that email addresses ONLY are checked on creation
> (though I am not even 100% sure of that). Name is certainly NOT UNIQUE with
> MANY multiple named people in the SETI Database... especially of names like
> "Dave" etc.
>
> Personally I dont think Name SHOULD be unique... but that I can leave up to
> the BOINC developers to argue about *evil grin*... of course when the email
> comes up on the developers list I will have my say *cackle*
>
Yes, you are right.
To go back to the original problem, now it's clear there is something "wrong" when joining Einstein project. I started with CPDN, it assigned me a CPID. Then I joined SETI and Predictor project, assigning me the SAME CPID. Which was consistent with my expectations. Now (despite the fact I requested two account with 2 differents email address) when joining Einstein, it assigned me an other CPID........ using the right email account
So why?
I did look at client_state.xml, looked at email hash values and they are the same on a PC with CPDN & Einstein compared to one who has only Einstein.
Ideas?
Now I tested something different and I am able to change the CPID:
environement 2 PCs.
One is running only Einstein
The other is running Einstein & Climate.
If I update the project (via the GUI interface) from the PC running ONLY Einstein the CPID is "new".
If I update the project on the other PC (running Einstein & Climate) the cPID goes back to the "unique" one for multiple projects.
(I am refreshing simply the homepage of eintein and read the CPID (the one used in exported data).
Someone can explain?
> Someone can explain? I
)
> Someone can explain?
I haven't looked into that code yet, but there should be some flag on the client side that tells the server either "take this CPID for my account" or "I don't have a CPID yet - give me one". Apparently this flag somehow is broken on the Einstein-only machine, so every contact of each of the clients tells the server to take the CPID of the client. Maybe that's because the Einstein-only client was using the "wrong" account before and got a CPID for the wrong email address?
Try to stop the client on the Einstein-only PC, delete the line of the client_state.xml file (and maybe also from the sched_reply.xml, too), start the client again and see if the problem persists.
BM
BM
> > Try to stop the client
)
>
> Try to stop the client on the Einstein-only PC, delet the line of the
> client_state.xml file (and maybe also from the sched_reply.xml, too), start
> the client again and see if the problem persists.
>
> BM
>
>
What line? email hash? cpid?
Just edited the posting - the
)
Just edited the posting - the brackets were lost...
BM
BM
> Just edited the posting -
)
> Just edited the posting - the brackets were lost...
>
> BM
>
It seems to be working correctly. I will do the same on other PC with the problem. For info, I deleted lines of both xml files.
On some PCs, I had to
)
On some PCs, I had to copy/paste the CPID from other xml files because it was creating again the wrong CPID.
Is it something which will be fixed by you in a future release?
> > Just edited the posting - the brackets were lost...
> >
> > BM
> >
>
> It seems to be working correctly. I will do the same on other PC with the
> problem. For info, I deleted lines of both xml files.
>
>
This is a problem of BOINC,
)
This is a problem of BOINC, either the Core Client or the Client/Server communication. The Einstein@Home developers try to help the BOINC team if possible, but we curretly have our hands full with E@H specific stuff. I don't know enough of the BOINC code involved there myself, so if this will be fixed, then probably not by me. Also I think this would be hard to track down and doesn't affect many users anyway, so I doubt that has a high priority on the BOINC todo list.
BM
BM
> On some PCs, I had to
)
> On some PCs, I had to copy/paste the CPID from other xml files because it was
> creating again the wrong CPID.
>
> Is it something which will be fixed by you in a future release?
>
The only time I had this problem, the email addresses were different. At that time, the client did not make the CPIDs match.
BOINC WIKI
> The only time I had this
)
> The only time I had this problem, the email addresses were different. At that
> time, the client did not make the CPIDs match.
>
Sure. I was mixing 2 problems. One coming from the fact I installed PC with wrong account key (on an other email address), the other coming from the fact that after reinstalling with the right account key the generared CPID (on some PC only) was not the correct one. Where should I report this issue?
I know at least one other person with the same issue as me. (And he is running only CPDN and Eintein, again on several PC).
> > > The only time I had
)
>
> > The only time I had this problem, the email addresses were different. At
> that
> > time, the client did not make the CPIDs match.
> >
> Sure. I was mixing 2 problems. One coming from the fact I installed PC with
> wrong account key (on an other email address), the other coming from the fact
> that after reinstalling with the right account key the generared CPID (on some
> PC only) was not the correct one. Where should I report this issue?
>
> I know at least one other person with the same issue as me. (And he is running
> only CPDN and Eintein, again on several PC).
>
Bugs can be reported at bbugs.axpr.net. Make certain that you read the bugs already there to avoid creating a duplicate.
BOINC WIKI