Authorization failure: -155 on Ubuntu 16.04 [SOLVED]

User avatar
Hal Bregg
Boinc Sergeant
Boinc Sergeant
Posts: 175
Joined: Thu Nov 08, 2018 1:22 pm
Location: Cumbria

#1 Authorization failure: -155 on Ubuntu 16.04 [SOLVED]

Post by Hal Bregg »

Hi all,

I stopped some projects from receiving more work on one of my host through boinstats and now when I try to check status on of onging tasks with

Code: Select all

boinccmd --get_state
all I get is Authorization failure: -155

No matter if I run this command as root or sudoer, results are the same.
I checked BOINC status with

Code: Select all

/etc/init.d/boinc-client status

● boinc-client.service - Berkeley Open Infrastructure Network Computing Client
   Loaded: loaded (/lib/systemd/system/boinc-client.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-01-27 20:18:35 CET; 1 day 2h ago
  Process: 1398 ExecStartPre=/bin/chown boinc:boinc /var/log/boinc.log /var/log/boincerr.log (code=exited, status=0/SUCCESS)
  Process: 1367 ExecStartPre=/usr/bin/touch /var/log/boinc.log /var/log/boincerr.log (code=exited, status=0/SUCCESS)
 Main PID: 1405 (sh)
    Tasks: 9
   Memory: 212.8M
      CPU: 1d 1h 57min 27.398s
   CGroup: /system.slice/boinc-client.service
           ├─1405 /bin/sh -c /usr/bin/boinc --dir /var/lib/boinc-client >/var...
           ├─1407 /usr/bin/boinc --dir /var/lib/boinc-client
           ├─7228 ../../projects/setiathome.berkeley.edu/setiathome_8.00_x86_...
           ├─7551 ../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_1.46_x...
           └─7776 ../../projects/wuprop.boinc-af.org/data_collect_v4_425_x86_...
Image
davidbam
General Bitchin'
General Bitchin'
Posts: 6371
Joined: Wed Aug 15, 2018 1:15 pm
Location: Huntly, Scotland
Contact:

#2 Re: Authorization failure: -155 on Ubuntu 16.04

Post by davidbam »

Maybe something like ...

Code: Select all

boinccmd --host IP_ADDR --passwd xxx --get_state
I think this is fool-proof but could you just try it for me please? • There are 10 types of people in the world; those who understand binary, and those who don’t
Image
User avatar
Hal Bregg
Boinc Sergeant
Boinc Sergeant
Posts: 175
Joined: Thu Nov 08, 2018 1:22 pm
Location: Cumbria

#3 Re: Authorization failure: -155 on Ubuntu 16.04

Post by Hal Bregg »

davidBAM wrote: Mon Jan 28, 2019 10:45 pm Maybe something like ...

Code: Select all

boinccmd --host IP_ADDR --passwd xxx --get_state
I need some clarification with the syntax of the command, david.
The host is VPS and I assume I must put its IP address, right? If so, terminal throws same error as in the subject but with number 102 instead.
Image
davidbam
General Bitchin'
General Bitchin'
Posts: 6371
Joined: Wed Aug 15, 2018 1:15 pm
Location: Huntly, Scotland
Contact:

#4 Re: Authorization failure: -155 on Ubuntu 16.04

Post by davidbam »

Then you should await arrival of a real expert :P

I use this for all my Linux machines but, thinking of it, I have already given them all a password for remote access (I'd replace passwd with that password). On Linux, I give a password by

Code: Select all

sudo echo -n myPassword >/usr/lib/boinc/gui_rpc_auth.cfg
sudo service boinc-client restart
I think this is fool-proof but could you just try it for me please? • There are 10 types of people in the world; those who understand binary, and those who don’t
Image
User avatar
scole of TSBT
Boinc Major General
Boinc Major General
Posts: 5980
Joined: Mon Feb 03, 2014 2:38 pm
Location: Goldsboro, (Eastern) North Carolina, USA

#5 Re: Authorization failure: -155 on Ubuntu 16.04

Post by scole of TSBT »

Is the boinc client on that system configured to allow remote connections? Can you connect to it using the boinc manager on another system or using boinctasks?
Image
User avatar
Hal Bregg
Boinc Sergeant
Boinc Sergeant
Posts: 175
Joined: Thu Nov 08, 2018 1:22 pm
Location: Cumbria

#6 Re: Authorization failure: -155 on Ubuntu 16.04

Post by Hal Bregg »

davidBAM wrote: Wed Jan 30, 2019 7:51 pm Then you should await arrival of a real expert :P

I use this for all my Linux machines but, thinking of it, I have already given them all a password for remote access (I'd replace passwd with that password). On Linux, I give a password by

Code: Select all

sudo echo -n myPassword >/usr/lib/boinc/gui_rpc_auth.cfg
sudo service boinc-client restart
None of this worked :(
scole of TSBT wrote: Wed Jan 30, 2019 8:56 pm Is the boinc client on that system configured to allow remote connections? Can you connect to it using the boinc manager on another system or using boinctasks?
I don't have it configured.
I searched a little bit but could not find anything useful. Or my searching skills are not up to scratch.
Image
User avatar
scole of TSBT
Boinc Major General
Boinc Major General
Posts: 5980
Joined: Mon Feb 03, 2014 2:38 pm
Location: Goldsboro, (Eastern) North Carolina, USA

#7 Re: Authorization failure: -155 on Ubuntu 16.04

Post by scole of TSBT »

if addition to change the password in the file /usr/lib/boinc/gui_rpc_auth.cfg, you must also....

If it's running boinc version 7.4.25 or higher, you need this line in the cc_config.xml
<allow_remote_gui_rpc>1</allow_remote_gui_rpc>
after you add it you must restart the boinc client

If it's running boinc version earlier than 7.4.25, you'll need to add the ip addresses of the remote systems you want to give permission to access that boinc client in file /usr/lib/boinc/remote_hosts.cfg. Then you must restart the boinc client

AND you must have access to that system on port 31416. If it's at a hosting site and you don't have direct access to that ip and port, won't work.
Image
User avatar
Hal Bregg
Boinc Sergeant
Boinc Sergeant
Posts: 175
Joined: Thu Nov 08, 2018 1:22 pm
Location: Cumbria

#8 Re: Authorization failure: -155 on Ubuntu 16.04

Post by Hal Bregg »

It's right time to close this thread.

It turned out that 'lockfile' was responsible for authorization failure. I deleted 'lockfile' from both home and from /var/lib/boinc-client directories and restarted boinc-client.

According to some various threads on different forums (I'd forgotten to take a note of which one), BOINC program was failing sometimes to delete mentioned file upon closure and causing authrisation failure.
Image
Post Reply Previous topicNext topic

Return to “Linux”