Recent posts

#1

ALL THINGS LINUX / Re: Problems running Boinc

Last post by Lennox84 - Yesterday at 10:22:11 PM

AMAZING!! Giving it a crack now. That's exactly what I needed

Just an update tho...

On Ubuntu it's in /etc/boinc-client
a /var/lib/boinc-client exists too with the same default config as what's in the /etc/boinc-client directory - Not sure if they're symlinked or not.
I've been editing the files in /etc/boinc-client for the other changes because of this line on the Berkely site - (see pic) so I'll continue to make the modifications there unless something blows up, but it's confusing that they're duplicated in the 2 different locations. Unless "It's not a bug, it's a feature" ??

LOL After taking the screenshot to share point 3 answered my above statement LOL  You cannot view this attachment. 

also the file cc_config.xml doesn't have the options in the file but there's a hyperlink that takes you to where all the options and log flags are: https://boinc.berkeley.edu/wiki/client_configuration

Either way, it feels good to finally start making some real progress. 

#2

ALL THINGS LINUX / Re: Problems running Boinc

Last post by Dark Angel - Yesterday at 09:52:52 PM

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.

#3

ALL THINGS LINUX / Re: Problems running Boinc

Last post by Lennox84 - Yesterday at 09:18:57 PM

Success!!! Thank you all for the help.You cannot view this attachment.

Dark Angel the file worked in seconds so that's perfect

Dingo, seems like I went the long way round but I'm much smarter because of it... 
I'll get the other systems setup and crunching then just so I can feel the raw achievement of the last few days of stress and then switch to BoincTasks moving forward because it just seems like a better solution but I've come this far already so might as well bask in the glory.

I'd prefer to use boinctasks over the Boincstats site to manage my systems I would think.

It's been a crazy last few days but I'm confident I've got my ducks in a row now... next step is XPAND LOL 

#4

ALL THINGS LINUX / Re: Problems running Boinc

Last post by Dingo - Yesterday at 09:12:55 PM

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.

#5

ALL THINGS LINUX / Re: Problems running Boinc

Last post by Lennox84 - Yesterday at 09:09:37 PM

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.

#6

ALL THINGS LINUX / Re: Problems running Boinc

Last post by Lennox84 - Yesterday at 09:06:27 PM

Ok that helps along with this doc too: https://boinc.berkeley.edu/trac/wiki/RpcAuth

So the reason the Unraid setup works is it's loading Boinc with --allow_remote_gui_rpc but I'm not sure how I'd do that on my Ubuntu server setup because it auto-starts the standard Boin-client instance without that option... I'm assuming there's a way to do that but it's unknown to me how I would do that.

Would it be something like "Sudo systemctl enable boinc-client ----allow_remote_gui_rpc" ??

At least this file would be easy enough, much like the changes I make to the hosts file on my setups (I run a few static routes too so this is a similar exercise).

So this file should live in /etc/boinc-client if I'm not mistaken?? Jumping in now... Wish me luck

#7

ALL THINGS LINUX / Re: Problems running Boinc

Last post by Dingo - Yesterday at 08:50:44 PM

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

#8

ALL THINGS LINUX / Re: Problems running Boinc

Last post by Dark Angel - Yesterday at 07:56:50 PM

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.

#9

ALL THINGS LINUX / Re: Problems running Boinc

Last post by Lennox84 - Yesterday at 05:47:05 PM

Thanks heaps for this.

So it seems I've been confused about my issue. Looks like I'm installing Boinc ok and it's active and all. But I'm trying to remote into my Boinc from Boinc Manager on my laptop and I can't see it like I can when I remote into the server and after some digging I think I might understand why but maybe not... Let's see how this goes.

Gui RPC is defaulted to 31416
I have my server running Boinc in a docker (See BOINC Unraid.png)
When I log into this from Select computer in Boinc Manager I see full task list etc.. (See Boinc Manager) and this is the kinda access I want to achieve because I need to link each system to bamSTATS so I can manage things remotely with groups etc..

But when I try and do this to my new box it never connects, it stays connecting unlike when I do so with the server (Says Connected).
I've attached the status results of the new box (See Big Boss CMD.png)

could it be a firewall issue? (See Big Boss CMD.png)
I never had that issue with my Server but maybe that's because Unraid did some cool stuff in the background?

I've been having the same issue on both Fedora and Ubuntu, So I'm thinking it's either a setup piece I'm missing of a network thing I'm missing but my Unraid server worked like a charm with no special setup.

Extremely appreciative of any and all assistance. Hopefully,You cannot view this attachment.You cannot view this attachment.You cannot view this attachment.    I don't sound like a complete buffoon.

My Unraid server has been running/crunching like a dream, so I'm trying to increase my footprint but I've gotta say this has been a real pain to try and get going.

#10

ALL THINGS LINUX / Re: Problems running Boinc

Last post by Dingo - Yesterday at 04:40:16 PM

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.