The officially official Devuan Forum!

You are not logged in.

#1 2017-07-14 14:36:12

ghaverla
Member
From: Dawson Creek, BC, Canada
Registered: 2017-06-19
Posts: 28

Boinc

I had boinc running on the first (of 4) Debian/Jessie machines which got upgraded to Devuan/Jessie, and then got upgraded again to Ascii/Ceres.

It had been running fglrx (aka Catalyst) as it had a HD 5450 in it.

Before the upgrade, I changed settings in the manager so that it did not download new work.  And it was allowed to finish all the work it had, and upload it.

I upgrade systems seldom and how to properly upgrade boinc in such a situation is not fluid in my head.  I thought it would be enough to just let the existing jobs finish.

As doing OpenCL via open source has improved a lot via Mesa3D, LLVM and others, I was thinking of seeing if this HD 5450 could be made to work with the open source OpenCL system.

I downloaded the various boinc packages from Devuan and tried to set things up get it working again.  At one point it had downloaded some work.  But trying to get the manager to communicate with the client only worked that one time.  Starting the manager from the GUI menu had different effects than starting from the command line.  gui_rpg_auth.cnf was a problem.  The new (on Devuan) package seems to want to start a data store in the user's $HOME, which I had never seen before.

Some of this may be the difference from Debian/Jessie to Debian/Sid.  It could be something done in conversion to Devuan.  I spent the day fighting things and not getting anywhere.  At one point, I downloaded strace and collected a strace log of the boincmgr (23k lines).  I didn't finish wading through that.

Growing frustrated, I wondered what was available from upstream.  My other Debian systems are running a 7.6.x version of boinc.  The boinc site has a 7.2.x package available?  Sorry, I don't want to go that far backwards.  Okay, over to the git and clone it.  It is version 7.7, so newer than what I was working with.  A few hiccups in getting dependencies of the compile going, but I've compiled much of that now.  It wants to work with MySQL to be a boinc server (almost nobody needs that, that is for projects to distribute work units), and doing a quick search it doesn't look like anyone has converted to MariaDB.  I have to go get farm parts today, so it will be a few hours before I can look at the results of the compile to see if that works here.

Maybe the gremlins will diffuse out of the system, and re-installing boinc from scratch again (I did it 3 or 4 times yesterday) may then work.  Maybe someone with better boinc-fu than I, may happen on this note and realize what I did wrong (my old boinc /var/lib/boinc-client is still on the old hard disk if I need it) and point me to the error.

Thanks for any wisdom/comments.

--

As Red Green has been known to say, "Keep your stick on the ice.".

Offline

#2 2017-08-13 02:40:34

ghaverla
Member
From: Dawson Creek, BC, Canada
Registered: 2017-06-19
Posts: 28

Re: Boinc

Hmmmm, no replies.  Aka - Gord, do more work.

Okay, we'll see what happens.  I've got a system move from an ATX to a mini-ITX, and a new system to go into the ATX tower.  All wanting to do BOINC.

Have a great day people!

Offline

#3 2017-08-13 03:04:13

ghaverla
Member
From: Dawson Creek, BC, Canada
Registered: 2017-06-19
Posts: 28

Re: Boinc

Churn on things for a minute or ten.

There were always two different problems with BOINC:
1. A user wants to run BOINC when they are logged in.
2. The system wants to run BOINC all the time (to use up cycles).

What I had on Debian, is solution 1, except that the data is kept in /var, which is a system thing.

It seems to me, that the "overview" package needs to be one, which will allow a system BOINC process to run, or allow whoever is logged in to X to run BOINC processes.  And then a person installs a boinc-system and/or boinc-user packages to handle the specifics.

Easy for me to say, I have never written something like this.  I think.  Maybe.  Sometimes.  Without enough beer.

Ideas?

Offline

#4 2017-08-13 17:21:23

leloft
Member
Registered: 2017-08-10
Posts: 6

Re: Boinc

I am also experiencing Boinc problems after upgrading to ascii this morning.  It appears to be related to the kernel version:

Machine 1: upgraded between Sun, 13 Aug 2017 11:14:00 +0100 and Sun, 13 Aug 2017 11:39:04 +0100 from jessie to ascii using

deb     http://auto.mirror.devuan.org/merged ascii main
deb-src http://auto.mirror.devuan.org/merged ascii main
deb     http://auto.mirror.devuan.org/merged ascii-updates main
deb-src http://auto.mirror.devuan.org/merged ascii-updates main
deb     http://auto.mirror.devuan.org/merged ascii-security main
deb-src http://auto.mirror.devuan.org/merged ascii-security main
deb     http://auto.mirror.devuan.org/merged ascii-backports main
deb-src http://auto.mirror.devuan.org/merged ascii-backports main

# Devuan repositories
deb http://packages.devuan.org/merged ascii main
deb-src http://packages.devuan.org/merged ascii main

Boinc: 7.6.33
kernel: 3.16.0-4-amd64
Boinc working on 4/4 cores, but unable to use boinccmd
********************************************************

Machine 2 upgraded between Sun, 13 Aug 2017 04:00:09 +0100 and Sun, 13 Aug 2017 04:33:18 +0100 from jessie to ascii using

deb http://gb.mirror.devuan.org/merged/   ascii main
deb-src http://gb.mirror.devuan.org/merged/ ascii main

# jessie-security, previously known as 'volatile'
deb http://gb.mirror.devuan.org/merged/ ascii-security main
deb-src http://gb.mirror.devuan.org/merged/ ascii-security main

# jessie-updates, previously known as 'volatile'
deb http://gb.mirror.devuan.org/merged/ ascii-updates main
deb-src http://gb.mirror.devuan.org/merged/ ascii-updates main

# jessie-backports, previously on backports.debian.org
deb http://gb.mirror.devuan.org/merged/ ascii-backports main
deb-src http://gb.mirror.devuan.org/merged/ ascii-backports main

# Devuan repositories
deb http://packages.devuan.org/merged ascii main
deb-src http://packages.devuan.org/merged ascii main

Boinc: 7.6.33
kernel: 4.9.0-3-amd64
Boinc working on 1/2 cores only, unable to use boincmd
***************************************************
Machines 3,4,5 running devuan jessie
Boinc: 7.4.23
kernel: 3.16.0-4-amd
Boinc running on 2/2 cores on all three machines, boinccmd works.
***************************************************
Note: the machine that upgraded from gb.mirror upgraded the kernel, but the machine that upgraded from auto.mirror did not.
I now have two versions of ascii one running the 3.16.0-4 (jessie) and one running the 4.9.0-3.
I am locked out of the 4.9.0-3 machine following a reboot.
I don't think it's the firewall (connection tracking modules not loaded in 4.9.0-3): turning iptables into ACCEPTing everything doesn't help with the boinccmd issues.

Offline

#5 2017-08-14 03:07:42

ghaverla
Member
From: Dawson Creek, BC, Canada
Registered: 2017-06-19
Posts: 28

Re: Boinc

leloft wrote:

I am also experiencing Boinc problems after upgrading to ascii this morning.  It appears to be related to the kernel version:

[ snip ]

I am not the greatest sysadmin debugger in the world.  Do you have logs (from the /var/log or from $HOME/.xsession*)?  Are they showing anything?  Do you get any more information if you start the programs from a command line, instead of from a GUI?

Offline

#6 2017-08-14 03:19:12

ghaverla
Member
From: Dawson Creek, BC, Canada
Registered: 2017-06-19
Posts: 28

Re: Boinc

ghaverla wrote:

Churn on things for a minute or ten.

Tonight, I compiled the client side of the BOINC source tree (from BOINC, not from Debian/Devuan).  And it is version 7.7.0 I believe.

Well, it is a different compile process than I have seen before.  And very little documentation as to what make targets are present, and what they are for.  I tried a make test, and there is no test target (maybe only CPAN has this typically?).  Looking in the Makefile, I tried a make dist, and that failed.  Make install should usually fail for ordinary users, as they shouldn't have write permission to /usr/local.  But changing to root and running make install, did install some stuff.

Boincmgr runs, it doesn't like that the BOINC core client isn't running.  Something for tomorrow.

----

In terms of what BOINC packages installs, at the present time dpkg -l | grep boinc reports boinc is not installed.  I do have "old" packages installed.  There are no *inst files related to boinc on the system.  All of the devuan packages show each package has debian-binary, control-tar.gz and data.tar.gz components.

----

In any event, tomorrow I will see if I can get the core client running even though there are no jobs.  It could be interesting as I need to specify where these are stored, and what I ran into on Devuan was this stuff was going in $HOME, and not in /var.  But maybe I will figure out what is going on.

Offline

Board footer