Problems running Boinc

[Lennox84]

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

[Lennox84]

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.

[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.

[Lennox84]

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 

[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.

[Lennox84]

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. 

[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

[Lennox84]

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

Oh Ok so I was thinking that was just happening to me because I use brave... Obviously it's a wider issue.

Yes I agree it's a bit of a pain. Atleast we don't lose the data we tried to post so I can cut, reload and post.

When I was posting my bigger response below with attachments I was 💩ing bricks I needed to remember the whole thing again.

[Lennox84]

Has anyone successfully run Boinc flatpak with GPU crunching...?

Can't seem to run repo Boinc on Fedora 38 (Maybe building myself would be better as it seems likely a permissions issue but a bit above my Linux knowledge)

The flatpack works for CPU crunching no problem but it won't crunch on my AMD 5700xt (I had the flatpak on an old M4600 with an Nvidia m200 and it ran CPU and GPU no problem, but it was an ubuntu derivative hence my thoughts on Fedora being overly protective). It can see the GPU in the event log but it has computation errors and fails.

I don't know if I want to move to Ubuntu as my main distro but I'm pretty invested in building out a solid crunching farm and this issue is stopping my big rig to come only :-(

As always, all help is appreciated.

[Dark Angel]

Has anyone successfully run Boinc flatpak with GPU crunching...?

Can't seem to run repo Boinc on Fedora 38 (Maybe building myself would be better as it seems likely a permissions issue but a bit above my Linux knowledge)

The flatpack works for CPU crunching no problem but it won't crunch on my AMD 5700xt (I had the flatpak on an old M4600 with an Nvidia m200 and it ran CPU and GPU no problem, but it was an ubuntu derivative hence my thoughts on Fedora being overly protective). It can see the GPU in the event log but it has computation errors and fails.

I don't know if I want to move to Ubuntu as my main distro but I'm pretty invested in building out a solid crunching farm and this issue is stopping my big rig to come only :-(

As always, all help is appreciated.

You need to be running the proprietary GPU drivers to be able to use them for crunching.  The open source ones just don't include the OpenCL/CUDA capability.

[Lennox84]

Thanks for that DarkAngel
So I've discovered more and a solution:

AMD no longer has proprietary drivers for Fedora as they are baked in (But no OpenCL Compute capability), they offer pro drivers but that's another story. What we really need is ROCM as that uses proprietary OpenCL drivers we need for Boinc (Compute)

Natively it didn't work for me however I used this guide for a docker image and it worked perfectly: https://hub.docker.com/r/boinc/client/#amd-gpu-savvy-boinc-client-usage

This Reddit was also helpful - https://www.reddit.com/r/Fedora/comments/13lld18/help_how_to_install_amd_gpu_drivers/

Hope this helps someone in the future.

I'm going to see how I can leverage Docker for my Boinc setups moving forward too I think.