boinccmd --join_acct_mgr [anything] *** ***

will print "Operation failed: Error -1"

Nothing in logs, no chance to figure out what's wrong.

boinccmd --join_acct_mgr [anything] *** ***

a) is the BOINC binary running when you use boinccmd?
b) which account manager are you trying to add?
c) do you have an account already at that account manager?

---

a) Sure (if it not running boinccmd will write "can't connect to host" - ok this part works ;)
b) bam.boincstats.com But actual value does not affect behaviour. When it write boinccmd --join_acct_mgr asdfsadf asfasdf asdfasdf the result excatly same.
c) Yes I have. Actually I have boinc client on windows machine connected to this manager, but I used GUI there. My Centos have no GUI installed, so boinccmd is essential.

bam.boincstats.com

I'm pretty sure that the URL needs http:// or https:// in front of it. Have you tried that?

boinccmd --join_acct_mgr https://bam.boincstats.com your account name your account password

BAM is HTTPS these days as well.

---

Yes, of course. As I wrote, url format does not affect behaviour at all. I've tried http:// https://, I've tried it with and without trailing slash finally I've tried "asdfasdf".

The error you get is one you get when the permissions on the BOINC directory aren't correct. Can you do any other commands with boinccmd?

Commands:
 --client_version                   show client version
 --create_account URL email passwd name
 --file_transfer URL filename op    file transfer operation
   op = retry | abort
 --get_cc_status
 --get_daily_xfer_history           show network traffic history
 --get_disk_usage                   show disk usage
 --get_file_transfers               show file transfers
 --get_host_info
 --get_message_count                show largest message seqno
 --get_messages [ seqno ]           show messages > seqno
 --get_notices [ seqno ]            show notices > seqno
 --get_project_config URL
 --get_project_status               show status of all attached projects
 --get_proxy_settings
 --get_simple_gui_info              show status of projects and active tasks
 --get_state                        show entire state
 --get_tasks                        show tasks
 --get_old_tasks                    show reported tasks from last 24 hours
 --join_acct_mgr URL name passwd    attach account manager
 --lookup_account URL email passwd
 --network_available                retry deferred network communication
 --project URL op                   project operation
   op = reset | detach | update | suspend | resume | nomorework | allowmorework
| detach_when_done | dont_detach_when_done
 --project_attach URL auth          attach to project
 --quit                             tell client to exit
 --quit_acct_mgr                    quit current account manager
 --read_cc_config
 --read_global_prefs_override
 --run_benchmarks
 --set_gpu_mode mode duration       set GPU run mode for given duration
   mode = always | auto | never
 --set_host_info product_name
 --set_network_mode mode duration   set network mode for given duration
   mode = always | auto | never
 --set_proxy_settings
 --set_run_mode mode duration       set run mode for given duration
   mode = always | auto | never
 --task url task_name op            task operation
   op = suspend | resume | abort

What if you do?
boinccmd --get_state
Or?
boinccmd --run_benchmarks

---

Probably missing password. On Redhat family distros BOINC client is usually set up to require a password when connecting to it. boinccmd tries to read the password from gui_rpc_auth.cfg file in current directory and if the file doesn't exist or can't be read boinccmd tries to connect without password.

gui_rpc_auth.cfg file is located in BOINC's data directory which is usually at /var/lib/boinc-client on Linux distros. If the file is empty then the client does not require password (which means anyone can then e.g. add some rogue project).

You have a few options available.
- add the password on boinccmd command line: boinccmd --passwd abcd
- add your account to boinc group and run boinccmd from /var/lib/boinc-client
- replace gui_rpc_auth.cfg with empty file, restart the client and then run boinccmd from any directory without password

>- add your account to boinc group and run boinccmd from /var/lib/boinc-client

Thanks that helped. But that was shame. I think if boinccmd can't access file or pass authorization it should clearly state this.

Later versions are a bit more clear:

Operation failed: authentication error