Hi,

Please help. I would like to continue contributing to the BOINC projects but its not working anymore:

I've been using boinc together wit SETI and Einstein for ages (Windows and Linux).
Now I installed the 5.2.14 BOINC client on my new gentoo linux system.

I ran the command as per the instructions at the end of the compilation:

* You need to attach to a project to do anything useful with boinc.
* You can do this by running /etc/init.d/boinc attach
* BOINC The howto for configuration is located at:
* http://boinc.berkeley.edu/anonymous_platform.php

Following the prompts, I entered the Project URL and the Account key.
Result:

* Attaching to project ... [ !! ]
2006-03-14 18:56:17 [---] 3) (Unix/Mac) Run this program with the -attach_project command-line option.
2006-03-14 18:56:17 [---] Visit http://boinc.berkeley.edu for more information
(--truncated some text--)

...
HERE'S THE PROBLEM:
Subsequently, whatever combination of commands I try with boinc_cmd, I get the following message:

RPC_CLIENT::init connect 2 on 3 returned -1
Authorization failure: -155

I changed the password in the /var/lib/boinc/gui_rpc_auth.cfg to something memorable, but I don't even get asked for it.

As soon as I load the boinc_gui, it starts up with this message:

The password you have provided is incorrect, please try again.

Point: I can't connect to a project. What should I do? If you've read this far, thank you! Any help would be much appreciated.

---

Same problem here. The password manager complains about a password and I finally figured out what it was by looking at your post then tried changing it and now it won't take anything.

I must say that I'm a bit disappointed in the whole BOINC application compared to the old SETI@HOME software. You would think that if someone wants you to donate cycle time they would make the setup a bit more straight forward.

Regards,

Mike

---

I had this problem with BOINC installed on 4 machines (running Ubuntu). On one of them, 'gort', I kept getting "Authorization failure: -155", but not the other 3. It occurred seemingly at random. It was driving me *nuts*. It particularly annoyed me that I could do a 'get_results' via ssh on all the machines except 'gort'

After hours of frustration, I noticed a few BOINC-related files in my home directory. They must've been there since I'd first tried to run BOINC on 'gort' a few hours earlier. I deleted these files, and the problem went away.

My best guess is that the CWD, or maybe $HOME, is on boinc_cmd's search path for configuration files before BOINC's working directory. It was picking up the old files and trying to talk to a non-existant BOINC client.

Moral: make sure there are no stale files in the CWD where you run boinc_cmd.

HTH & YMMV

Emmet.

---

You are a genius.

Thanks a lot.

---