Constantly logging "No protocol specified"

Bug #1876313 reported by Jani Uusitalo
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
BOINC
New
Unknown
boinc (Debian)
Confirmed
Unknown
boinc (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Boinc-client logs "No protocol specified" incessantly, twice every second on my setup.

    -- Logs begin at Wed 2020-03-25 14:45:19 EET, end at Fri 2020-05-01 17:14:34 EEST. --
    touko 01 00:00:00 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:00 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:01 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:01 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:02 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:02 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:03 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:03 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:04 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:04 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:05 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:05 saegusa boinc[2083]: No protocol specified
    touko 01 00:00:06 saegusa boinc[2083]: No protocol specified

...and on and on...

    touko 01 17:14:54 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:55 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:55 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:56 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:56 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:57 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:57 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:58 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:58 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:59 saegusa boinc[2083]: No protocol specified
    touko 01 17:14:59 saegusa boinc[2083]: No protocol specified
    touko 01 17:15:00 saegusa boinc[2083]: No protocol specified
    touko 01 17:15:00 saegusa boinc[2083]: No protocol specified
    touko 01 17:15:01 saegusa boinc[2083]: No protocol specified
    touko 01 17:15:01 saegusa boinc[2083]: No protocol specified
    touko 01 17:15:02 saegusa boinc[2083]: No protocol specified
    touko 01 17:15:02 saegusa boinc[2083]: No protocol specified

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: boinc-client 7.16.6+dfsg-1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri May 1 17:16:46 2020
InstallationDate: Installed on 2016-10-13 (1296 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SourcePackage: boinc
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.boinc-client.gui_rpc_auth.cfg: [inaccessible: [Errno 13] Lupa evätty: '/etc/boinc-client/gui_rpc_auth.cfg']
mtime.conffile..etc.boinc-client.cc_config.xml: 2020-04-03T18:39:31.411167
mtime.conffile..etc.boinc-client.global_prefs_override.xml: 2020-04-03T15:47:12.178284

Revision history for this message
Jani Uusitalo (uusijani) wrote :
Changed in boinc:
status: Unknown → New
Changed in boinc (Debian):
status: Unknown → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in boinc (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.