I tried to follow the thread about getting BOINC to work on Linux, and I got lost...

Message boards : Questions and problems : I tried to follow the thread about getting BOINC to work on Linux, and I got lost...
Message board moderation

To post messages, you must log in.

AuthorMessage
Zeiss Ikon

Send message
Joined: 2 Jul 17
Posts: 30
United States
Message 110830 - Posted: 31 Dec 2022, 0:08:39 UTC

I recently "upgraded" from Kubuntu 20.04 to Kubuntu 22.04 -- which involved a failed do-release-upgrade, followed by (or due to) a failed power supply, and after replacing that, three or four reinstalls of Kubuntu 22.04 (interspersed with a Boot Repair that may have a bug -- one of the copy-paste commands it told me to enter seemed to delete a lot of OS-critical files, leading to one or those reinstalls).

I've now got the system up and running, seemingly stable (except that I don't get GRUB if I do a software restart -- works fine otherwise, though), and I'm getting my stuff working again. Today it's BOINC's turn (well it was, yesterday, but I didn't get there).

I installed the boinc-manager, boinc-client, boinc-client-nvidia-cuda, boinc-screensaver, and whatever depends they brought with them.

Then I started getting the infamous error message that seems to revolve around gui_rpc_auth.cfg. I've tried to follow this thread (https://boinc.berkeley.edu/forum_thread.php?id=14013), but I got lost about ten posts in. I think I've added my userid to the boinc group, but there doesn't seem to be a way (in this version of Kubuntu) to open a root-owned file with the system text editor (Kate) "because of unfixable security problems."

I've just purged all of the above packages, manually (as root) deleted the /etc/boinc and /etc/boinc-client folders, and reinstalled only boinc-manager, boinc-client, boinc-client-nvidia-cuda (depends didn't get removed, as I didn't run an autoremove), and now BOINC Manager will open, but will not show a list of projects; manually entering a project URL (https://milkyway.cs.rpi.edu/milkyway/) gives a message roughly "this project may not have tasks for this type of computer" -- on a project I've run for years.

I have an AMD Fx8350 (8 cores/threads, 4.1 GHz maximum), 32 GB RAM recently tested good, nVidia GeForce GTx1650 w/ 4 GB VRAM; my / and /home are on different partitions of a 256 GB SSD, with more than 10 GB free in / and 30 GB or so free in /home. I was running BOINC with Milkyway (CPU only) and Einstein (GPU only) on this machine for a couple years before the failed Kubuntu upgrade.

What am I missing (and why doesn't this work the way the instructions say it should)?
ID: 110830 · Report as offensive
Zeiss Ikon

Send message
Joined: 2 Jul 17
Posts: 30
United States
Message 110831 - Posted: 31 Dec 2022, 0:18:47 UTC - in response to Message 110830.  

Oh, sure, and as soon as I posted the above, it started working...

Never mind...
ID: 110831 · Report as offensive
Zeiss Ikon

Send message
Joined: 2 Jul 17
Posts: 30
United States
Message 110835 - Posted: 31 Dec 2022, 15:20:06 UTC - in response to Message 110831.  

Hmmm. Okay, now that my BOINC tasks are downloading and computing, I've got another oddball situation: when I start my computer, i get a popup asking for authentication for the BOINC client -- and my user password for the computer lets it run (or it'll time out after a minute or so, and just vanish, leaving boinc-client not running). What's up with this?
ID: 110835 · Report as offensive

Message boards : Questions and problems : I tried to follow the thread about getting BOINC to work on Linux, and I got lost...

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.