BOINC Command on Raspberry Pi Gives Authorization Failure
10 Nov 2015 18:01:53 UTC
Topic 198302
(moderation:
I'm running Einstein@Home on a Raspberry Pi 2B. When I attempt to use ssh in Terminal with BOINC commands (for example, "boinccmnd --get_tasks"), I get the following message: "Authorization failure: -155."
This started after I mistakenly entered only "boinc" at the prompt.
How do I fix this so I can once again use the Terminal and commands to manage my Einstein@Home projects? I've reinstalled BOINC and rebooted and the problem persists.
Thanks in advance for any help.
BOINC Command on Raspberry Pi Gives Authorization Failure
)
You need to supply the gui_rpc_auth password, or navigate to the directory boinc is installed in:
http://boinc.berkeley.edu/wiki/Controlling_BOINC_remotely
http://boinc.berkeley.edu/wiki/Boinccmd_tool
and maybe allow access in the remote_hosts.cfg
Claggy
Thank you for your reply.
)
Thank you for your reply. I've entered a password in the gui_rpc_auth.cfg file, but am still getting the authorization failure message. I am in no way a knowledgeable and experienced linux person, so I'm probably way over my head here. I don't know what to enter when prompted for "host name." I've tried the IP address with no success. Also, what password is to be entered to accompany the host name: the one I added to the gui_rpc_auth file, einstein@home account or what?
Would resetting the project be the way to start afresh or would the messed up files still be present?
What have you tried so
)
What have you tried so far?
Try boinccmd --passwd gui_rpc_auth_password --get_cc_status
Claggy
So far, I've removed and
)
So far, I've removed and reinstalled boinc-manager and boinc-client but can't use the BOINC Manager in a GUI because I can't connect the host computer with BOINC. I've tried entering a password in the gui_rpc_auth.cfg file, but still get the Authorization failure: -155 message.
I just tried the command you suggested and it too returns the "Authorization failure: -155." I think that will be the result for any command that begins with boinccmd.
RE: I've tried entering a
)
Did you restart Boinc or the Pi 2?
Claggy
RE: ... can't use the BOINC
)
Does this mean, "... can't use BOINC Manager on a remote machine to connect to the BOINC client on the pi because the connection is refused."? If so, all you need to do is create a file 'remote_hosts.cfg' in the BOINC data directory on the pi, containing the IP addresses of any other host you wish to use BOINC Manager on, in order to control the BOINC client on the pi. The file will be used if you have the BOINC client 'read config files' through BOINC Manager. Restarting BOINC will be needed if you can't connect to BOINC through the manager.
Does "... tried entering a password in the gui_rpc_auth.cfg file" mean that you changed the 32 character 'default' value that this file contains? If so, you have a problem because, unless you stop and restart BOINC, the old 32 character string is still the expected password, no matter what the file currently contains. How do you start and stop BOINC on the pi? Did you happen to save a copy of the default gui_rpc_auth.cfg before you changed the password? Can you stop and restart BOINC? If you can, the new password should be picked up on the restart and so be accepted.
Cheers,
Gary.
First, my sincere thanks to
)
First, my sincere thanks to Gary and Claggy for your assistance; I really appreciate the time you took to troubleshoot this for me.
In the course of trying to modify files, the Pi crashed and, in frustration, I simply reinstalled the operating system. I've now got Einstein@Home up and running again and all seems fine: I can ssh from another machine and Boinc Manager works on the Pi's desktop. The only downside is the Einstein@Home projects that had started on the previous OS installation won't be completed--unless there is a way to copy those projects from my account as new downloads.
Thank you again for your time and effort in responding to my request for help.
I run BOINCtasks on another
)
I run BOINCtasks on another (Windows) machine and use it control the Pi's. That way you don't have to worry about using BOINCCMD and you still have a graphical view of what the Pi is doing. It also lets you edit the config files remotely. The only time you'd need to ssh into the Pi would be to do OS updates or some other maintenance.
BOINC blog