Posts by Keith Myers

Info	Message
41) Message boards : Projects : News on Project Outages Message 113865 Posted 6 Apr 2024 by Keith Myers	https://asteroidsathome.net/ is apparently down right now.
42) Message boards : BOINC Manager : GPU tasks being crowded out by CPU tasks Message 113757 Posted 11 Mar 2024 by Keith Myers	No, you could use a max_concurrent statement separately for each task type in an app_config.xml file. Just put in two separate <app_version> statements. https://boinc.berkeley.edu/wiki/Client_configuration#Application_configuration
43) Message boards : Projects : News on Project Outages Message 113741 Posted 8 Mar 2024 by Keith Myers	Asteroids has a expired SSL certificate. No connections possible until they renew.
44) Message boards : Projects : TN-Grid Message 113716 Posted 3 Mar 2024 by Keith Myers	That project notice was from over two weeks ago. Those tasks lasted about 3 days. Been out of work for over a week now.
45) Message boards : Questions and problems : Suspend not working properly Message 113695 Posted 28 Feb 2024 by Keith Myers	You just weren't using the BOINC Manager and client correctly. Boinc is rather difficult for beginners to use and navigate all of its idiosyncrasies, If you had suspended either the project or the tasks in the Manager, Boinc would have been truly suspended and not interfered with your actual work. The Boinc gadget in the task bar or whatever Windows thingy is called only suspends Boinc and tasks for an hour and then resumes processing.
46) Message boards : Questions and problems : Can't get virtual work. Message 113654 Posted 22 Feb 2024 by Keith Myers	For LHC VBox tasks to work, I also had to change something in the bios. I can't remember exactly what off hand. It was in addition to allowing virtualisation. From Google AI answer you also need to enable IOMMU in the UEFI along with virtualization to get Oracle VM Virtual Box to work. Yes, you need to enable IOMMU and virtualization extensions to enable PCI passthrough in Oracle VM VirtualBox. PCI passthrough allows a virtual machine to use a host device as if it is directly attached to the VM. An IOMMU hardware unit is required for PCI passthrough support to be fully functional. An IOMMU is required if the device uses bus mastering. For example, if it performs DMA to the OS memory on its own.
47) Message boards : Questions and problems : New Mini PC Kamuri AM08Pro Message 113645 Posted 20 Feb 2024 by Keith Myers	That machine is certainly more than capable of running VB tasks. Amateur radio isn't going to be that demanding on the machine. I would check whether the projects you intend to run have VB tasks. If they do install the version with Virtual Box otherwise leave it out. +1
48) Message boards : BOINC Manager : new HD error Message 113629 Posted 15 Feb 2024 by Keith Myers	After I installed new HD using the clone feature iI get the error msg 2/14/2024 9:36:24 AM \| \| Unrecognized tag in cc_config.xml: <options> 2/14/2024 9:36:24 AM \| \| Error in cc_config.xml options 2/14/2024 9:36:24 AM \| \| Missing end tag in cc_config.xml 2/14/2024 9:36:24 AM \| \| Starting BOINC client version 7.24.1 for windows_x86_64 It seems to boot and run OK, but the error annoys me. Any help for the technically challenged user? TIA RWP Copy the contents of your cc_config.xml file and parse it through the XML Validator here: https://www.xmlvalidation.com/index.php The validator will tell you the error and where the missing tag is.
49) Message boards : Questions and problems : BOINC Invalid client RPC password. Try reinstalling BOINC Message 113617 Posted 15 Feb 2024 by Keith Myers	Works if you are still running any LTS of Ubuntu versions 20 or less. I would have thought if everyone had this problem with versions 21.x and above of Ubuntu, we would have heard a lot more about it here. Only from users of the AIO. And from the previous post, I guess most people have never tried it. So no reports of any issues if there are not many using it. All my teammates use it as the base BOINC configuration before adding more support for our special apps. I never use any repo version BOINC unless the AIO is not available for the platform like with my Raspberry Pi's. Only then do I have to do the permissions dance with files and folders under root. As, I stated, Ubuntu flavors past 20 have deprecated libssl1.1 library and only supply libssl3.0 now. But it is a simple fix to add the missing library back in with a download of the libssl1.1 library from the OpenSSL repository. http://security.ubuntu.com/ubuntu/pool/main/o/openssl/openssl_1.1.1f-1ubuntu2.21_amd64.deb sudo dpkg -i openssl_1.1.1f-1ubuntu2.21_amd64.deb
50) Message boards : Questions and problems : BOINC Invalid client RPC password. Try reinstalling BOINC Message 113612 Posted 14 Feb 2024 by Keith Myers	In other words, no, this site's software is hopelessly broken? Then I'll give up, I guess. Up to you. Works if you are still running any LTS of Ubuntu versions 20 or less.
51) Message boards : Projects : Anything and Everything to do with (WCG) World Community Grid Message 113610 Posted 14 Feb 2024 by Keith Myers	WCG down again. 503 error
52) Message boards : Questions and problems : BOINC Invalid client RPC password. Try reinstalling BOINC Message 113607 Posted 13 Feb 2024 by Keith Myers	Lunatics was the original expert or power user Seti app, tech tips, utilities website. Been around forever. Forums are no longer there but all the special apps are still available. The two devs that developed the SETI applications hung out there. The BOINC.zip file is what is referred to as the All-in-One version of Boinc. It is a full installation of Boinc that is just unzipped into your /home directory. Everything is already set up with all files and folders in place with the local user permissions set. To get Boinc running all one needs to do is unpack the file and double-click on the Boinc Manager and that starts the Boinc client. Just need to start adding projects via the standard Manager interface. Older client that was compiled under Ubuntu 20.04 so you need to add the older OpenSSL 1.1 library to get it to run under Ubuntu 22.04 or later because the those later versions dropped 1.1 versions and moved to 3.0 versions of OpenSSL. Just wanted to point out the easy way to solve your issue. There is a much harder way to move all the files, folders, links and permissions of a distro version of BOINC into the /home folder if you want to go that way. As long as you are comfortable with the command line and have some time, you can get the newer repo versions moved to /home also.
53) Message boards : Questions and problems : BOINC Invalid client RPC password. Try reinstalling BOINC Message 113599 Posted 13 Feb 2024 by Keith Myers	Using a /home located folder for BOINC solves a multitude of problems. I personally like the original Berkeley installer version colloquially known as the All-In-One installation. Can be found at the Lunatics website. http://www.arkayn.us/lunatics/BOINC.7z
54) Message boards : The Lounge : Grumbles, Glory and All Your Off Topic Discussions Message 113592 Posted 12 Feb 2024 by Keith Myers	Probably not useful. Requires Boinc apps to be PTX or run-time compiled. AFAIK, all Boinc apps are already full binary blobs.
55) Message boards : The Lounge : Grumbles, Glory and All Your Off Topic Discussions Message 113565 Posted 7 Feb 2024 by Keith Myers	Do what the message states. Quit Firefox so the snap can update. Look in your System Monitor and kill the instance that is still running. If you don't see any instance there then just stop Firefox through snap. sudo snap info firefox sudo snap stop firefox sudo snap refresh sudo snap info firefox sudo start firefox If you still get the message try: sudo snap stop firefox sudo snap disable firefox sudo snap refresh sudo snap enable firefox sudo snap info firefox sudo snap start firefox
56) Message boards : Questions and problems : Where is the cc_config.xml file suppose to live? Message 113541 Posted 3 Feb 2024 by Keith Myers	The BOINC data directory location is always printed out in the beginning of the stdoutdae.txt file, IOW the BOINC Event Log. If you can find that file, it will tell you where BOINC thinks its data directory is located. As Jord states, client and project preferences are in the global_prefs and global_prefs_override xml file in the data directory.
57) Message boards : BOINC client : No suitable wxWidgets library found. Message 113477 Posted 27 Jan 2024 by Keith Myers	I only build the boinc-client. May be I will need to build the boinc and start a the same time. If you only build the client, you shoudn't be getting any warning for wx-widgets. The gtk and widgets libraries are only needed for the manager ./_autosetup ./configure --disable-server --disable -manager --enable-client make
58) Message boards : Questions and problems : Where is the cc_config.xml file suppose to live? Message 113476 Posted 27 Jan 2024 by Keith Myers	If /var/lib/boinc is also where the project folders are . . . that is the correct location.
59) Message boards : BOINC client : Downloading Extra Work Message 113431 Posted 23 Jan 2024 by Keith Myers	Some projects, in fact, most projects set a physical limit on how many tasks a host can hold or be sent. Projects set rules for how many cpu tasks or how many gpu tasks based on the number of cores in the host or the number of gpus the host has. This does not always align with the days of work setting in the client. My favorite project has a limit of sixteen gpu tasks per host. That's it. No more than that can ever be held on the host. Granted some tasks take half a day to run, but some only take an hour or less. You just have to accept what the project imposes for their rules.
60) Message boards : Questions and problems : GUI RPC password not generated in BOINC headless Message 113430 Posted 23 Jan 2024 by Keith Myers	You can input your own password in the file. It does not have to be the salted, auto-generated password the software is supposed to create. The password can be anything you want. Even blank, no password needed.

Copyright © 2025 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.