boinc-client and X and monitor

Message boards : Number crunching : boinc-client and X and monitor
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile David Anderson (not *that* DA) Project Donor
Avatar

Send message
Joined: 5 Dec 09
Posts: 194
Credit: 55,635,261
RAC: 38,986
United States
Message 1920929 - Posted: 24 Feb 2018, 23:24:01 UTC

Running boinc on a small computer. If I leave the monitor detached boinc-client starts to complain that "No protocol specified" in /var/log/boincerr.log .

This is with
boinc-client 7.6.31+dfsg- armhf
Ubuntu 16.04 LTS

Seems quite odd to me. I don't have much need for a monitor
on that machine (I ssh in and run boincmgr remotely), so ... why?
Quite odd.
ID: 1920929 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 5304
Credit: 353,630,481
RAC: 1,093,202
United States
Message 1920964 - Posted: 25 Feb 2018, 1:35:45 UTC - in response to Message 1920929.  

I don't run that way but it sounds like you need to run the client "headless"

I think the error message is a residual from the the client looking for a display manager.

You could start the client with the -daemon parameter which detaches from the controlling terminal.

Maybe you already do that when you remote in.
Seti@Home classic workunits:20,676 CPU time:74,226 hours
ID: 1920964 · Report as offensive
Profile David Anderson (not *that* DA) Project Donor
Avatar

Send message
Joined: 5 Dec 09
Posts: 194
Credit: 55,635,261
RAC: 38,986
United States
Message 1921083 - Posted: 25 Feb 2018, 20:00:05 UTC

boinc-client is started by systemd, so it's running
as a daemon already, I would think.

/etc/systemd/system/multi-user.target.wants
links boink service to
/lib/systemd/system/boinc-client.service

which comtains:
[Unit]
Description=Berkeley Open Infrastructure Network Computing Client
After=network.target

[Service]
Nice=10
User=boinc
PermissionsStartOnly=yes
ExecStartPre=/usr/bin/touch /var/log/boinc.log /var/log/boincerr.log
ExecStartPre=/bin/chown boinc:boinc /var/log/boinc.log /var/log/boincerr.log
#ExecStart=/usr/bin/boinc --dir /var/lib/boinc-client
ExecStart=/bin/sh -c '/usr/bin/boinc --dir /var/lib/boinc-client >/var/log/boinc.log 2>/var/log/boincerr.log'
ExecReload=/usr/bin/boinccmd --read_cc_config
ExecStopPost=/bin/rm -f /var/lib/boinc-client/lockfile
IOSchedulingClass=idle

[Install]
WantedBy=multi-user.target

Which does not use -daemon . Hmm. I don't know much about systemd
though.
ID: 1921083 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 5304
Credit: 353,630,481
RAC: 1,093,202
United States
Message 1921091 - Posted: 25 Feb 2018, 20:23:15 UTC - in response to Message 1921083.  

I'm just learning about systemd myself. It supplants the old systemctl and the old controls for systemctl don't apply 1:1. Seems you are starting the client as a daemon, by the system instead of by the boinc cmd line. Don't know if that has anything to with the problem. Could be ownership issues.
Seti@Home classic workunits:20,676 CPU time:74,226 hours
ID: 1921091 · Report as offensive
Profile David Anderson (not *that* DA) Project Donor
Avatar

Send message
Joined: 5 Dec 09
Posts: 194
Credit: 55,635,261
RAC: 38,986
United States
Message 1921106 - Posted: 25 Feb 2018, 21:05:08 UTC

My concern is that a side effect of the 'error' is to pile up
some set of resources leading to eventual kernel
hangup. Not that I have any evidence of that
other than the system just seeming to stop.

So far, with monitor in use, I see no boincerr.log
records being added and no hangs.
But odroid-xu4 needs to keep going for much longer
to mean much.
ID: 1921106 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 5304
Credit: 353,630,481
RAC: 1,093,202
United States
Message 1921109 - Posted: 25 Feb 2018, 21:09:06 UTC - in response to Message 1921106.  

Maybe you can glean some information about using BOINC in headless state from the recent forum threads discussing how to get multiple BOINC instances started on Android devices that Raistmer, Richard and Petri have posted.
Seti@Home classic workunits:20,676 CPU time:74,226 hours
ID: 1921109 · Report as offensive
Profile David Anderson (not *that* DA) Project Donor
Avatar

Send message
Joined: 5 Dec 09
Posts: 194
Credit: 55,635,261
RAC: 38,986
United States
Message 1921752 - Posted: 28 Feb 2018, 22:06:00 UTC - in response to Message 1921109.  

Thanks Keith. I will look for such threads.
I was out of town a couple days (now back) and
notice that plugging in a monitor (
while system down, then rebooting)
does not remove the messages from boinc.
Even logged in via ssh.
But logging in at the local keyboard/monitor stops
the
No protocol specified
boinc-client messages.

Have yet to have the system in question
run two days
without stopping...sigh.
ID: 1921752 · Report as offensive
Profile David Anderson (not *that* DA) Project Donor
Avatar

Send message
Joined: 5 Dec 09
Posts: 194
Credit: 55,635,261
RAC: 38,986
United States
Message 1922239 - Posted: 3 Mar 2018, 0:17:11 UTC - in response to Message 1921752.  

Focusing on confusing issues with odroid-xu4 itself right now.
It's run 24 hours with 4 seti tasks at once, no errors.

For now just letting it run with os configure changes
on that machine. In a couple days will review
again unless something changes sooner.
ID: 1922239 · Report as offensive
Profile David Anderson (not *that* DA) Project Donor
Avatar

Send message
Joined: 5 Dec 09
Posts: 194
Credit: 55,635,261
RAC: 38,986
United States
Message 1923138 - Posted: 7 Mar 2018, 16:22:23 UTC

Was unable to find anything (meaningful to me)
about running boinc-client with no monitor.
What little I found was old(er) boinc-client and
the logging has, according to some messages
I found, changed over time.

Reducing the clock rate slightly on the
single board computer has let it run
boinc for two days (with monitor attached).
It seems possible the boinc-client log
messages (when headless) were not a problem at all,
just an annoyance.

If anyone has knowledge of current boinc-client run headless
and controlling boinc-client logging in that environment
I'd appreciate hearing about such.
But otherwise I'll just take this as a learning experience :-)
ID: 1923138 · Report as offensive
Kissagogo27 Special Project $75 donor

Send message
Joined: 6 Nov 99
Posts: 222
Credit: 5,306,569
RAC: 4,072
France
Message 1923160 - Posted: 7 Mar 2018, 19:03:23 UTC
Last modified: 7 Mar 2018, 19:03:37 UTC

ID: 1923160 · Report as offensive
Profile David Anderson (not *that* DA) Project Donor
Avatar

Send message
Joined: 5 Dec 09
Posts: 194
Credit: 55,635,261
RAC: 38,986
United States
Message 1927535 - Posted: 31 Mar 2018, 18:21:35 UTC - in response to Message 1923160.  

I tried that and it did not make a difference.
It does not surprise that Linux and X don't use the
same monitor-sense approach as past Windows.

For now on the system I'm just letting boinc-client log
in boincerr.log every second :-(

Thanks for the tip, though. Worth a try.
DavidA.
ID: 1927535 · Report as offensive

Message boards : Number crunching : boinc-client and X and monitor


 
©2018 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.