Posts by David Anderson (not *that* DA)

1) Message boards : Number crunching : boincmgr not finding projects redux (Message 2035757)
Posted 4 Mar 2020 by Profile David Anderson (not *that* DA) Project Donor
Post:
The previous was just....wrong. I knew this yesterday during
the weekly outage, so now I'll correct the mistakes and show a
shell script any Unix/Linux user might find useful
if and only if one is having trouble connecting to existing projects
with boincmgr or boinccmd.

(Below using xxd, a standard Linux hex dumper program
to display the file content.)
A correct example of the gui rpc cfg files is (remember the
contents of each should match the others but any
content will work), followed by a shell script that
I found useful to create.

-rw-r--r-- 1 root root 7 Feb 26 15:10 /etc/boinc-client/gui_rpc_auth.cfg
00000000: 6d79 6163 6374 0a myacct.

-rw-r----- 1 boinc boinc 7 Feb 26 15:10 /var/lib/boinc/gui_rpc_auth.cfg
00000000: 6d79 6163 6374 0a myacct.

-rw-r----- 1 boinc boinc 7 Feb 26 15:10 /var/lib/boinc-client/gui_rpc_auth.cfg
00000000: 6d79 6163 6374 0a myacct.

owner of of /home/davea/gui_rpc_auth.cfg should be davea
-rw-rw-r-- 1 davea davea 7 Mar 3 11:13 /home/davea/gui_rpc_auth.cfg
00000000: 6d79 6163 6374 0a myacct.


#!/bin/sh
# In case you have a system with boinc project(s) and
# boincmgr and boinccmd cannot see the project(s)
# you may have an authorization error.

# the command
# strace boinccmd --set_run_mode never
# may help to see if it is an authorization issue.

#The following is commented so it just shows what is what.
#To actually do anything to the files uncomment lines
#as necessary.

# Pick a hex dump program you have on hand. xxd is standard Linux.
hx=xxd
auth="myacct"

targ=/etc/boinc-client/gui_rpc_auth.cfg
#echo "$auth" >$targ
ls -l  $targ
$hx $targ
ls -l $targ >/tmp/auth 
grep 'root root' </tmp/auth 1>/dev/null 2>/dev/null
if [ $? -ne 0 ]
then
  echo "ERROR! $targ should be owner and group root"
fi
 
echo ""
targ=/var/lib/boinc/gui_rpc_auth.cfg
#echo "$auth" >$targ
sudo ls -l $targ
sudo $hx $targ
sudo ls -l $targ >/tmp/auth
sudo chown davea /tmp/auth
grep 'boinc boinc' </tmp/auth 1>/dev/null 2>/dev/null
if [ $? -ne 0 ]
then
  echo "ERROR! $targ must be owner and group boinc"
  #sudo chown boinc $targ
  #sudo chgrp boinc $targ
fi

echo ""
targ=/var/lib/boinc-client/gui_rpc_auth.cfg
#echo "$auth" >$targ
sudo ls -l $targ
sudo $hx $targ
sudo ls -l $targ >/tmp/auth
sudo chown davea /tmp/auth
grep 'boinc boinc' </tmp/auth 1>/dev/null 2>/dev/null
if [ $? -ne 0 ]
then
  echo "ERROR! $targ must be owner and group boinc"
  #sudo chown boinc $targ
  #sudo chgrp boinc $targ
fi

echo ""
targ="$HOME/gui_rpc_auth.cfg"
#echo "$auth" >$targ
echo "owner of of $targ should be $USER" 
ls -l $targ
$hx $targ
exit 
2) Message boards : Number crunching : boincmgr not finding projects redux (Message 2035092)
Posted 2 Mar 2020 by Profile David Anderson (not *that* DA) Project Donor
Post:
Back in Nov 14-16 2019 I found a way to get
linux boincmgr to find the project (as opposed to asking me to set up at least
one project).

However, there is a simple way to diagnose the problem
if you have strace.

strace boinccmd --set_run_mode never

will let you know what is going wrong.

Here is a working set as an example. The files can contain any
string of bytes as long as they match.

rw-r----- 1 davea davea 7 Feb 26 15:10 /var/lib/boinc/gui_rpc_auth.cfg
0 6d796163 63740a myacct.
lrwxrwxrwx 1 davea davea 31 Feb 28 08:51 /home/davea/gui_rpc_auth.cfg -> /var/lib/boinc/gui_rpc_auth.cfg
0 6d796163 63740a myacct.

The following may not be needed, but cannot hurt
-rw-r--r-- 1 root root 7 Feb 26 15:10 /etc/boinc-client/gui_rpc_auth.cfg
0 6d796163 63740a myacct.
-rw-r----- 1 davea davea 7 Feb 26 15:10 /var/lib/boinc-client/gui_rpc_auth.cfg
0 6d796163 63740a myacct.

Perhaps this will help someone. I hope so. I just had it happen *again*
on just one seti machine after an update.
3) Message boards : Number crunching : linux: boinc-client will not start (Message 2019187)
Posted 15 Nov 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
Thanks for thinking about this, Jord. Your comments got
me thinking again. Thanks to Keith too.

BTW: On none of my machines am I as user part of the boinc group.

Problem solved, boinc and seti@home running.

I kept focusing on /var/lib/boinc-client/gui_rpc_auth.cfg
and its content.
But crucially /etc/boinc-client/gui_rpc_auth.cfg
needs to have the same content!
The latter owned by root, the former owned by boinc.

I was lacking /etc/boinc-client/gui_rpc_auth.cfg ! No file!
While /var/lib/boinc-client/gui_rpc_auth.cfg was present with
20 or 30 character string.

With each of them containing a single newline character
then boincmgr can rpc with boinc and my project
becomes visible and the GPUs are visible.
With a failed rpc boincmgr came up ok but showed no project(s)
and no GPUs.

The updates changed one of the files (I think) so they were
inconsistent. I deleted /etc/boinc-client/gui_rpc_auth.cfg
and then things were still inconsistent as /var/lib/boinc-client/gui_rpc_auth.cfg
kept getting recreated by sudo service boinc-client but could not match
the missing /etc/boinc-client/gui_rpc_auth.cfg
.
Now /etc/boinc-client/gui_rpc_auth.cfg and /var/lib/boinc-client/gui_rpc_auth.cfg
have identical content.

Summary: It's surely my own fault as a result of something I did in the
past which maybe conflicted a bit with standard use of these files
so the install was just doing its thing normally.
4) Message boards : Number crunching : linux: boinc-client will not start (Message 2019032)
Posted 14 Nov 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
Killed and restarted boinc with --gui_rpc_port 31417 and syslog winds up after
sudo service boinc-client restart
with:
Nov 14 15:05:37 dseti3 boinc[17112]: 14-Nov-2019 15:05:37 [---] [gui_rpc] got new GUI RPC connection
14-Nov-2019 15:05:38 [---] [gui_rpc] GUI RPC Command = '<boinc_gui_rpc_request>
Nov 14 15:05:38 dseti3 boinc[17112]: <auth1/>
Nov 14 15:05:38 dseti3 boinc[17112]: </boinc_gui_rpc_request>
Nov 14 15:05:38 dseti3 boinc[17112]: '
Nov 14 15:05:38 dseti3 boinc[17112]: 14-Nov-2019 15:05:38 [---] [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply>
Nov 14 15:05:38 dseti3 boinc[17112]: <nonce>1573772738.325697</nonce>
Nov 14 15:05:38 dseti3 boinc[17112]: </boinc_gui_rpc_reply>
Nov 14 15:05:38 dseti3 boinc[17112]: '
Nov 14 15:05:38 dseti3 boinc[17112]: 14-Nov-2019 15:05:38 [---] [gui_rpc] GUI RPC Command = '<boinc_gui_rpc_request>
Nov 14 15:05:38 dseti3 boinc[17112]: <auth2>
Nov 14 15:05:38 dseti3 boinc[17112]: <nonce_hash>b3ad3233193c7e375f0b4399efe0fc5f</nonce_hash>
Nov 14 15:05:38 dseti3 boinc[17112]: </auth2>
Nov 14 15:05:38 dseti3 boinc[17112]: </boinc_gui_rpc_request>
Nov 14 15:05:38 dseti3 boinc[17112]: '
Nov 14 15:05:38 dseti3 boinc[17112]: 14-Nov-2019 15:05:38 [---] [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply>
Nov 14 15:05:38 dseti3 boinc[17112]: <unauthorized/>
Nov 14 15:05:38 dseti3 boinc[17112]: </boinc_gui_rpc_reply>
Nov 14 15:05:38 dseti3 boinc[17112]: '
Nov 14 15:05:38 dseti3 boinc[17112]: 14-Nov-2019 15:05:38 [---] [gui_rpc] handler returned -155, closing socket

No joy.
5) Message boards : Number crunching : linux: boinc-client will not start (Message 2019025)
Posted 14 Nov 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
boinc 16514 boinc 5u IPv4 137043 0t0 TCP *:31416 (LISTEN)
(previous post lost part of the line)
so it's boinc itself. ?
6) Message boards : Number crunching : linux: boinc-client will not start (Message 2019023)
Posted 14 Nov 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
netstat -atup
shows

tcp 0 0 localhost:31416 localhost:46794 TIME_WAIT -

Well. boinc is active! Killing and service boinc-client restart restarts things
but nothing changes.

lsof shows:
boinc 16514 boinc 5u IPv4 137043 0t0 TCP *:31416 (LISTEN

But boinc not working.
On a working system most of this looks the same, but boinc-client shows as active with
service --status-all
7) Message boards : Number crunching : linux: boinc-client will not start (Message 2019016)
Posted 14 Nov 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
Turned on <gui_rpc_debug>1</gui_rpc_debug>
and on restart lots of
repeats ending:
Nov 14 14:09:01 dseti3 boinc[4424]: 14-Nov-2019 14:09:01 [---] [gui_rpc] Remote control allowed
Nov 14 14:09:02 dseti3 boinc[4424]: 14-Nov-2019 14:09:02 [---] [gui_rpc] found allowed hosts list
Nov 14 14:09:02 dseti3 boinc[4424]: 14-Nov-2019 14:09:02 [---] [gui_rpc] Remote control allowed
Nov 14 14:09:03 dseti3 boinc[4424]: 14-Nov-2019 14:09:03 [---] [gui_rpc] found allowed hosts list
Nov 14 14:09:03 dseti3 boinc[4424]: 14-Nov-2019 14:09:03 [---] [gui_rpc] Remote control allowed
Nov 14 14:09:04 dseti3 boinc[4424]: 14-Nov-2019 14:09:04 [---] [gui_rpc] found allowed hosts list
Nov 14 14:09:04 dseti3 boinc[4424]: 14-Nov-2019 14:09:04 [---] [gui_rpc] Remote control allowed
Nov 14 14:09:05 dseti3 boinc[4424]: 14-Nov-2019 14:09:05 [---] [gui_rpc] found allowed hosts list
Nov 14 14:09:05 dseti3 boinc[4424]: 14-Nov-2019 14:09:05 [---] [gui_rpc] Remote control allowed
Nov 14 14:09:05 dseti3 boinc[4424]: 14-Nov-2019 14:09:05 [---] GUI RPC bind to port 31416 failed: 98
Nov 14 14:09:06 dseti3 boinc[4424]: 14-Nov-2019 14:09:06 gstate.init() failed
8) Message boards : Number crunching : linux: boinc-client will not start (Message 2019015)
Posted 14 Nov 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
sudo ufw status
Status: inactive
So it's not a firewall issue. ?
9) Message boards : Number crunching : linux: boinc-client will not start (Message 2019013)
Posted 14 Nov 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
This error happens when the user has no permission to use the RPC port number, or forgotten to allow it through the firewall.
Happens in combination with Gstate.init() failed, error code: -180

I removed the two gui_rpc_auth.cfg files which still resulted in the -180 error
on restarting boinc-client attempts
10) Message boards : Number crunching : linux: boinc-client will not start (Message 2019009)
Posted 14 Nov 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
Here is more detail. I emptied gui_rpc_auth.cfg (/var/lib/boinc-client and my $HOME)

on boinc-client restart I see more detailed info now:

Nov 14 13:47:15 dseti3 boinc[3869]: 14-Nov-2019 13:47:15 [---] gui_rpc_auth.cfg is empty - no GUI RPC password protection
Nov 14 13:47:15 dseti3 boinc[3869]: 14-Nov-2019 13:47:15 [---] GUI RPC bind to port 31416 failed: 98
Nov 14 13:47:16 dseti3 boinc[3869]: 14-Nov-2019 13:47:16 gstate.init() failed
Nov 14 13:47:16 dseti3 boinc[3869]: Error Code: -180
Nov 14 13:47:16 dseti3 systemd[1]: boinc-client.service: Main process exited, code=exited, status=76/n/a
11) Message boards : Number crunching : linux: boinc-client will not start (Message 2019005)
Posted 14 Nov 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
After the latest update:
uname -a shows:
4.15.0-70-generic #79-Ubuntu SMP

And boinc-client won't start.

syslog after "sudo service boinc-client restart"
systemd[1]: boinc-client.service: Main process exited, code=exited, status=76/n/a
systemd[1]: boinc-client.service: Failed with result 'exit-code'.
That does not look good.

Some details follow:

boincmgr will start up but of course cannot find projects without
the client running.
I switch to the noveau Linux driver, remove nvidia, and reselected nvidia 435 package
on the additional drivers panel. (most recent driver available)

(with several reboots in there)
Plus sudo apt install of
nvidia-modprobe boinc-client-nvidia-cuda nvidia-opencl-dev
The GPUs are nvidia GTX 760's (two of them).
12) Message boards : Number crunching : Lots of errors (Message 2014500)
Posted 7 Oct 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
Over 100 errors (not done in time). Sorry. Yes, no harm is really done, but
I hate errors anyway.

It's been very hot here this summer so much of the day the seti work (and in half
the machines the entire machine) is stopped. So boinc/seti estimates
of how much work could be done were...optimistic.

It's cooled off temporarily so ... more hours of seti.

I use a raspberry pi and a bit of python software and
an 8 relay board that lets me stop/idle/restart by time
and ... other things.

Happy Computing.
DavidA
13) Message boards : Number crunching : Operation failed: authentication error (linux ubuntu) fixed (Message 2010853)
Posted 6 Sep 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
Why is this so tricky? Is it just me?

Anyway, it turns out it also crucial that
/etc/boinc-client/gui_rpc_auth.cfg
be an empty file. It works ok with a newline
or without, it seems, but no auth string should be there.
Why something *created* an auth string in there is
unknown to me.

With /etc/boinc-client/gui_rpc_auth.cfg
owned by boinc

and /var/lib/boinc-client/gui_rpc_auth.cfg (the symlink to the above file)
owned by root boinccmd things work. What ownerships will fail
is unknown to me.

Oh my.
14) Message boards : Number crunching : Operation failed: authentication error (linux ubuntu) fixed (Message 2010760)
Posted 5 Sep 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
There's another crucial thing, just discovered today on
another machine when a bunch of updates done.

The only gui_rpc_auth.cfg on the machine should, apparently be

/etc/boinc-client/gui_rpc_auth.cfg

and there must also be a symlink:

/var/lib/boinc-client/gui_rpc_auth.cfg -> /etc/boinc-client/gui_rpc_auth.cfg

Having the second as a file (even identical to /etc/boinc-client/gui_rpc_auth.cfg)
did not work for me.

The kernel and other updates on the odroid xu4 did not involve any
choices asked of me...seti@home just was broken after the update till
I got the cfg files just right (which meant deleting a gui_rpc_auth.cfg
from my home directory...the update process created this one, it seems).
15) Message boards : Number crunching : Operation failed: authentication error (linux ubuntu) fixed (Message 2010758)
Posted 5 Sep 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
Ok. Now this is working again.
IT turns out (maybe 'seems' is the better word
to be critical that the following file and symlink
exist:

sudo ls -l /var/lib/boinc-client/gui_rpc_auth.cfg /etc/boinc-client/gui_rpc_auth.cfg
-rw-r----- 1 root boinc 1 Aug 14 2017 /etc/boinc-client/gui_rpc_auth.cfg
lrwxrwxrwx 1 root root 34 Jun 28 2018 /var/lib/boinc-client/gui_rpc_auth.cfg -> /etc/boinc-client/gui_rpc_auth.cfg

Having these as identical files did not work (for me)! Symlink matters.
And no other gui_rpc_auth.cfg exists on the machine.

Sorry about all the noise on this, I'll repeat this message in the original thread
(84551) so it has a more complete analysis.
16) Message boards : Number crunching : Operation failed: authentication error (linux ubuntu) fixed (Message 2010754)
Posted 5 Sep 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
In thread 84551 I described how I got setiathome reattached
on one machine.

Well, yesterday another kernel update (and lots else too)
this time on an odroid xu4, has, with any boinccmd

Operation failed: authentication error

boincmgr cannot see any project or task.

And so far none of the things that worked before to fix
this work.
I'm stumped for the moment.
17) Message boards : Number crunching : Operation failed: authentication error (linux ubuntu) fixed (Message 2010702)
Posted 5 Sep 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
Well another machine, an Odroid-xu4, just got a kernel update and
that same problem of boincmgr getting 'authentication error'
and the detach command too fails with authentication error.
Arrrggggh.
18) Message boards : Number crunching : Operation failed: authentication error (linux ubuntu) fixed (Message 2007888)
Posted 17 Aug 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
A normal update of a bunch of things (including kernel)
on ubuntu 18.04 left me with boinccmd and boincmgr
not working:
boinccmd did nothing but return
Operation failed: authentication error

I finally did

boinccmd --project 'http://setiathome.berkeley.edu/' detach
boinccmd --project_attach 'http://setiathome.berkeley.edu/' projkey
where projkey is the project key you can find for the project
on your seti@home account or in
account_setiathome.berkeley.edu.xml in the BOINC data directory.

That restored boinccmd and boincmgr to working state.

Other ubuntu 18.04 and Linux Mint machines
running seti@home here have not had
this problem. Very odd.
I just though I would mention it in case it happens to someone else.

DavidA.
19) Message boards : Number crunching : ubuntu 18.04 No irq handler for vector (Message 1997934)
Posted 12 Jun 2019 by Profile David Anderson (not *that* DA) Project Donor
Post:
After a major update last night boincmgr could not find its project list.

Lots of nvidia updates and I thought it was another nvidia botch
so removed nvidia to go to nouveau drivers then reinstalled nvidia
(some reboots along the way).
Which did not help.

syslog showed:
do_IRQ: 18.34 No irq handler for vector

I have had apcusbd running all along to track power events.
From a hint on the net about apcusbd and this sort of thing I did
sudo service apcusbd stop
and now boinc finds the project again.

So the problem vanishes with this change. SOLVED, sort of.
Posting this here in case it might help someone.
20) Message boards : Number crunching : Linux and nvidia 390.77: ubuntu update leads to errors (Message 1962503)
Posted 30 Oct 2018 by Profile David Anderson (not *that* DA) Project Donor
Post:
Thanks Keith, I have been working toward that, and it seems to have succeeded.
No more worrying messages in dmesg output.
The sequence:
In additional drivers, select nouveau driver. Apply.
sudo apt-get purge 'nvidia*'
sudo reboot
sudo apt purge 'libnvidia*'
( similar sudo purge '*nvidia*'' did not work to remove libnvidia, it seems)
sudo apt autoremove (that removed a fair amount of old stuff!)
dpkg -l |grep -i nvidia (to be sure all nvidia gone before next step)
In additional drivers, selected 390, applied
sudo apt install ocl-icd-opencl-dev
reboot

Whew. We'll see if that's sufficient. Looks promising so far,
I have new GPU tasks, one running now. I'll watch the error count.


Next 20


 
©2022 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.