Hi,

i registered in the last days, and got the "Rosetta@home account confirmation" Email.
But for running the client i need the account key, which i didn't get with this email. Could not find the Account key in my Account Page or anywhere else.
Where can i find it?


Or is the only chance for me to get this account to install boinc to a Desktop System? That would not be good.

Regards

Hspille

When you attach to the project, select the radio button for "existing account", enter your EMail address and password, and BOINC will connect to the project and begin downloading the files needed to run. ...no account keys anymore.

---

Rosetta Moderator: Mod.Sense

well, but i have a "console only" system.... There is no radio button.

boinccmd --help will give you the options.

Specifically you are looking for:

boinccmd --lookup_account https://boinc.bakerlab.org/ [email protected] password

replace your email and password accordingly.

---

It should then be upgraded to project Password instead of Account Key then, otherwise people will get confused

i tried this command and saw this message: can't connect to local host.

------
pcname:~/BOINC # ./boinccmd --lookup_account https://boinc.bakerlab.org/ [email protected] password
can't connect to local host
------

linux: SLES 10 SP 2 x86_64
boinc version 6.10.58


help, please

The project domain should be:
https://boinc.bakerlab.org/rosetta

Looks like you forgot the /rosetta part, at least on what you've posted here.

---

Rosetta Moderator: Mod.Sense

The project domain should be:
https://boinc.bakerlab.org/rosetta

Looks like you forgot the /rosetta part, at least on what you've posted here.

------
pcname:~/BOINC # ./boinccmd --lookup_account https://boinc.bakerlab.org/rosetta/ [email protected] password
can't connect to local host
------
the same result (

Is the user you are signed on with allowed to use sockets? Are you running under the same user that started the BOINC core client? "local host" refers to sockets connection between boinccmd and the BOINC core client that should be out there running, listening on port 31416 (check netstat).

---

Rosetta Moderator: Mod.Sense

Is the user you are signed on with allowed to use sockets? Are you running under the same user that started the BOINC core client? "local host" refers to sockets connection between boinccmd and the BOINC core client that should be out there running, listening on port 31416 (check netstat).

Thank you for your help. The problem was in my wrong-doing (the error was discovered when using the command netstat-l), after installation it was necessary to run the ./boinc and then try to get account key.

Yes, the BOINC "core client" has to be running to service requests produced by the issuance of boinccmd. boinccmd actually just sends a sockets message to the core client requesting that it perform the desired operation. So it has to already be fired up and listening on that socket. Since these sockets are internal within your system, boinccmd is trying to connect to "localhost" to communicate the request you've made.

---

Rosetta Moderator: Mod.Sense

Hi all, I hope I'am in the good topic.
I ask myself if it's possible to get an weak account key for Rosetta@Home, I know that lot of projects proposed this, maybe Rosetta@Home could have this too if it's possible (the server have to be update if it isn't I imagine).
If it's too hard to do this don't care, I'm not expected to have one, however it would be practice.

Thank you very much for all the project,
e.clement

PS : I hope you can understand my post because I'm not sure of my English (I prefer to write french).

---

Join Charity Race, the Benefit-Crunching-Action !

Right, I am pretty certain that support for weak account keys was incorporated in to BOINC after the last R@h server upgrade. But the next time the server code is updated, it should pick up that feature.

---

Rosetta Moderator: Mod.Sense

@Mod.Sense : thank you very much for your answer, I will be patient to have a WAK.

---

Join Charity Race, the Benefit-Crunching-Action !

Right, I am pretty certain that support for weak account keys was incorporated in to BOINC after the last R@h server upgrade. But the next time the server code is updated, it should pick up that feature.

Any news for this? I want to create a common team account, where everyone can crunch on without any further registration. Obviously I can't publish the password for it.

---

LUE