Posts by MarkJ

1) Message boards : BOINC Manager : Boinc manager does not connect in openSUSE 15.2 (Message 95433)
Posted 3 days ago by MarkJ
Post:
Re: Log files

Debian (and probably all the derivatives) have switched to using the system logs and not the text files that are used under windows, To view the logs under Debian you can use the journalctl command. You might need to prefix it with a sudo.

Example: sudo journalctl --unit=boinc-client
2) Message boards : GPUs : no usable GPUs found fedora 31 workstation (Message 94388)
Posted 19 Dec 2019 by MarkJ
Post:
Because you have a GTX970 you could use an older driver from Nvidia, not the 440. I found this site that has instructions about installing the official Nvidia drivers which might help.
3) Message boards : GPUs : no usable GPUs found fedora 31 workstation (Message 94384)
Posted 19 Dec 2019 by MarkJ
Post:
So according to that there aren’t any usable GPUs which suggests you don’t have the right driver installed. It also says you’ve installed the pocl OpenCL which there are reports of it not being suitable for projects to use. I’d suggest getting rid of it.

I use Debian and have to install the nvidia-kernel-dkms package along with nvidia-opencl-icd. Seeing as you’re using Fedora that won’t work for you. A quick google search came up with this: https://rpmfusion.org/Howto/NVIDIA#About_this_Howto which has a section on CUDA. I’m not sure how up to date it is and there is no mention of the RTX2000 or the GTX1600 series of cards (ie current models). You’ll need CUDA and OpenCL to use them on most BOINC projects. There is mention of them being a third party ppa on the Fedora site.
4) Message boards : GPUs : no usable GPUs found fedora 31 workstation (Message 94344)
Posted 18 Dec 2019 by MarkJ
Post:
Did you reboot after installing the drivers?

Usually BOINC will tell you what if found in its log, the first 20 lines or so should show what it found. Please post those log lines.

From memory all it does is look for the OpenCL.so and CUDA libraries in particular folders. Given the 440 drivers are new it’s possible Nvidia put then in a new location.
5) Message boards : Questions and problems : Not sending work: Last request too recent - what does this mean? (Message 94343)
Posted 18 Dec 2019 by MarkJ
Post:
I get "Not sending work - last request too recent: 22 sec". To me that means I have to wait 22 sec (which is clearly not true - it's actually telling me a useless piece of information - when I last made a request). This is shown the same in the standard Boinc Manager and in Boinctasks (although in Boinc manager I have to go into the event log to see it - Boinctasks shows it in the messages tab). Why doesn't it say "Please wait a further 2.5 minutes"?

Those messages are in the log (Messages tab in BOINCtasks and Event log in BOINC Manager).

The back-off timer is shown on the Projects tab in BOINCtasks and BOINC Manager. In both cases it is shown on the right side where it displays other info such as “No new tasks” and “Scheduler request in progress”, etc.
6) Message boards : Questions and problems : Not sending work: Last request too recent - what does this mean? (Message 94298)
Posted 16 Dec 2019 by MarkJ
Post:
If using manager under status it says communication deferred and counts down to when you can request work again. under the projects tab.

[Slaps self on face] I forgot about checking in there (I use Boinctasks to control all my machines which shows the above). Although I still stand by my assertion that the response I got should have told me the time before possible communication, not how long since I last asked.

It’s a countdown timer, so it is the time until you can make another scheduler request. Once the timer goes away you can tell it to update, or let BOINC do it on its own.

Note that you can sometimes manually make another request before the timer expires provided you aren’t asking for work, example you set it to ”no new task” and then tell it to update which would report any completed work and update any prefs changed on the project website. The timer would then restart from the project back-off interval again.
7) Message boards : BOINC client : gpu ONLY tasks not executing on Boinc (Message 94259)
Posted 14 Dec 2019 by MarkJ
Post:
I prefer working from the idea that the controls are centralized to the software, rather than remote.
Remote settings mostly work if you have multiple devices that are relatively identical (meaning, all have Nvidia or ATI GPUs, or all run CPU jobs), and can work on the same settings (eg: do Seti on all my devices).

There are two things for that. One is BOINCtasks and the other is an account manager.

BOINC supports a few different AM’s such as BAM and GridRepublic where you can standardise your settings across projects. See https://boinc.berkeley.edu/wiki/Account_managers

BOINCtasks is good for managing a fleet of machines. See https://efmer.com/
8) Message boards : Questions and problems : Are Risc CPUs supported? (Message 94258)
Posted 14 Dec 2019 by MarkJ
Post:
Yes, I know ARM is supported, but is the RISC architecture supported?
There exist RISC V based servers, would they be compatible with the ARM software?

There are many RISC architectures. They are not compatible with each other. Apps compiled for ARM CPUs won’t work on the Alpha, Power9, RISC V or Sparc, etc.

The projects will support the popular ones, like the x86_64 and ARM. Then there are different OS’s to consider. They don’t have the staff, time or budget to support less common architectures or OS’s. As Richard has said you could possibly get the source code and compile it on your target architecture if it’s not specifically supported.
9) Message boards : Questions and problems : Are Risc CPUs supported? (Message 94248)
Posted 14 Dec 2019 by MarkJ
Post:
Seeing they're basically a derivative of ARM processors, I wondered if boinc and possibly any projects supporting Risc CPUs?

Actually RISC CPUs were around well before ARM came along. There are a number of different ones and they are not compatible with other brands.

The Raspberry Pi uses an ARM chip along with many other low-power devices, particularly mobile phones and tablets. There are a few projects supporting the Pi (Asteroids, Einstein and Seti that I can think of off-hand). A few projects also support Android tablets. Because of their low-power design they tend to be slow, like 10 hours a workunit or more.
10) Message boards : Questions and problems : Xeon phi (31S1P) still beneficial in 2019 (Message 94189)
Posted 11 Dec 2019 by MarkJ
Post:
Hi!
I bought a Intel 31S1P Xeon Phi, a passively cooled PCIE card, because it was cheap.
Now I want to know what to do with it. So Boinc it will be.

1- Are they considered CPUs, or GPUs? (I presumed they'd be a CPU co processor using the PCIE interface)?
2- Are there any projects supporting this card?
3- Does Linux support this PCIE card?
4- Are they still relevant to today (considering the later Nvidia and AMD GPU alternatives out there with 4000+ GPU cores)?

As far as I know there aren’t any BOINC projects that can use the Xeon Phi. You would be better off using an AMD or Nvidia GPU which various projects can make use of.
11) Message boards : GPUs : GPU 0 suspended and GPU 1 always computing (Message 94119)
Posted 9 Dec 2019 by MarkJ
Post:
Given that cc_config.xml is an optional file, does anyone happen to know whether the file and the symlink are created 'empty' by the installer, or whether they appear after first use?

From memory the package installer has a cc_config.xml that has a couple of the logging flags set to their default values, so it’s not an empty file and it’s present once you’ve installed the boinc-client package.
12) Message boards : GPUs : GPU 0 suspended and GPU 1 always computing (Message 94084)
Posted 8 Dec 2019 by MarkJ
Post:
/etc/boinc-client

The 4 files in /etc/boinc-client/ are sym linked to the ones in /var/lib/boinc-client/ so while it appears you have one in each folder they are the same files. You can edit it in either folder.
13) Message boards : Questions and problems : BOINC not seeing 3rd GPU (Message 94082)
Posted 8 Dec 2019 by MarkJ
Post:
could use some help....
thanks :)

We could too. How about providing some information?

Lets start with the top 20 or so lines of the BOINC log where it shows which devices are detected, what OS you’re running and if it found the cc_config file or not.
14) Message boards : BOINC Manager : Raspberry Pi updating. (Message 93899)
Posted 25 Nov 2019 by MarkJ
Post:
Was wondering is there a terminal command to update the BOINC software version ? Don't really want to remove and re add the software again on the older Pis

I can't see a update section inside the manager

The usual way to keep all the software up to date is using apt or aptitude. BOINC doesn’t have an update function.

From a terminal window (or ssh into it from another machine) and at the prompt type:
sudo apt update (to update the list of available packages)
sudo apt upgrade (to download the updates and install them)

Buster has BOINC client and manager version 7.14.2

If you’ve been running them for a year then you may still be running stretch. I’d suggest clean installing Buster if you’re still on stretch. That means download the image from raspberrypi.org and re-image your SD card and then reinstall BOINC.
15) Message boards : Questions and problems : HTTP Timeouts On All Request Types (Message 93859)
Posted 22 Nov 2019 by MarkJ
Post:
Have you tried setting http 1.0? From the BOINC client configuration page:

<http_1_0>0|1</http_1_0>
Set this flag to use HTTP 1.0 instead of 1.1 (this may be needed with some proxies).

Put it under the options tag. After that restart client. I wouldn’t expect any difference if browsers and other things work fine but you never know.
16) Message boards : BOINC client : Controlling BOINC with household programmable thermostat? (Message 93736)
Posted 16 Nov 2019 by MarkJ
Post:
If you could write something to pass the on/off to the system you probably could just use boinccmd to suspend processing. Maybe just touch a file for the “on” event and have a script that checks if the file exists every 5 minutes or so and then issue a boinccmd to resume or suspend.

One drawback would be if BOINC stays suspended for a couple of weeks then tasks will time out so you’d need to somehow finish off the work on hand when you transition from winter (heating mode) to spring or summer.
17) Message boards : BOINC Manager : Boinc in a Raspberry Pi with VNCServer does not show BoincManager (Message 93735)
Posted 16 Nov 2019 by MarkJ
Post:
There is BOINCtasks, see efmer.com. You can use it to control BOINC on multiple machines. It’s great when you have headless (ie no keyboard or screen) computers. No need to install remote access software like VNC, BOINC manager or X11.
18) Message boards : Questions and problems : Can’t connect to localhost (Message 93119)
Posted 7 Oct 2019 by MarkJ
Post:
Jessie had 7.4.23, stretch had 7.6.33 and Buster has 7.14.2. We’re currently testing 7.16. If you’ve used the repo version I expect you’ll be running the 7.4.23 version. You can do a “boinccmd—version” without the quotes to see what it thinks it’s got.

Back to the issue at hand, can you see if boinc-client is running. If it installed correctly then it should start up when the Pi does. Try “sudo service boinc-client status” without the quotes to see if it thinks it’s running “sudo service boinc-client start” to get it going.
19) Message boards : Questions and problems : Can’t connect to localhost (Message 93113)
Posted 6 Oct 2019 by MarkJ
Post:
Ian, you refer to running Jessie, the current version of Raspbian is Buster. Is there some reason you are 2 OS versions behind?

The command line tool used to have issues. What happens if you cd to /etc/boinc-client and do the boinccmd from there?
20) Message boards : BOINC Manager : boincmgr will not start on Ubuntu LINUX when left over file /home//BOINC Manager- (Message 92984)
Posted 28 Sep 2019 by MarkJ
Post:
I just tried under Debian using the repo version of BOINC (7.10 in this case). It creates a "BOINC Manager-<ID> file in the users home folder while the manager is running. Its deleted when you exit the manager (successfully). I guess because yours crashed it got left behind.

It looks like its designed to prevent running more than one instance of the manager per user. I tried the "File -> New BOINC Manager window" option and not surprisingly it doesn't work.


Next 20

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