Devuan bug report logs -
#525
network-manager: during upgrade network-manager does not start
Reported by: "Dimitris T." <dimitris@stinpriza.org>
Date: Fri, 27 Nov 2020 12:03:02 UTC
Severity: normal
Tags: moreinfo, unreproducible
Found in version 1.27.91-2+devuan1
Done: Mark Hindley <mark@hindley.org.uk>
Full log
🔗
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Tue, 24 Jan 2023 17:01:33 +0000
with message-id <Y9AO7aoL0wUWiUU6@hindley.org.uk>
and subject line Re: bug#525: network-manager: during upgrade network-manager does not start
has caused the Devuan bug report #525,
regarding network-manager: during upgrade network-manager does not start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.devuan.org
immediately.)
--
525: https://bugs.devuan.org/cgi/bugreport.cgi?bug=525
Devuan Bug Tracking System
Contact owner@bugs.devuan.org with problems
[Message part 2 (message/rfc822, inline)]
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
[Message part 3 (message/rfc822, inline)]
On Wed, Mar 03, 2021 at 10:27:53PM +0200, Dimitris wrote:
> tried `apt install --reinstall network-manager` and it restarts ok.
> also downgraded to 1.28.0-2+devuan1, and re-upgraded with exactly the same
> commands, this time it restarts ok.
>
> can't think of anything else to assist with this bug report, so please close
> it..
Closing, as requested.
Mark
Send a report that this bug log contains spam.