Devuan bug report logs - #525
network-manager: during upgrade network-manager does not start

Full log

🔗 View this message in rfc822 format

X-Loop: owner@bugs.devuan.org
Subject: bug#525: network-manager: during upgrade network-manager does not start
Reply-To: "Dimitris T." <dimitris@stinpriza.org>, 525@bugs.devuan.org
Resent-From: "Dimitris T." <dimitris@stinpriza.org>
Resent-To: devuan-bugs@lists.dyne.org
Resent-CC: Mark Hindley <mark@hindley.org.uk>
X-Loop: owner@bugs.devuan.org
Resent-Date: Fri, 27 Nov 2020 12:03:02 +0000
Resent-Message-ID: <handler.525.B.160647840214462@bugs.devuan.org>
Resent-Sender: owner@bugs.devuan.org
X-Devuan-PR-Message: report 525
X-Devuan-PR-Package: network-manager
X-Devuan-PR-Keywords: 
Received: via spool by submit@bugs.devuan.org id=B.160647840214462
          (code B); Fri, 27 Nov 2020 12:03:02 +0000
Received: (at submit) by bugs.devuan.org; 27 Nov 2020 12:00:02 +0000
Delivered-To: devuanbugs@dyne.org
Received: from tupac3.dyne.org [195.169.149.119]
	by doc.devuan.org with IMAP (fetchmail-6.4.0.beta4)
	for <debbugs@localhost> (single-drop); Fri, 27 Nov 2020 12:00:02 +0000 (UTC)
Received: from cacofonix.stinpriza.org (cacofonix.stinpriza.org [148.251.45.81])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by vm6.ganeti.dyne.org (Postfix) with ESMTPS id AD9FFF60BD9
	for <submit@bugs.devuan.org>; Fri, 27 Nov 2020 12:51:56 +0100 (CET)
Authentication-Results: vm6.ganeti.dyne.org;
	dkim=pass (2048-bit key; unprotected) header.d=stinpriza.org header.i=@stinpriza.org header.b="MXXau8r4";
	dkim-atps=neutral
Received: from localhost (unknown [45.153.183.197])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by cacofonix.stinpriza.org (Postfix) with ESMTPSA id CEFBE2A004F1;
	Fri, 27 Nov 2020 13:51:53 +0200 (EET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=stinpriza.org; s=mail;
	t=1606477914; bh=a/xetDrj/xKkkDxE/RS3+hxNFTzYXVnet7fKlap6Nlo=;
	h=From:To:Subject:Date:From;
	b=MXXau8r4W2Do6KiYLmzFYv0NJ6/nRkB8pr6vEklNI+DRzOSKzvepB3wmS8gE7/nuR
	 rRyYSI1ZEGykHmmyqhpUbETM8BwcqfBfaJOrfC8P3MCwqt0NBg25fad9DDA9vWRKjw
	 GWMhgqKn1rFows7xpx9uJzvS2rWet+YTmMt3afLX+ePZLoYn+LxHUe0H0DQ1sc/g6/
	 MELEYDBMEEDL2wVS1hRCKrVYFj634ficiKpE9N9OJdI8YxiM5hGd47CWbD/PlecAV4
	 FgizV2HsGbAa+pCw8A5o3CQxyzwifq+50YYBbO6T/g6hEin9oiCckqAinHmJ/vzkOT
	 BqHmV/Kq2TDAA==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
From: "Dimitris T." <dimitris@stinpriza.org>
To: Devuan Bug Tracking System <submit@bugs.devuan.org>
Message-ID: <160647791245.8816.7996622677789872322.reportbug@louise.lan>
X-Mailer: reportbug 7.8.0+devuan1
Date: Fri, 27 Nov 2020 13:51:52 +0200
X-Virus-Scanned: clamav-milter 0.102.4 at cacofonix.stinpriza.org
X-Virus-Status: Clean
X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.5.11 (cacofonix.stinpriza.org [0.0.0.0]); Fri, 27 Nov 2020 13:51:54 +0200 (EET)
X-Greylist: Default is to whitelist mail, not delayed by milter-greylist-4.5.11 (cacofonix.stinpriza.org [0.0.0.0]); Fri, 27 Nov 2020 13:51:54 +0200 (EET)
X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW,SPF_PASS
	autolearn=disabled version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org

Package: network-manager
Version: 1.27.91-2+devuan1
Severity: normal

Hey,

(noticed it in previous upgrades too -neglected to report-, but latest upgrade yesterday reminded me to...)

after upgrading network-manager, daemon is not started, even though status reports it as "running". :


# apt install --reinstall network-manager
....
....
Get:1 https://$somemirror/merged ceres/main amd64 network-manager amd64 1.27.91-2+devuan1 [3449 kB]
...
Preparing to unpack .../network-manager_1.27.91-2+devuan1_amd64.deb ...
Unpacking network-manager (1.27.91-2+devuan1) over (1.27.91-2+devuan1) ...
Γίνεται εγκατάσταση network-manager (1.27.91-2+devuan1) ...
insserv: warning: script 'cgroups' missing LSB tags
insserv: Default-Start undefined, assuming empty start runlevel(s) for script `cgroups'
insserv: Default-Stop  undefined, assuming empty stop runlevel(s) for script `cgroups'
Stopping network connection manager: NetworkManager.
Starting network connection manager: NetworkManager.
Processing triggers for dbus (1.12.20-1+devuan1) ...
Processing triggers for man-db (2.9.3-2) ...

# service network-manager status 
NetworkManager is running.

# ps -aux | grep Network
(nothing)

# ls -la /var/run/NetworkManager 
drwxr-xr-x  2 root root  80 Νοε  27 13:27 devices
-rw-r--r--  1 root root  30 Νοε  27 13:27 no-stub-resolv.conf
-rw-r--r--  1 root root  30 Νοε  27 13:27 resolv.conf


as you can see, no NetworkManager.pid created in /run/NetworkManager, and daemon is not running. 

restarting/stopping+starting service manually eg. `service network-manager restart`, works as expected. 

# service network-manager restart
Stopping network connection manager: NetworkManager already stopped.
Starting network connection manager: NetworkManager.

#ls -la /var/run/NetworkManager          
drwxr-xr-x  2 root root  80 Νοε  27 13:29 devices
-rw-r--r--  1 root root   4 Νοε  27 13:29 NetworkManager.pid
-rw-r--r--  1 root root 104 Νοε  27 13:29 no-stub-resolv.conf
-rw-r--r--  1 root root 104 Νοε  27 13:29 resolv.conf


was using openrc before, and think it also applied there as well.



thanks in advance,
d.


p.s a silly question perhaps, but does the daemon really needs to restart on each upgrade? (security related excluded..)
"forcing" a network restart on running/connected system might not be the best option...(?)



-- System Information:
Distributor ID:	Devuan
Description:	Devuan GNU/Linux 4 (chimaera/ceres)
Release:	testing/unstable
Codename:	n/a
Architecture: x86_64

Kernel: Linux 5.9.0-3-amd64 (SMP w/4 CPU threads)
Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

Versions of packages network-manager depends on:
ii  adduser                  3.118
ii  dbus                     1.12.20-1+devuan1
ii  eudev [udev]             3.2.9-8
ii  init-system-helpers      1.58+devuan1
ii  libaudit1                1:2.8.5-3.1
ii  libbluetooth3            5.55-1
ii  libc6                    2.31-4
ii  libcurl3-gnutls          7.72.0-1
ii  libelogind0              243.8-1
ii  libeudev1                3.2.9-8
ii  libglib2.0-0             2.66.3-1
ii  libgnutls30              3.6.15-4
ii  libjansson4              2.13.1-1
ii  libmm-glib0              1.14.8-0.1
ii  libndp0                  1.6-1+b1
ii  libnewt0.52              0.52.21-4+b2
ii  libnm0                   1.27.91-2+devuan1
ii  libpam-elogind [logind]  243.8-1
ii  libpsl5                  0.21.0-1.1
ii  libreadline8             8.1~rc3-1
ii  libselinux1              3.1-2+b1
ii  libteamdctl0             1.31-1
ii  libuuid1                 2.36.1-2+devuan1
ii  policykit-1              0.105-29+devuan1
ii  udev                     1:3.2.9+devuan4
ii  wpasupplicant            2:2.9.0-15

Versions of packages network-manager recommends:
ii  crda                         4.14+git20191112.9856751-1
ii  dnsmasq-base [dnsmasq-base]  2.82-1
ii  iptables                     1.8.6-1
ii  modemmanager                 1.14.8-0.1
ii  ppp                          2.4.7-2+4.1+deb10u1+b1

Versions of packages network-manager suggests:
ii  isc-dhcp-client  4.4.1-2.1+b2
pn  libteam-utils    <none>

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
dns=none
ip6-privacy=2
[ifupdown]
managed=false


-- no debconf information

Send a report that this bug log contains spam.