Problems running Boinc

[tazzduke]

Also let us know how you went.

[NudgeyNR]

Tried the rest of the commands and it did not work.

Still have to manually run it via a sudo command.

[tazzduke]

Hi NudgeyNR

which command do you have to run as sudo??

On another note, you could also spin up another VM running Kubuntu 22.04 and then do the instructions (if you have the time or energy), cause it could be something to do with Kubuntu 22.10.

Regards

[tazzduke]

Bugger, its something to do with the extra security they implemented in Kubuntu 22.10.

I installed a fresh VM of Kubuntu 22.10, installed Boinc, via the package manager.
Then I had to do the following steps as well, this was after trying to start the boinc.client service.  it told me my user was not in the sudoers file.

Add the normal user to the SUDO group by doing the following
Type SU in a konsole, this will switch to the Root, (should be the same password you use to login with)
Type in the following command usermod -aG sudo username (where username is the name of the user)
reboot the system.

That should fix it.  I managed to get BOINC up and running on a Kubuntu 22.10 VM / BOINC Version 7.20.2

Regards

[NudgeyNR]

Good Evening NudgeyNR

Well I went and spun up a Kubuntu 22.10
Completed the updates,
I installed the boinc software, using the muon package manager.

Need to add the normal user to the sudoers file, before it can do sudo commands.
To do this
Open up a Konsole and switch to root by doing the following.
Type in SU and press enter
It will ask for a password, this is normally the same one that you log in with.
Then enter the follwoing command
usermod -aG sudo username (username is the name of the normal user for the machine)
Once this has been done, reboot the machine.

Now you should be able to complete the following successfully.

Then you will need to do the following - in a normal user console.

1. start boinc service

sudo systemctl start boinc-client.service

2. to add user to boinc group

sudo /usr/sbin/usermod -G boinc -a $(whoami)

3. add read/write permission to

sudo chmod g+rw /var/lib/boinc

4.  symlink as per Berkeley

ln -s /var/lib/boinc/gui_rpc_auth.cfg /home/username/gui_rpc_auth.cfg

"Where username is the actual username for the user of that machine"

Logout (or reboot) and log back in.

5.  Start Client Service

sudo systemctl start boinc-client.service

6. Auto start the service on boot

sudo systemctl enable boinc-client.service.

FInd your BOINC shortcut in the menu and double click on it.

Hope this got you going, as it worked for me.

Oops forgot to add, if this has worked for you, next is to get the actual boinc-client to autostart on boot

goto application launcher
goto settings
goto system settings
select startup and shutdown
select autostart
select add (to add an application)
select system
select boinc
select ok

Now we should be all good and up and running.

Let me know how it goes. also allow for a bit of time difference and work schedule.

Regards

PS.  Edited due spelling errors and also we were dealing with Kubuntu 22.10 which is different to Kubuntu 22.04.

After the new change(s) everything is working as it should.

I had to redo all the commands then reboot.

Thanks for your time and effort tazzduke much appreciated.

[tazzduke]

You are welcome NudgeyNR

I have to redo my Kubuntu install again, I didn't give it enough hard drive space lol.

Cheers

[tazzduke]

Gday Lennox84

I found the information on the following link, which also helped getting a Fedora Workstation running boinc here last year.

https://www.overclock.net/threads/guide-installing-boinc-on-fedora-25-and-fedora-26-fedora-27.1633927/

Don't worry about the title, it should be fine with the latest version of Fedora.

Cheers

[tazzduke]

Glad to hear Lennox84

I prefer Linux Mint myself, have tried a plethora of distributions except anything ARCH related.

Back in the days of running Seti, I just found Linux Mint came easy to me thats all.

Nowadays I run Linux Mint 20.2, cause it lets me run certain apps from LHC@Home.

Cheers

[Dingo]

I just use the version of BOINC on Ubuntu.  sudo apt update sudo apt install boinc

A long time ago in 2003 I used to create my own BOINC to fit the Linux machine I had at the time.  I think this script may still work Or you can use it as a reference.

If you are using Ubuntu then BOINC is installed to /usr/bin and not in /opt/boinc.  Save as a file like loadboinc.sh and chmod +x loadboinc.sh

I have attached the file as a txt file as it would not let me paste the code into the message.



[attachment deleted by admin]

[Dark Angel]

By default Boinc will only allow manager access from the local host.  To access it from another machine you either need to allow it universally in the cc_config.xml file (not reccommended for security reasons) or put the remote host's IP address or device name (if you have local name resolution)in the remote_hosts.cfg file.

The default content of the file looks like this:
# This file contains a list of hostnames or IP addresses (one per line)
# of remote hosts, that are allowed to connect and to control the local
# BOINC core client via GUI RPCs.
# Lines beginning with a # or a ; are treated like comments and will be
# ignored.
#
#host.example.com
#192.168.0.180

Personally I use IP addresses but I use static IPs for my crunchers and only one can access the others.

[Dingo]

I and a few others use BOINC Tasks as you can set it up to see all your computers in one place and have all the functionality of BOINC Manager and much more.

You need the IP address and the password.  The password ins in the BOINC folder file called gui_rpc_auth.xml



[attachment deleted by admin]

[Dingo]

I and a few others use BOINC Tasks as you can set it up to see all your computers in one place and have all the functionality of BOINC Manager and much more.

You need the IP address and the password.  The password ins in the BOINC folder file called gui_rpc_auth.xml

But for this to work I'll need the solution from Dark Angel setup 1st right? or does BoincTasks circumvent that??

Don't get me wrong I like the look of it and will definitely look at it, but with my current problem, it would seem my Boinc installs aren't set up for remote access because the --allow_remote_gui_rpc option is not set so BoincTasks wouldn't have access if I'm understanding right.

You don't need to setup remote gui rpc as BoincTasks will connect if it has the IP and Password.  Boinc does need to be started on the remote machine for it to work.

[Dark Angel]

On the Ubuntu server, assuming you installed from teh repositories, the file where that option is permanently set is:

/var/lib/boinc-client/cc_config.xml

You need to either be su or run your editor with sudo to edit it.

Scroll through it and you'll see a heap of options.

[Dark Angel]

AHhh yes.  The ones in /var/lib/boinc-client are also links to the others.  I just checked my server install to see what was going on as I always access them from the directory I gave you and never noticed they are links.

[Dark Angel]

These 403 error pages when I try to post legitimate content are getting very frustrating