BOINC on ARM

[Christian Beer]

Am 10.01.2018 um 18:33 schrieb jarek:
> Hello,
> 
> 
> boinccmd --lookup_account https://lhcathome.cern.ch/lhcathome/ `mail` `password`
> 
> but next commands ended again with the same error:
> 
> boinccmd --project_attach https://lhcathome.cern.ch/lhcathome/ `account`
> Authorization failure: -155
> boinccmd --get_state
> Authorization failure: -155

Hi this sounds very familiar from previous issues. The problem with
boinccmd is that it needs to read the password in
/var/lib/boinc-client/gui_rpc_auth.cfg Normally on Ubuntu this is empty.
You should first check that it is. Next thing to check is if the user
you use to run the boinccmd command has read access to this file. The
whole directory is usually owned by the user boinc and group boinc. So
you first need to add your normal user to the group in order to access
the directory.

The authorization failure means that the boinc daemon expected a
password from boinccmd and it didn't provide one. Or the daemon expected
a password but got one.

I don't have a password set and my user is in the boinc group and the
--get_state RPC is working for me. As soon as I specify a password via
commandline I get an authorization failure.


> 
> Moreover, in /var/log/boincerr.log there are, after 1st line:
> 
> dir_open: Could not open directory ‘slots’ from ‘/var/lib/boinc-client’.

This indicates there is a permission problem for the boinc daemon. Could
you post the result of "ls -l /var/lib/boinc-client"?

> 
> repeated (ad libitum) following lines:
> 
> dir_open: Could not open directory ‘/dev/input’ from ‘/var/lib/boinc-client’.
> dir_open: Could not open directory ‘/dev/input/mice’ from
> ‘/var/lib/boinc-client’.

This is normal as the BOINC idle detection tries to check for user
activity via timestamps of those files. This is nowadays not permitted.


Regards
Christian