Message boards : Questions and problems : (k)ubuntu 23.10 upgrade causes 'invalid client RPC password. Try re-installing boinc manger' error message
Message board moderation
Author | Message |
---|---|
Send message Joined: 18 Oct 23 Posts: 1 |
Version 7.22 Kubuntu 23.10 World Community Grid ' Invalid client RPC password. Try re-installing boinc manager' error message I've upgraded to Kubuntu 23.10 from 23.04 and have since got this error. I have checked permissions on boinc link in /var and I have tried re-installing but no difference. CPU AMD Ryzen 9 5900x (12 core, 24 threads) GPU Nvidia Gefore 1650 Can't get any event-log information. |
Send message Joined: 28 Jun 10 Posts: 2721 |
Try adding yourself to the boinc group sudo usermod -a -G boinc yourusername I haven't tried the upgrade yet but have 23.10 running in a VM but didn't have this problem, probably because I installed BOINC compiling from source rather than using the packaged version. |
Send message Joined: 5 Oct 06 Posts: 5131 |
We (I) think this is a false error message: the password is likely to be unchanged and correct, but the OS upgrade has changed and tightened the security regime. The Manager runs in user mode, but the client (which does all the work and generates the event log messages) runs as a system service. What's probably happening is that the Manager is unable to read the 'gui_rpc_auth.cfg' file which contains the password. The first thing to try is adding your user name for the system, to the 'boinc' user group: sudo usermod -a -G groupName userNameReboot the system to make the change effective. Edit: If that doesn't work, it's possible that your system isn't set to auto-start the 'boinc-client' service at startup. Try sudo systemctl start boinc-clientUse the other systemctl options - stop, disable, enable - to control BOINC from there on. |
Send message Joined: 28 Jun 10 Posts: 2721 |
My setup doesn't autostart the client at boot but does start it on starting the manager. I don't think you get the "Invalid client RPC password" message if the client isn't running. Instead you get, "Unable to connect to running client" in bottom right hand corner of manager assuming you have advanced view. Edit: I have now updated my host machine to Mantic and the issue has not occurred with me but I always add myself to the boinc group and am still running 7.25.0 compiled from source code from git-hub |
Send message Joined: 5 Oct 06 Posts: 5131 |
See my comments on this specific error message in https://github.com/BOINC/boinc/issues/4460 |
Send message Joined: 28 Jun 10 Posts: 2721 |
Nothing I have read about security changes with 23.10 is relevant to this. I do know that upgrades to previous editions of Ubuntu have also caused this problem as a quick search of these boards shows. A completely fresh install with BOINC never having been on the system before works but upgrading to the next iteration produces this error. How much is something to do with the package managers and how much to do with the code at git-hub I couldn't say. |
Send message Joined: 14 Apr 12 Posts: 51 |
It could be this also: https://github.com/BOINC/boinc/issues/3355 I had directed edited the systemd file, so they were overwritten, other had pointed out the better way is to create an override file then it won't get overwritten. Working fine after this |
Copyright © 2024 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.