Posts by hadron

21) Message boards : Questions and problems : Unable to launch BOINC CLIENT/MANAGER since upgrade (Message 109902) Posted 28 Sep 2022 by hadron Post: Great. I see that Mint have released an upgrade tool for converting v20.3 installations like mine to v21. I was planning to reduce my computing load from 01 October anyway (when my electricity supplier increases their prices yet again), so I'll take a crunching timeout and try it out. My working hypothesis for the problem you encountered rests on one simple fact: BOINC v7.18.1 was never released for the desktop operating systems Apple, Linux, Windows. It was only ever released for Android. I suspect the Ubuntu repo maintainers saw the Android release notice, and pulled a broken source tree. Now I just need some help in proving it, and examples like this help me down that route. If all that is true, then ask the folks at openSUSE what they did to make it work -- because 7.18.1 does work here, quite well. I am having one problem -- I cannot access the VM Console in the Boinc manager, and I have tried just about everything I can think of to make it work. boinc-client runs as a systemd service when target multi.user (aka runlevel 5) is reached (it is not enabled by default, so must first be enabled: su - systemd enable boinc-client). When boinc is installed, it creates a user and user group, both named "boinc". The client runs as user boinc, and to enable the manager to communicate with it, it is necessary to add yourself to group boinc. Additionally, if VirtualBox is installed, the boinc user must be added to group vboxusers (created when VBox is installed) -- otherwise, boinc-client cannot create a virtual machine. All this works just fine, except as noted above.
22) Message boards : Projects : News on Project Outages (Message 109835) Posted 15 Sep 2022 by hadron Post: I have submitted an email to TACC regarding BOINC@TACC.... Ok I received the following update from the TACC in Austin TX Bill F.... Thanks, Bill. Very disappointing news this is.
23) Message boards : Projects : News on Project Outages (Message 109830) Posted 13 Sep 2022 by hadron Post: Any secure connection attempt to Cosmology@home fails -- I have been trying to join the project, but it appears they must be using a self-signed certificate: both BOINC and Firefox refuse to accept it because it can't be verified. I'm not a a desktop PC to verify... most likely, Cosmology's SSL Certificate is EXPIRED. It was expired one day last week when I tried. Chrome & Mozilla on Android refuses to load website due to insecure SSL connection. Same message as I received on desktop PC's last week. Yes, it is definitely an insecure connection. The reason I think it is a self-signed certificate is because Firefox reports that it cannot be authenticated. If it were an expired certificate instead, then Firefox would report that. I have found some more information on the cosmology@home website. Apparently all admins and above have been AWOL since some time in 2020. I'm giving up on the project, at least for now. If it finally does come back to life, I'm sure I'll find out in short order.
24) Message boards : Questions and problems : "chdir: Permission denied" error when running BOINC on kubuntu 22.04 (Message 109829) Posted 13 Sep 2022 by hadron Post: You can try deleting the password file and hope that boinc will just generate another, but I suspect you are going to have to re-install boinc. Whatever does work, you also need to add yourself to group boinc, and if you are using virtualbox, you need to add user boinc to group vboxusers (or whatever Ubuntu may be calling it). DON'T do that. If you don't understand what you're trying to achieve, it's worse than useless. First, make sure the BOINC client is listening for a known password. You've changed the password in gui-rpc-auth.cfg to 123456 - that's fine: it's not a high-security data risk. But now you must re-start the BOINC client, to make sure it's listening for the new password. Second, look at the launcher for the BOINC manager. Examine its properties. If the 'Command' line just says "boincmgr", change it to: boincmgr --password=123456 Now, the client and the manager are on the same page - they're speaking the same language. There's a key for the lock. They should work together. People who do know are here to assist those who do not, are we not? Since deleting gui-rpc-auth.cfg clearly does not work, the file can easily be recreated -- but a suggesting a trivial password like 123456 is hardly the proper response. The password should be a 32-character random hexadecimal code (represented, of course, in text format). If you do need to create a new file, make sure to set the owner/group to boinc/boinc, and set the permissions as 0640 (rw-r--) Even worse is to fire up the boinc manager with the password embedded in the startup command so every system user can use it -- even if it's not a security risk, it means any system user can access your boinc operation and do whatever they please with it, a risk I think most of us would choose to avoid. There is a proper way to do all this, which, unfortunately, is not well documented -- it took me hours of searching to find it. But here it is, for everyone to read. Many have already posted most of it, but alas, it seems to have been swept away in an awful lot of noise. These instructions are for openSUSE 15.4, but should work on any Linux distro. After installing boinc client, boinc manager and virtualbox, first go into your system's user/group manager (you will need root access to do this), and look for group "boinc" -- it will be a system group. Add your user to that group, which will allow the manager to connect with the client (that will be run under your user account, so it inherits all your access privileges -- including being able to read the password file). Next, you must allow the boinc client to start up virtualbox. When that was installed, it will have created a group called something like vboxusers (that is the openSUSE group name, other distros may vary). Add user "boinc" to that group. Now, everyone who needs to talk to someone else can do so, and no prying mischievous 15-year-old kid can mess with it (unless, of course, your user password is trivial, and the kid has hacked into your user account). Now you want to set up the client so it starts automatically when the system boots. By now, most distros should be using systemd rather than sysconfig to boot the system. This greatly simplifies this part. Open a console and run this command: sudo systemctl list-units --all \|grep boinc This will tell you all the systemd services that have "boinc" in their names; in openSUSE, the relevant one is called boinc-client.service. You need to enable this to get the client to start on system boot: sudo systemctl enable boinc-client To start the client immediately, run this sudo systemctl start boinc-client Now you can fire up the manager, and since it can read all the boinc files (being a member of group boinc), it can talk to the client. The client itself, being a member of vboxusers, has enough access to start up the virtual machine whenever it is needed. Systemd is a steep learning curve for everyone who has spent years working with sysconfig. However, once you start getting used to it, you will see just how much it simplifies system control. The key is to take it slow and easy at the start -- and above all else, do NOT go hacking the service files, unless you REALLY know what you are doing. I'm still learning, and it's been nearly a year and a half since I first encountered systemd (starting with Leap 15.3). And by all means, if you start to think you are getting into trouble, STOP, come back here, and ASK.
25) Message boards : Questions and problems : "chdir: Permission denied" error when running BOINC on kubuntu 22.04 (Message 109811) Posted 12 Sep 2022 by hadron Post: Same condition here. Fresh load of Ubuntu 20.04.01 Ran the following command: sudo apt install boinc-client boinc-manager (according to instructions at https://boinc.berkeley.edu/wiki/Installing_BOINC_on_Ubuntu As instructed launched BOINC by the icon found under applications. File programs shows file belongs to root and to BOINC group Used nano to edit gui-rpc-auth.cfg to enter 123456 as a random password After this instead of getting the notice that var/lib/boinc-client permission denied.... I get nothing.... Any help would be appreciated. Thank you. Don You can try deleting the password file and hope that boinc will just generate another, but I suspect you are going to have to re-install boinc. Whatever does work, you also need to add yourself to group boinc, and if you are using virtualbox, you need to add user boinc to group vboxusers (or whatever Ubuntu may be calling it).
26) Message boards : Projects : News on Project Outages (Message 109794) Posted 11 Sep 2022 by hadron Post: WCG have obviously fixed their certificate issue as site is back up and uploads and downloads are happening albeit even more slowly than before presumably due to how the servers are getting hammered with the backlog. Things are improving, especially transfer speeds. I just got a new project arrive less than 15 minutes ago, all in under 3 minutes. Oh, and it all arrived without any of those infamous "transient HTTP errors".
27) Message boards : Projects : News on Project Outages (Message 109793) Posted 11 Sep 2022 by hadron Post: Any secure connection attempt to Cosmology@home fails -- I have been trying to join the project, but it appears they must be using a self-signed certificate: both BOINC and Firefox refuse to accept it because it can't be verified.
28) Message boards : Projects : News on Project Outages (Message 109792) Posted 11 Sep 2022 by hadron Post: The URL for BOINC@TACC no longer resolves to an IP address. I haven't contacted TACC to see if the project is dead, as I think that is best left to someone officially connected with BOINC.

Previous 20

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.