Subject: bug#525: network-manager: during upgrade network-manager does not start

From: Dimitris <[email-masked]>
Date: Fri, 27 Nov 2020 21:13:43 +0200

ok, so i think i've narrowed it to the following command failing :
# invoke-rc.d network-manager restart
which is probably the one running in every install/upgrade.. look dbus 
related, not sure about their internals though..

getting this in daemon.log :

Nov 27 21:01:59 host NetworkManager[18788]: <info>  [1606503719.6799] 
NetworkManager (version 1.27.91) is starting... (after a restart)
Nov 27 21:01:59 host NetworkManager[18788]: <info>  [1606503719.6801] 
Read config: /etc/NetworkManager/NetworkManager.conf (lib: 
no-mac-addr-change.conf)
Nov 27 21:02:24 host NetworkManager[18788]: <error> [1606503744.7064] 
bus-manager: cannot connect to D-Bus: Timeout was reached
Nov 27 21:02:24 host NetworkManager[18788]: <info>  [1606503744.7066] 
exiting (error)

while, when manually running `service network-manager restart`, it works 
fine :

Nov 27 21:02:58 host NetworkManager[18827]: <info>  [1606503778.0879] 
NetworkManager (version 1.27.91) is starting... (after a restart)
Nov 27 21:02:58 host NetworkManager[18827]: <info>  [1606503778.0881] 
Read config: /etc/NetworkManager/NetworkManager.conf (lib: 
no-mac-addr-change.conf)
Nov 27 21:02:58 host NetworkManager[18827]: <info>  [1606503778.0919] 
bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"

using runit as init, maybe with sysv this would work(?).

d.

Στις 27/11/20 7:18 μ.μ., ο/η Mark Hindley έγραψε:
> Control: tags -1 moreinfo unreproducible
> 
> Dimitris,
> 
> On Fri, Nov 27, 2020 at 01:51:52PM +0200, Dimitris T. wrote:
>> 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". :
> 
> Thanks for this. However, I can't reproduce the behaviour you observe.
> 
> Here is my attempt in a VM which seems correct:
> 
> $ sudo service network-manager status
> NetworkManager is running.
> $ pidof NetworkManager
> 4025
> $ sudo apt install --reinstall network-manager
> Reading package lists... Done
> Building dependency tree... 50%
> Reading state information... Done
> 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
> Need to get 3,449 kB of archives.
> After this operation, 0 B of additional disk space will be used.
> Get:1ohttp://pkgmaster.devuan.org/merged unstable/main amd64 network-manager amd64 1.27.91-2+devuan1 [3,449 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) ...
> Setting up network-manager (1.27.91-2+devuan1) ...
> 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) ...
> 
> $ sudo service network-manager status
> NetworkManager is running
> $ pidof NetworkManager
> 4327
> 
> So what is different about your system? Is there anything in syslog whilst the
> reinstall happens that might give a clue?
> 
> Thanks
> 
> Mark
>