boinc has been running for years on this system. I went to check statistics this afternoon. I found boinc manager wouldn’t start properly with message below. I have not made any changes to boinc in months. I have v8.2.8 as installed by openSUSE tumbleweed. asteroids@home is currently running in client..

Boinc message upon start of boinc manager ----> "Invalid client RPC password. Try reinstalling BOINC"

I did the suggested reinstall of boinc manager as suggested with no change. boinc client is still running as I can see the cpu usage in “system manager”. I can also see the boinc transfer messages in lnav. No tab works on the gui so there is no re-login possibility. I also did a system reboot.

I don’t know what an RPC password is.
This could also be a boinc connection issue with no openSUSE involvement.


Anyone else seeing this issue?

thanks, tom kosvic

I have seen it on a number of occasions in the past. Sometimes adding my user to the boinc group has resolved it. As a last resort, sometimes I have made myself the owner of /var/lib/boinc or boinc-client on older systems.

Problem solved by steps below found on internet search:

Generate a New RPC Password
Use the following command to create a new password:

sudo apt -y install pwgen
pwgen 30 1 | sudo tee /etc/boinc-client/gui_rpc_auth.cfg


Set Correct Permissions
Ensure that the permissions for the RPC password file are set correctly:

sudo chown root:boinc /etc/boinc-client/gui_rpc_auth.cfg
sudo chown root:boinc /var/lib/boinc/gui_rpc_auth.cfg

Add User to BOINC Group
Add your user to the BOINC group to allow access:

sudo usermod -a -G boinc $USER

Restart the BOINC Client
Finally, restart the BOINC client to apply the changes:

sudo systemctl restart boinc-client

Just in case, this issue should be automativally solved if out vanilla package is installed: https://boinc.berkeley.edu/linux_install.php

---

BOINC maintainer.
For any insight, check my BOINC Development Blog.

someone suggested changing permissions on /var/lib/boinc-client/ to 664, NOPE, so I blasted it open 777, and poof it worked. I just cant stand trying "minimal" permissions. I know 777 works. ! LOL Good Luck

---