Invalid client RPC Password

Message boards : Questions and problems : Invalid client RPC Password
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile StarzDust66

Send message
Joined: 9 Dec 20
Posts: 8
United States
Message 105870 - Posted: 27 Oct 2021, 21:35:55 UTC
Last modified: 27 Oct 2021, 21:46:42 UTC

Hi,

I am stumped. I have had success installing and running Boinc on several older computers. I've even had it installed on this one too in the recent past. Then, I upgraded this computer to Astronomy Linux running Ubuntu 21.10 OS. Now, no joy. I am cross posting this to both to Einsten@home and the Boinc websites.

This is an HP computer.

I have installed and re-installed Boinc and after apparently fixing one issue now I get the following error message:

Invalid client RPC password Try reinstalling Boinc.

HP Pavilion Notebook
5.9 GiB RAM
AMD A6-6310 APU
Radeon r4 graphics (AMD Kabini)
Ubuntu 21.10
64 bit
Wayland


So far I haven't located a resolution that works for this. Any pointers or help on how to resolve this issue will be most greatly appreciated.

Regards,

John
ID: 105870 · Report as offensive
Profile Dave
Help desk expert

Send message
Joined: 28 Jun 10
Posts: 1769
United Kingdom
Message 105874 - Posted: 28 Oct 2021, 5:04:53 UTC

Add yourself to the user group boinc and give yourself rw permissions to /var/lib/boinc-client.

I hope I have that right from memory. It has been discussed here in the past.
ID: 105874 · Report as offensive
Profile Joseph Stateson
Volunteer tester
Avatar

Send message
Joined: 27 Jun 08
Posts: 611
United States
Message 105876 - Posted: 28 Oct 2021, 13:55:03 UTC - in response to Message 105874.  
Last modified: 28 Oct 2021, 13:56:42 UTC

Add yourself to the user group boinc and give yourself rw permissions to /var/lib/boinc-client.

I hope I have that right from memory. It has been discussed here in the past.


I know enough about Linux to get into trouble but not always enough get out. Any system I put together 18.04 or 20.2, I always my account "jstateson" to get boinc and the GPU drivers.
When I edit cc_config or want to make changes to app_config I have to use sudo.

Looking at ownership and other properties I don't see any consistency and assume that is just the way Linux works. For the executable binary


jstateson@jysdualxeon1:/usr/bin$ ls -l boinc
-rwxr-xr-x 1 root root 20579552 Oct 22 20:43 boinc


but different here

jstateson@jysdualxeon1:/etc/boinc-client$ ls -l
total 24
-rw-rw-r-- 1 boinc boinc 2792 Oct 22 20:45 cc_config.xml
-rw-rw-r-- 1 boinc boinc  467 Apr 10  2020 cc_config.xml.bu
-rw-r--r-- 1 root  boinc   31 Jun 11 13:39 config.properties
-rw-rw-r-- 1 root  boinc 1498 Oct 11 08:51 global_prefs_override.xml
-rw-r----- 1 root  boinc   11 Oct 11 19:25 gui_rpc_auth.cfg
-rw-r--r-- 1 root  boinc  306 Apr 10  2020 remote_hosts.cfg
jstateson@jysdualxeon1:/etc/boinc-client$ cat config.properties
data_dir=/var/lib/boinc-client


and even the links from the data directory have different ownership than the targets which is confusing

jstateson@jysdualxeon1:/var/lib/boinc-client$ ls -l
total 1136
-rw-r--r--  1 boinc boinc   1569 Oct  8 18:51 account_boinc.bakerlab.org_rosetta.xml
-rw-r--r--  1 boinc boinc   5511 Oct 27 06:59 account_einstein.phys.uwm.edu.xml
-rw-r--r--  1 boinc boinc   2129 Oct  4 22:19 account_milkyway.cs.rpi.edu_milkyway.xml
-rw-r--r--  1 boinc boinc   5502 Oct 27 06:59 account_www.worldcommunitygrid.org.xml
-rw-r--r--  1 boinc boinc   1951 Sep 18  2020 acct_mgr_reply.xml
-rw-r--r--  1 boinc boinc   9200 Sep 18  2020 acct_mgr_request.xml
-rw-r--r--  1 boinc boinc  49812 Oct 22 20:43 all_projects_list.xml
lrwxrwxrwx  1 boinc boinc     34 Apr 10  2020 ca-bundle.crt -> /etc/ssl/certs/ca-certificates.crt
lrwxrwxrwx  1 root  root      31 Oct 11 17:40 cc_config.xml -> /etc/boinc-client/cc_config.xml
-rw-r--r--  1 boinc boinc 209336 Oct 28 08:14 client_state_prev.xml
-rw-r--r--  1 boinc boinc 209446 Oct 28 08:14 client_state.xml
-rw-r--r--  1 boinc boinc   4256 Oct 27 06:53 coproc_info.xml
-rw-r--r--  1 boinc boinc  20217 Oct 28 08:14 daily_xfer_history.xml
-rw-r--r--  1 boinc boinc  12642 Oct 22 20:44 get_current_version.xml
-rw-r--r--  1 boinc boinc   2710 Oct  5 22:53 get_project_config.xml
lrwxrwxrwx  1 root  root      43 Oct 11 17:40 global_prefs_override.xml -> /etc/boinc-client/global_prefs_override.xml
-rw-r--r--  1 boinc boinc   6022 Oct 22 20:03 global_prefs.xml
lrwxrwxrwx  1 root  root      34 Oct 11 17:40 gui_rpc_auth.cfg -> /etc/boinc-client/gui_rpc_auth.cfg


The following two items are obviously different from the rest and also the target ownerships are just the opposite.

lrwxrwxrwx  1 boinc boinc     34 Apr 10  2020 ca-bundle.crt -> /etc/ssl/certs/ca-certificates.crt
lrwxrwxrwx  1 root  root      31 Oct 11 17:40 cc_config.xml -> /etc/boinc-client/cc_config.xml
-rw-rw-r-- 1 boinc boinc 2792 Oct 22 20:45 cc_config.xml
-rw-r--r-- 1 root root 199113 Sep 25 06:41 ca-certificates.crt


This system seems to be working fine Some Linux system the apt-get chooses an old version and on other occasions a suggestion is made (here at Berkeley) to use a repository run by someone who keeps the latest and greatest. I assume they (the repository gurus) know what they are doing.

Anyway, I assume all the above is correct since it works but it seems a mix of too many hands in the pot.

[edit] AFAICT I am not a "member of boinc" and do not even know how to join a boinc group but this system seems to work.
ID: 105876 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 4793
United Kingdom
Message 105878 - Posted: 28 Oct 2021, 16:01:15 UTC - in response to Message 105876.  

I think it's the group membership which is critical. Loads of 'HowTo' on the web, like https://linuxize.com/post/how-to-add-user-to-group-in-linux/

The command is

sudo usermod -a -G groupname username
where:
groupname is boinc
username is your Linux account name.

Do the usermod in terminal, and reboot the machine afterwards. Makes it easier to use the BOINC Manager.
ID: 105878 · Report as offensive

Message boards : Questions and problems : Invalid client RPC Password

Copyright © 2022 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.