|
1)
Message boards :
Questions and problems :
Removed MilkyWay as requested by notification -- now can't reconnect to project
(Message 114269)
Posted 9 days ago by Zeiss Ikon Post: I checked the address and it appears the same, but I was using the add menu -- let me try the direct address. [a moment later] Okay, the add menu has https: where the direct address has http: -- but they give the same result. I first get "connecting to project" followed by asking my login credentials, then the progress dot makes one round trip and takes one step on the second before returning to the start position and stopping -- I've had BOINC Manager stand like this for more than five minutes on a couple attempts (in the past, it usually took 10-15 seconds). |
|
2)
Message boards :
Questions and problems :
Removed MilkyWay as requested by notification -- now can't reconnect to project
(Message 114266)
Posted 10 days ago by Zeiss Ikon Post: Every time I try to reconnect to MilkyWay, BOINC Manager freezes and I wind up having to kill the process(es) from htop (Kubuntu 22.04.4, flatpak BOINC). Any suggestions? I'm reluctant to remove a working flatpak install to see if 8.0.2 fixes it, given how much trouble I've had with the .deb version in the past... |
|
3)
Message boards :
Questions and problems :
Four years on, and this still won't just install and work on Ubuntu?
(Message 114218)
Posted 22 days ago by Zeiss Ikon Post: Given BOINC is working under flatpak, I'm a little reluctant to uninstall it and try those instructions, as the last time I used apt to install BOINC I had the RPC password problem and couldn't get it resolved (hence why I switched to the flatpak). |
|
4)
Message boards :
Questions and problems :
Four years on, and this still won't just install and work on Ubuntu?
(Message 114201)
Posted 28 days ago by Zeiss Ikon Post: Okay, following up, flatpak had an nVidia updated today, 535-183-01, and I'm now able to run GPU tasks again. Still getting that message from flatpak that Gnome 44 (apparently used by flatpak BOINC) is EOL, though, and flatpak BOINC is still at manager version 7.22.1... |
|
5)
Message boards :
Questions and problems :
Four years on, and this still won't just install and work on Ubuntu?
(Message 114155)
Posted 20 Jun 2024 by Zeiss Ikon Post: Okay, good news and bad news: Apparently, purging the apt-installed version I was led to by the notification and then running "sudo flatpak repair .edu.berkeley.BOINC" (followed by a restart) has fixed my client -- but now I'm still getting a problem that popped up after a system update earlier this evening: "GPU Missing". I run flatpak nVidia drivers as well, and they're as up to date as they can be (no updates available). According to "sudo flatpak list" I have nVidia 535-171-04. The nVidia driver search says the current recommended version for my graphics card and OS is 550.90.07, though that was only released a couple weeks ago and likely hasn't made it into flatpak form yet... |
|
6)
Message boards :
Questions and problems :
Four years on, and this still won't just install and work on Ubuntu?
(Message 114153)
Posted 20 Jun 2024 by Zeiss Ikon Post: I've been running BOINC (Milky Way and Einstein, for CPU and GPU respectively) for years (and distributed computing since SETI@Home was almost unique), a couple years without issues (I somehow got it to work after installing Kubuntu 22.04 a couple years ago) -- and we apparently still don't have a setup that will "just work" on Linux. I had a notification today to download BOINC 8.0.2, and silly me, I grabbed it immediately and installed it. Now I somehow have Manager 7.22.1 (which might be correct for BOINC 8.0.2??), but when I launch it I get the dreaded "Invalid client RPC password. Try reinstalling BOINC" -- which experience says never works. There's a long thread https://boinc.berkeley.edu/forum_thread.php?id=14013 from 2020-2022 about this, with no clear conclusion as to how to fix it, but I'm certain my group membership and file configuration were okay half an hour ago, and now they're not. I'm not a Linux guru, I just switched when WinXP was getting a little too vulnerable (thirteen years ago) and never had a good reason to put up with Microsoft since. This means I can paste (or type) a command sequence at the CLI, but I'm not really capable of researching for myself how to fix this -- I just like the idea of my computer contributing something useful to the world. FWIW, as noted I'm running Kubuntu 22.04.4 on an AMD Fx8350, 32 GB DDR3 RAM, nVidia GTx2070, Milky Way and Einstein projects (once I can reconnect to them). It occurs to me this may be a problem due to running the flatpak BOINC, and installing the .deb with "sudo apt install" as shown on the page linked from the notification.. Unfortunately, purging the apt-installed .deb (which was probably an older version from the repositories anyway) didn't help. So, now that I'm back to (never left) the flatpak BOINC, how do I resolve the error above? Will waiting for the flatpak to update resolve the problem (I think installing the flatpak is what fixed this for me in 2022)? |
|
7)
Message boards :
Questions and problems :
Old way doesn't work -- how do I change where BOINC looks for its data directory (Kubuntu 22.04)?
(Message 111651)
Posted 23 Apr 2023 by Zeiss Ikon Post: I think we're talking about two different CUDA libraries. I don't have any nVidia development libraries -- but I do have two or three libraries that have description of "compute libraries for CUDA computation" and were automatically installed when ubuntu-drivers installed the upgrade from nvidia 515 to nvidia 530. |
|
8)
Message boards :
Questions and problems :
Old way doesn't work -- how do I change where BOINC looks for its data directory (Kubuntu 22.04)?
(Message 111634)
Posted 22 Apr 2023 by Zeiss Ikon Post: I have the following: Thu 20 Apr 2023 07:35:44 PM EDT | | No usable GPUs found Question is, why, and how do I fix it? The OS detects the hardware: lspci | grep "NVIDIA" The driver is installed and running (not sure why it shows 11 versions??): ubuntu-drivers list So, why wouldn't BOINC have detected the GPU? EDIT: Okay, that was unexpected. I checked flatpak and found there was an update for BOINC; installing it, killing all the BOINC and project processes, and restarting BOINC has apparently fixed this issue. I now have Einstein happily running on 0.9 CPU + 1 GPU, and when BOINC started I had this: Sat 22 Apr 2023 10:15:59 AM EDT | | CUDA: NVIDIA GPU 0: NVIDIA GeForce GTX 1070 (driver version 530.41, CUDA version 12.1, compute capability 6.1, 8106MB, 8106MB available, 6463 GFLOPS peak) |
|
9)
Message boards :
Questions and problems :
Old way doesn't work -- how do I change where BOINC looks for its data directory (Kubuntu 22.04)?
(Message 111627)
Posted 21 Apr 2023 by Zeiss Ikon Post: Well, okay, and the standard software-developer solution for a chicken-and-egg problem is to do something arbitrary that makes perfect sense to a developer (who may or may not have two heads, because all that knowledge won't fit in one) but no sense at all to an end user who's just trying to accomplish what ought to be a fairly straightforward task. But now, I've got an entirely different problem. I was having some issues with update kernels not booting to GUI (in my case, KDE Plasma 5 desktop), which turned out to be due to dkms somehow having gotten uninstalled so the nVidia driver blob wasn't getting built into the new kernels. Working with the Kubuntu forums, I managed to get that fixed (someone posted a link to a one-liner that rebuilds all dkms drivers for all eligible kernels) and now I can boot freshly updated kernels again (I think -- haven't had a new kernel update since the fix). BUT: since fixing that, Einstein@Home is reporting "missing GPU" for all tasks. I'm currently on Kubuntu 22.04.2, with kernel 5.19.0-40-generic (the HWE kernel path) and nVidia 530 (the recommended version for this Kubuntu an kernel) installed via ubuntu-drivers. Every test I know how to run says I have a fully functioning nVidia driver, I have the CUDA libraries installed, and have just installed nvidia-cuda-toolkit in order to check my CUDA version: nvcc --version nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 2005-2021 NVIDIA Corporation Built on Thu_Nov_18_09:45:30_PST_2021 Cuda compilation tools, release 11.5, V11.5.119 Build cuda_11.5.r11.5/compiler.30672275_0 I presume this is a supported CUDA version. This worked on nVidia 515, but I'd have to purge and reinstall nVidia drivers (possibly from command line) to get back to that version; Kubuntu's Driver manager won't even let me try. |
|
10)
Message boards :
Questions and problems :
How to get Flatpak BOINC manager to let the client run when the manager window is closed?
(Message 111613)
Posted 19 Apr 2023 by Zeiss Ikon Post: The Flatpak build patches BOINC to set the default for Stop running tasks when exiting the BOINC Manager to ‘on’. Yep, that seems to have worked. Kind of a non-obvious way to do it, IMO. Now, with the Manager closed, htop shows a bunch of processes that start with "../../projects*" and one that has /app/bin/boinc --redirectio --launched_by_manager-- that latter, presumably, is the one I want to set up to run on system start, but there is no /app folder -- not even inside ~/.var. |
|
11)
Message boards :
Questions and problems :
How to get Flatpak BOINC manager to let the client run when the manager window is closed?
(Message 111606)
Posted 18 Apr 2023 by Zeiss Ikon Post: ./run_client then started the client as did run_manager with the client shut down first. Closing down manager then gave me the exit dialogue so I am guessing the problem lies in the client somewhere. To me, that suggests that the flatpak version 7.22.0 (which is what I have) is missing the ability to leave the client running (as well as to ask when it receives a close input). I've definitely got a running client when the manager is open; I can see the work units ticking down in Tasks tab, and Statistics and Disks tabs reflect the activity as well. I don't see where to execute run_client -- there don't seem to be any executables in .var/app/edu.berkeley.BOINC. |
|
12)
Message boards :
Questions and problems :
How to get Flatpak BOINC manager to let the client run when the manager window is closed?
(Message 111603)
Posted 18 Apr 2023 by Zeiss Ikon Post: Don't know anything about the Flatpak version, but the older versions of the Boinc Manager still had the Options >> Other Options dialog in the menu that gave you the "Enable exit Manager dialog" checkbox. I've been running with the Manager closed for literally years before the buggy version got into the Ubuntu repository. The Flatpak I have installed, however, has the following options in "Options, Other Options": Language Notice Reminder Interval Run the client (checked) Enable Manager exit dialogue (checked) Enable Client shutdown dialogue (checked) Except I haven't been seeing any shutdown dialogs. Changing settings for any of the three doesn't seem to change what happens with the client. |
|
13)
Message boards :
Questions and problems :
How to get Flatpak BOINC manager to let the client run when the manager window is closed?
(Message 111600)
Posted 17 Apr 2023 by Zeiss Ikon Post: After fighting with the repository (Kubuntu 22.04) version of BOINC Manager, I gave up and installed the flatpak version this past weekend. That's working just fine -- except I noticed that my CPU fan wasn't running at high level like it should when my Fx8350 is going full blast on all eight cores. A little poking, and I've determined that it runs fine per preferences when the BOINC Manager is open, but if I close the manager (either with the x button upper right, or with File, Close Window), computation stops. I *think* this means the client service isn't running? The command that would tell the client to start on boot in the .deb install (sudo systemctl enable boinc-client) returns "Failed to enable unit: Unit file boinc-client.service does not exist." I presume this is because the flatpak doesn't offer a system service. There must be a flatpak command that I can put in my autostart so the client runs independent of the manager -- but I don't know what it is. flatpak run edu.berkeley.BOINC launches the manager (which starts the client), but the client ought to run in background whether the manager is running or not. Or is this one of the ways in which the flatpak version isn't quite ready for prime time? |
|
14)
Message boards :
Questions and problems :
Old way doesn't work -- how do I change where BOINC looks for its data directory (Kubuntu 22.04)?
(Message 111599)
Posted 17 Apr 2023 by Zeiss Ikon Post: Occasionally I see something I want to try that I can only get that way but that is no more than two or three times a year. And in twelve years of running Linux exclusively (plus as dual-boot with Windows XP for a couple years before that), I haven't found one. Either I find a source of a compiled binary (*.tar.gz does not scare me, nor do non-repository .deb packages) or I find an alternative. Then again, I'm also not someone who installs new software every week just to try something new; I tend to find a tool that does the job and stick with it (hence why I still install Synaptic and Gparted as soon as I'm up and running on any new install -- the latter saved me when I installed 20.04, because there was a serious bug in the version of KDE Partition Manager that shipped with the 20.04.1 binary). |
|
15)
Message boards :
Questions and problems :
Old way doesn't work -- how do I change where BOINC looks for its data directory (Kubuntu 22.04)?
(Message 111591)
Posted 16 Apr 2023 by Zeiss Ikon Post: if nothing has changed, But you know that's a fantasy state. If you're having to build from source again, it's because you've upgraded your OS, most likely, and you'll also be getting a newer version of the BOINC Manager code. What you learned last year will only serve as guidelines for what you need to do next year. As I tell people from time to time, I don't run Linux because installing and troubleshooting operating systems is a hobby for me, I run Linux because it's (mostly) FOSS, not from Microsoft, fully featured, supports almost every piece of hardware you can plug in, and it has better community support than Windows -- and I don't run/can't afford Apple hardware, so their OS is hard to get running (not to mention completely unsupported on a Hackintosh, and much worse for lock-in than Windows). For instance, I don't like Discover, so one of the first things I do when I get a new Kubuntu install running is install Synaptic with sudo apt update && sudo apt install synaptic. Anyway, my new SSD is installed, /etc/fstab updated to mount a 700+ GB partition as /home instead of the old 160 GB that only had a few GB free, and in that process, the contents of old home copied to new home via Gparted "copy partition" and "paste partition" -- and with all that free space, flatpak BOINC has half a gigabyte of free space and is once again happily churning away. And I was able to expand my / partition to give Kubuntu another 20 GB for its install space, increase my /swap to 32 GB (to match my RAM), give Timeshift 200 GB to store snapshots -- all because BOINC ran out of work space. Now I need to find an efficient way to move hundreds of files from my ~/Downloads into the freed space that was too full as my old /home so I can mount that partition as my ~/Downloads... |
|
16)
Message boards :
Questions and problems :
Old way doesn't work -- how do I change where BOINC looks for its data directory (Kubuntu 22.04)?
(Message 111589)
Posted 16 Apr 2023 by Zeiss Ikon Post: Good grief, that's an annoying bug. Apparently, the Flatpak BOINC Manager will lock up if one of two things happens (not certain which): your first attempt to connect to a project after installation is to one you're already a member of, or you enter an incorrect project password. I tried connecting to a new-to-me project, and it hooked right up; after doing so (and removing the project I wasn't interested in) and looking up the passwords in my browser's manager, I was able to connect to both Einstein and Milkyway and they're now happily waiting for my computer to be "unused" to run tasks. Now I just need to figure out how to move the data directory for the flatpak to the 20 GB partition I set up for BOINC and I can ignore this again until next time I upgrade my Kubuntu. |
|
17)
Message boards :
Questions and problems :
Old way doesn't work -- how do I change where BOINC looks for its data directory (Kubuntu 22.04)?
(Message 111587)
Posted 16 Apr 2023 by Zeiss Ikon Post: I compile mine from source obtained from git-hub Sorting out the dependencies can take a while unless you are more conversant with them all than I am but certainly doable. I've been Debian-based only since 2011 and still haven't done a compile from source that wasn't in a package. Generally, if I have to do that, a software isn't really ready to work for users who aren't Linux wizards. My expertise level is that of someone who can type recommended commands at a command line, make and remove files and directories and navigate the file system (though I prefer to navigate to a folder in Dolphin then "Open terminal here" if it's more than one or two levels up or down or the name of anything in the path will require quoting). Beyond that, I'm like an average Windows user who got fed up with Microsoft's methods back when XP was still supported: IOW, I can follow directions and usually find them on the web, but I don't even attempt to figure out an esoteric multi-option command line on my own. Also, note an edit to my previous post, possibly while/after the above was posted. |
|
18)
Message boards :
Questions and problems :
Old way doesn't work -- how do I change where BOINC looks for its data directory (Kubuntu 22.04)?
(Message 111585)
Posted 16 Apr 2023 by Zeiss Ikon Post: Sigh... I found the direct command to start boinc-client as a service (/etc/init.d/boinc-client which is a good sized shell script). It works, seemingly (status reports running), but starting BOINC Manager kills it, then reports "BOINC Manager (Pre-release) is not able to start a BOINC client. Please run the client and try again." I feel like I'm in a loop here. I've replaced the shortcut method to point to the 20 GB data directory partition with editing /etc/boinc-client/config.properties -- which is apparently the "proper" way to redirect the data directory -- but this seems to have changed nothing. I've been running @Home projects since before they were consolidated into BOINC, except for a couple years when I couldn't take the performance hit and couldn't afford a hardware upgrade. It used to be the case you'd just download the client and manager, install them, connect to your chosen projects, and done. CPU monitor then goes to 100% for all cores when not actively using the machine (at least after getting settings right) and no need to think about it unless something broke it. I have to say, I'm very disappointed with what's available now. I've understood from a thread I found while looking for solutions to this that the Ubuntu packagers grabbed a "not ready" version of the manager and stuck it in their "fully tested" repositories. Is there a way to obtain a Linux version of BOINC without going through the Ubuntu package managers? A Snap or Flatpak? IMO, this is the way something like this should install, especially going forward after this incident with Ubuntu packagers. EDIT: D'oh! BOINC Manager apparently is available as a Flatpak. Let me try installing that instead of fighting with this... And that's not working very well, either. Installed and runs pretty well -- except BOINC Manager locks up at "Communicating with Project" after I enter my password to connect to either of my projects... And it appears this is using my /home for its data directory space again, with no apparent way to change it (I found some hints that this may only be possible after connecting to/installing a project app). |
|
19)
Message boards :
Questions and problems :
Old way doesn't work -- how do I change where BOINC looks for its data directory (Kubuntu 22.04)?
(Message 111583)
Posted 16 Apr 2023 by Zeiss Ikon Post: Okay, new 1 TB SSD installed (thanks, Amazon, for rapid free delivery!). partitioned, etc. BOINC now has 20 GB to play in. Looked up how to create symlinks across different devices (hint: Linux apparently likes to make commands Byzantine in scope, and then create obvious-seeming aliases that don't do what you'd expect them to) so the "boinc" shortcut to "boinc-client" finds another shortcut to an entire partition reserved for BOINC tasks. I had to manually start the client (executing boinc in terminal) before BOINC Manager would let me connect to projects. And after creating the gui_rpc_auth.cfg file (touch gui_rpc_auth.cfg) and enduring the warning that any user on this machine can control BOINC (no problem, I lock the screen when I'm not at console to keep the cats from going on the internet, and they can't type anyway) -- but as soon as I restarted Kubuntu, I got the "can't start the client" popup (despite having been prompted for my password when the desktop loaded) in BOINC Manager. The client service isn't starting when Kubuntu starts up. Edit: By way of a little hack in the autostart settings, I was able to get the client to start -- but now BOINC Manager is telling me "Invalid RPC password. Try reinstalling BOINC." Which I've done (sudo apt reinstall boinc) without change. |
|
20)
Message boards :
Questions and problems :
Old way doesn't work -- how do I change where BOINC looks for its data directory (Kubuntu 22.04)?
(Message 111554)
Posted 14 Apr 2023 by Zeiss Ikon Post:
That's probably the sensible way to do it. Give BOINC ten or twenty GB to work in, and it'll never complain again -- and if it does, I can just clear out that partition and it'll go back to work. And I hadn't realized how cheap SSDs had gotten -- I just got 1 TB and a three-pack of cables for under $60, same-day delivery from Amazon. Last time I bought a terabyte it was a platter drive and cost me $300 or so -- that's the drive that still has the Windows (98 and XP) legacy partitions on it. I should spend a few hours cleaning it up sometime... |
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.