gui_rpc_auth.cfg exists but can't be read. Check the File permissions.

Message boards : Questions and problems : gui_rpc_auth.cfg exists but can't be read. Check the File permissions.
Message board moderation

To post messages, you must log in.

Previous · 1 · 2

AuthorMessage
Profile joelhuebner

Send message
Joined: 21 Mar 21
Posts: 2
United States
Message 103631 - Posted: 21 Mar 2021, 20:01:29 UTC - in response to Message 101190.  

chmod 664 /etc/boinc-client/gui_rpc_auth.cfg is the file permissions command that worked for me.

I tried all the others in this thread, still was getting the "permissions" message.

TY VM
ID: 103631 · Report as offensive     Reply Quote
JohnMD

Send message
Joined: 27 May 16
Posts: 8
Denmark
Message 103640 - Posted: 21 Mar 2021, 23:28:16 UTC

Isn´t time you "know-alls" got to the bottom of this ?
I'm just an amateur that wants to donate.
ID: 103640 · Report as offensive     Reply Quote
Stevo.acts

Send message
Joined: 9 Apr 21
Posts: 1
United States
Message 103913 - Posted: 9 Apr 2021, 18:21:52 UTC - in response to Message 101190.  

Following the steps you provided only fixed half the problem. The other part :
sudo nano journalctl -u boinc-client.service
(Now type 7883508 into the box)
Save and go back to terminal.
Type :
systemctl restart boinc-client
Then you're all good.
ID: 103913 · Report as offensive     Reply Quote
Bryn Mawr
Help desk expert

Send message
Joined: 31 Dec 18
Posts: 238
United Kingdom
Message 103917 - Posted: 9 Apr 2021, 21:28:44 UTC - in response to Message 103913.  

Following the steps you provided only fixed half the problem. The other part :
sudo nano journalctl -u boinc-client.service
(Now type 7883508 into the box)
Save and go back to terminal.
Type :
systemctl restart boinc-client
Then you're all good.


What is the significance of the 7883508?
ID: 103917 · Report as offensive     Reply Quote
Gort

Send message
Joined: 23 May 21
Posts: 1
United States
Message 104473 - Posted: 25 May 2021, 16:59:42 UTC

Tried all this .... except the last post... still no joy.
ID: 104473 · Report as offensive     Reply Quote
linuxcruizer

Send message
Joined: 23 Mar 20
Posts: 2
United States
Message 104621 - Posted: 25 Jun 2021, 20:51:26 UTC - in response to Message 104473.  
Last modified: 25 Jun 2021, 20:55:27 UTC

Hello,

I have been down this same rabbit hole, and it is very frustrating when you have 7 machines, and two of them (HPs) continued giving me the same errors that you experienced, and the other five PCs start services has the Boinc Manager GUI waiting on my desktop (setup using the commands found here <https://boinc.berkeley.edu/wiki/Stop_or_start_BOINC_daemon_after_boot> , but I digress...).

I ended up aptitude purging as well, then with Krusader, I searched the entire filesystem for anything related to boinc and deleted. Rebooted, used the download instructions again, found on World Community Grid <https://www.worldcommunitygrid.org/ms/viewDownloadAgain.action>

Using the last command from the download guide of "boincmgr -d/var/lib/boinc-client", (no joy) and then "sudo boincmgr -d/var/lib/boinc-client" I again received the rpc password failure.

Using Krusader as root, I went into the "/etc/boinc-client/gui_rpc_auth and input my password (the one I use for Boinc for both Rosetta@home and World Community Grid) and saved.

Using Debian/Ubuntu/Linux Mint/KDE desktop distribution (don't ask, I just like it), I used the command <update-rc.d boinc-client defaults 98> in Konsole (Terminal) to start boinc-client at startup, and rebooted my computer.

The Boinc Manager was on the desktop waiting for me to add project(s) or using my account manager.

I then ran a status command of <service boinc-client status> on Konsole to make sure boinc was running and found this:
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 Fri 2021-06-25 13:43:53 CDT; 38min ago
Docs: man:boinc(1)
Main PID: 1378 (boinc)
Tasks: 13 (limit: 17835)
Memory: 3.1G
CGroup: /system.slice/boinc-client.service
├─1378 /usr/bin/boinc
├─3071 ../../projects/www.worldcommunitygrid.org/wcgrid_mcm1_map_7.43_x86_64-pc-linux-gnu>
├─4955 ../../projects/boinc.bakerlab.org_rosetta/rosetta_4.20_x86_64-pc-linux-gnu -run:pr>
├─4976 ../../projects/boinc.bakerlab.org_rosetta/rosetta_4.20_x86_64-pc-linux-gnu -run:pr>
└─4978 ../../projects/boinc.bakerlab.org_rosetta/rosetta_4.20_x86_64-pc-linux-gnu @foldit>

Jun 25 13:53:35 computer'sname boinc[1378]: 25-Jun-2021 13:53:35 [Rosetta@home] Started download of asy>
Jun 25 13:53:49 computer'sname boinc[1378]: 25-Jun-2021 13:53:49 [Rosetta@home] Finished download of as>
Jun 25 13:53:49 computer'sname boinc[1378]: 25-Jun-2021 13:53:49 [Rosetta@home] Started download of fol>
Jun 25 13:53:52 computer'sname boinc[1378]: 25-Jun-2021 13:53:52 [Rosetta@home] Finished download of fo>
Jun 25 14:01:59 computer'sname boinc[1378]: 25-Jun-2021 14:01:59 [Rosetta@home] Finished download of da>
Jun 25 14:02:22 computer'sname boinc[1378]: 25-Jun-2021 14:02:22 [Rosetta@home] Starting task pre_helic>
Jun 25 14:02:35 computer'sname boinc[1378]: 25-Jun-2021 14:02:35 [Rosetta@home] Starting task pre_helic>
Jun 25 14:02:35 computer'sname boinc[1378]: 25-Jun-2021 14:02:35 [---] Suspending computation - CPU is >
Jun 25 14:02:45 computer'sname boinc[1378]: 25-Jun-2021 14:02:45 [---] Resuming computation
Jun 25 14:02:58 computer'sname boinc[1378]: 25-Jun-2021 14:02:58 [Rosetta@home] Starting task foldit_20>
lines 1-24/24 (END)

Now remember, that the Boinc Manager started at system startup, so I decided to exit the Boinc Manager to determine if my Boinc application would start Boinc Manager. So, after closing Boinc Manager, I went to: start (application launcher)>Applications>System>Boinc and clicked on the icon which resulted in previous behavior of starting and then disappearing........so I right clicked on the Boinc Icon found at start>Applications>System>Boinc and chose edit application. I then went to the Applications Tab and entered the following:
Command: /var/lib/boinc-client
Work Path: boincmgr
and then clicked OK.

I checked the system monitor to insure that Boinc was not running and then again went to start>Applications>System>Boinc and clicked on the Application Icon for Boinc. The Boinc Manager came up and started with no issues.

This has been a long an arduous journey, fraught with downloading, uninstalling, purging, reinstalling, starting from boot, and finally hacking the command and work path for the Boinc Desktop Application in order to get things working.

From what I have learned from going through all of the searches, this is a common issue for some Distros and not for others. For instance, when I was running Linux Mint Cinnamon, Boinc just worked without any issues. I began having issues when I layered KDE on top of Linux Mint. Also, of note, I had updated my boinc-client/boinc manager to version 7.16.17(x64) wxWidgets version 3.0.4. I am still not sure why the rpc password issue began.

Summary:
I found that if I did not purge all that was boinc before reinstalling, that nothing I did would work, and even after purging everything boinc, I still had to hack the Command and Work path of the boinc application to get the boinc client and boinc manager to start and behave properly.

This is definitely an issue that needs some attention. My experience has been purging, reinstalling, start the boinc-client at startup and then hack the Boinc Manager icon application properties. Has a lot of my issues been self inflicted? Probably. Is this going to work for everyone? Probably not.

Thanks to everyone for their input and feedback across this post. I wish you all good luck in finding the solution for all of those having similar issues.
ID: 104621 · Report as offensive     Reply Quote
linuxcruizer

Send message
Joined: 23 Mar 20
Posts: 2
United States
Message 104623 - Posted: 26 Jun 2021, 3:49:05 UTC

Update: The following may be of interest: I discovered after the stop of a boinc account manager, no more issues. Next, I changed back from KDE to a Cinnamon Desktop. The operation of my Desktop with the boinc managers has gone back to being very stable. The two PCs that I have left with KDE desktops became stable after removing the Boinc Account Manager and tweaking /etc/default/boinc-client "# Set this to 1 to enable and to 0 to disable the init script.
ENABLED="1" (see footnote)
As stated in prior post, this allows the boinc client and boinc manager to run at startup.

I am not sure why the boinc account manager was causing me issues, or it maybe it was my layered distribution. I really like using a KDE desktop, but I have found that I have a new appreciation for the stability of my Cinnamon Desktop.

Thanks again for everyone's input, all of your heavy lifting has helped.


footnote: tweaking information was gleaned from <https://boinc.berkeley.edu/wiki/Installing_BOINC_on_Ubuntu>
ID: 104623 · Report as offensive     Reply Quote
Rudolfensis

Send message
Joined: 6 Dec 08
Posts: 10
Benin
Message 109207 - Posted: 13 Jul 2022, 22:19:25 UTC

I will admit that this error and the other one about var/etc/boinc_client can't be read (something like that combination of directory but don't totally remember if that's the exact one) made me question 2 things.

First... installing totally untouched Linux OS'... one after the other. Like Ubuntu, Cento... which ever I would get this AUTH error or the file can't be read error and made me really think why do these errors exist in the first place? They are untouched OS, just freshly installed, no new software but BOINC and each time run into a brick wall right after installing BOINC client/manager.

Second thing was... the hours I've spent going down rabbit holes trying to figure instructions which lead to even more problem made me wonder why I was even bothering trying to run BOINC on Linux. I mean it was so idiotic at some point I realize that some of the instruction were not even updated on BOINC's site itself. One of that was giving a command line "Sudo aptitude... " which on the latest Ubuntu does not even exist, there is no such a thing as APTITUDE software on 20.04 (I think that was the number or 20.4).

I was about to give up till I decided to try another OS called BEEPIN and BOOM! Not only Boinc works right after installing but I'm able to log into my account and make the laptop work again.

This still doesn't address the reason why BOINC is not able to spread a software version for Linux which almost never works unless you have a University degree in software engineering. Why these two errors comes up on almost all fresh OS?
ID: 109207 · Report as offensive     Reply Quote
Profile Keith Myers
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 17 Nov 16
Posts: 736
United States
Message 109208 - Posted: 14 Jul 2022, 1:36:04 UTC - in response to Message 109207.  

Because of certain BOINC developers that think security is paramount in running BOINC and users should have no control over the BOINC installation.

You can always sidestep the distro versions of BOINC and install using the original Berkely installation mechanism. I've never used a distro version of BOINC on any of my x86/x64 hosts. Only on the ARM devices which has no Berkely installer.

You can get the Berkeley installer here. http://www.arkayn.us/lunatics/BOINC.7z


ID: 109208 · Report as offensive     Reply Quote
hadron

Send message
Joined: 5 Sep 22
Posts: 15
Canada
Message 110251 - Posted: 27 Oct 2022, 14:43:41 UTC - in response to Message 101198.  

The Linux tools for ensuring that the Manager can read - and thus supply - the requisite password from gui_rpc_auth.cfg are woefully inadequate.
No, the Manager should not need, and not be able, to read that file at all. The user has to provide the password to prove they're authorised to control the Client. To make that work the password has to be secret, enforcing a password and then allowing everybody to look it up is just absurd. You could add authorised users to the boinc group as you suggested and then allow only those to read the password file. In fact that's what I do, but I'm sure that's still not how it was intended to work. The Manager has the ability to read the password from a file but I don't think that was meant to read the Client's password file but one provided by the user. Correct me if I'm wrong. For me the whole concept of someone else reading the Client's private file is only added by the Linux packagers and it's another case where the convenience vs security decision goes in the wrong direction.


By default, no ordinary user is a member of group boinc; they must be added to that group at administrator level. If you are a member of group boinc, then it should be rather obvious that you are authorized to use boinc -- including the manager. Permissions 0640 are correct. Every user cannot then read the password file, because they are not members of group boinc.
ID: 110251 · Report as offensive     Reply Quote
hadron

Send message
Joined: 5 Sep 22
Posts: 15
Canada
Message 110252 - Posted: 27 Oct 2022, 14:56:09 UTC - in response to Message 103599.  

I've found a new (?) page, which may assist readers and save them wading through this whole thread.

Accessing BOINC on Linux

The final suggestion on that page is

exec su $USER
That only works if you want to launch BOINC Manager from the command line in terminal. If you want to use a graphical launch icon on your desktop, or a menu item created by your distribution, you'll need to reboot the machine.


That command should be sufficient to allow $USER to use the manager without rebooting or logging out and back in. In openSUSE 15.4, I added my own account to group boinc from YaST, the SUSE sysadmin tool, and was immediately able to use the manager. Presumably, every other distro's sysadmin tool should give the same result.
ID: 110252 · Report as offensive     Reply Quote
Previous · 1 · 2

Message boards : Questions and problems : gui_rpc_auth.cfg exists but can't be read. Check the File permissions.

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.