Hi there!
I'm trying to run Rosetta@home on my home server (Debian GNU/Linux, without X-server and GUI), on which I already have other Boinc projects running successfully. When I'm trying to get account key by running command
boinccmd --lookup_account https://boinc.bakerlab.org/rosetta/ email@domain.com passwd
but I get Authorization failure: -155.

My first thoughts were: it seems to be network problem, maybe firewall blocks some ports. But 80 and 443 ports are open, and afaik boinc does not use any other ports.
then I tried different passwords, rechecked URL and login/password, and so on. None helped.

What can you say?

What can you say?

You could say "misleading message" - it all boils down to what directory you are in when you try to execute the command - for some reason boinccmd ALWAYS assumes that is your current working directory s the BOINC directory and he expects certain files to be in that directory.

I ran into the same problem when I was automating some "tuning" for BOINC using cron to kick off some commands. What I ended up doing was to create a basic little script like:

cd /home/chris/Desktop/BOINC
boinccmd --what ever you want

Works fine, lasts a long time. Close enough for government work and all that stuff.

CH

What can you say?

You could say "misleading message" - it all boils down to what directory you are in when you try to execute the command - for some reason boinccmd ALWAYS assumes that is your current working directory s the BOINC directory and he expects certain files to be in that directory.

I ran into the same problem when I was automating some "tuning" for BOINC using cron to kick off some commands. What I ended up doing was to create a basic little script like:

cd /home/chris/Desktop/BOINC
boinccmd --what ever you want

Works fine, lasts a long time. Close enough for government work and all that stuff.

CH

Yep, you were right! Still, there is one bad thing - if I run boinc from my regular user (not boinc), boinc will not use /var/lib/boinc-client/ as work dir because of permissions. But that's not serious, and, after all, quite logical, so that's OK. Thanks for advice, Chris Holvenstot!

Or you can set a password in the gui_rpc_auth.cfg and call boinccmd (from anywhere) like this:
boinccmd --host localhost --passwd yourpass --your_command