How do I connect a boinccmd (a command-line tool) to my own computer (this same one, which crunches and the same at which I want to call the boinccmd command-line tool)?

- boincmgr graphical tool works fine (???) without anything right arter boot-up as I log-in.
- boinccmd says: Authorisation error: -155. Whatever command I put as a command.
- Ubuntu 12.04 with the latest update.
- boinccmd stoped working after I rebooted after the standard security-only update....

Any ideas?

I solved the problem surprisingly quickly in the so-called RTFM-way... Sorry for spamming - hopefully someone finds it useful.

1. I started pinning down the problem from the graph in page 4 (chapter 3: the boinc client, 3.1: applications) in http://www.worldcommunitygrid.org/bg/BOINCMassInstall.pdf. Notice, that in the description of the graph it says that "boinccmd uses TCP/IP to connect" and actually it is equivalent to boincmgr (so if one qorks ok, boinc-crunching actually works, just your monitoring tool sux).

2. I used a link from the above document to find a full text on boinccmd at
http://boinc.berkeley.edu/wiki/Boinccmd_tool where it says that:

3. ...you have to be in the "boinc" (computing core) directory in order to ommit "--host" param (which I always have, before now...). Otherwise you have to know host, and pass (see the above mentioned boinc website).

Final note: In my default Ubuntu 12.04 the boinc computing core's directory is:

/usr/lib/boinc-client

and if I run boinccmd while in this directory, all works fine, no "authentication error 155", e.g.:

boinccmd --get_state

# works as OK.

boinccmd must run in the same directory as the boinc-client binary.
boinccmd must run under the same account that the boinc-client runs under.

But if you can run BOINC Manager, then why the need for the boinccmd tool?

---

Thanks for your reply!

I use this computer to crunch 24/7 only, so I access it remotely over ssh. But while updates of this box, I prefer to do it locally, so I can see what is going on at the reboot before sshd strats. And due to this I knew now that the manager worked and boinccmd did not work. Thanks again!

boinccmd must run in the same directory as the boinc-client binary.
boinccmd must run under the same account that the boinc-client runs under.

But if you can run BOINC Manager, then why the need for the boinccmd tool?

Sorry to contradict, but if you have a dual program/data dir setup (like when you copy a working windows install to a new location and lose all registry entries) you have to run boinccmd out of the data dir or you'll end up with exactly that -155 authorisation error. Or rather more intriguingly with a -112 when you try to --quit. Not to mention that most boinccmd commands do just fine out of the program dir. You just get the odd one that needs to know where the data actually is. Took me a bit to figure out.

Linux of course is a different beast alltogether as it does not use a dual dir setup and data and program dir are the same.
Therefore your assumption of boinccmd having to be run from the directory of the binary is quite correct in that case.