[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: getting network-manager to restart



On Sun, 2 Nov 2025 18:19:29 -0600
Mike McClain <mike.junk.46@att.net> wrote:

> In Trixie I'm trying to get ipupdown working without network-manager,
> since I'm in a two station network I don't need all the extra baggage
> that the professionals have gotten Debian to adopt.
> I got it working in bookworm but in trying to get it working in Trixie
> I ran 'systemctl stop NetworkManager' and now can't get it started
> again hence have no i'net there so I'm posting from bookworm.
> Neither 'systemctl start NetworkManager', 'systemctl restart
> NetworkManager', or even reinstalling it using 'dpkg -i' to reinstall
> from a package I DL'e from bookworm.

I'm not following you. If you want to forgo Network Manager (NM) in
favor of ifupdown, why are you fiddling with starting and stopping NM?

What I would do:

* Check /etc/network/interfaces(.d)? to be sure that proper descriptions
  of your interfaces are present, correct, and not commented out. "man 5
  interfaces" for details.

* Systemctl stop, disable, and mask NetworkManager.

* If you have removed ifupdown, re-install it.

* You make have work to do to be sure ifupdown is working. Make sure it
  works with all your interfaces.

* Apt purge network-manager.

If I am reading that incorrectly, here is what I have for NM systemd
units, and their states:

oot@peregrine:/etc/libvirt# systemctl status NetworkManager*
● NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled; preset: enabled)
     Active: active (running) since Sun 2025-11-02 20:56:39 MST; 8s ago
 Invocation: 8eaf580a967e4a56b2ef45abb89e4818
       Docs: man:NetworkManager-dispatcher.service(8)
   Main PID: 220523 (nm-dispatcher)
      Tasks: 5 (limit: 76663)
     Memory: 1.3M (peak: 4.8M)
        CPU: 116ms
     CGroup: /system.slice/NetworkManager-dispatcher.service
             └─220523 /usr/libexec/nm-dispatcher

Nov 02 20:56:38 peregrine systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
Nov 02 20:56:39 peregrine systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.

● NetworkManager-wait-online.service - Network Manager Wait Online
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-online.service; enabled; preset: enabled)
     Active: active (exited) since Fri 2025-10-24 22:22:38 MDT; 1 week 1 day ago
 Invocation: dd272c99d1654fbe99f90b073e98fb8d
       Docs: man:NetworkManager-wait-online.service(8)
   Main PID: 1306 (code=exited, status=0/SUCCESS)
   Mem peak: 2.5M
        CPU: 31ms

Oct 24 22:22:32 peregrine systemd[1]: Starting NetworkManager-wait-online.service - Network Manager Wait Online...
Oct 24 22:22:38 peregrine systemd[1]: Finished NetworkManager-wait-online.service - Network Manager Wait Online.

● NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: enabled)
     Active: active (running) since Fri 2025-10-24 22:22:32 MDT; 1 week 1 day ago
 Invocation: 23f1e01027124d7b82f0662fec82b700
       Docs: man:NetworkManager(8)
   Main PID: 1263 (NetworkManager)
      Tasks: 4 (limit: 76663)
     Memory: 10.5M (peak: 11.8M)
        CPU: 2min 51.062s
     CGroup: /system.slice/NetworkManager.service
             └─1263 /usr/sbin/NetworkManager --no-daemon

Nov 02 18:41:38 peregrine NetworkManager[1263]: <info>  [1762134098.9143] dhcp4 (wlp1s0): state changed new lease, address=192.168.100.47
Nov 02 18:56:38 peregrine NetworkManager[1263]: <info>  [1762134998.9150] dhcp4 (wlp1s0): state changed new lease, address=192.168.100.47
Nov 02 19:11:38 peregrine NetworkManager[1263]: <info>  [1762135898.9180] dhcp4 (wlp1s0): state changed new lease, address=192.168.100.47
Nov 02 19:26:38 peregrine NetworkManager[1263]: <info>  [1762136798.9175] dhcp4 (wlp1s0): state changed new lease, address=192.168.100.47
Nov 02 19:41:38 peregrine NetworkManager[1263]: <info>  [1762137698.9106] dhcp4 (wlp1s0): state changed new lease, address=192.168.100.47
Nov 02 19:56:38 peregrine NetworkManager[1263]: <info>  [1762138598.9110] dhcp4 (wlp1s0): state changed new lease, address=192.168.100.47
Nov 02 20:11:38 peregrine NetworkManager[1263]: <info>  [1762139498.9139] dhcp4 (wlp1s0): state changed new lease, address=192.168.100.47
Nov 02 20:26:38 peregrine NetworkManager[1263]: <info>  [1762140398.9168] dhcp4 (wlp1s0): state changed new lease, address=192.168.100.47
Nov 02 20:41:38 peregrine NetworkManager[1263]: <info>  [1762141298.9125] dhcp4 (wlp1s0): state changed new lease, address=192.168.100.47
Nov 02 20:56:38 peregrine NetworkManager[1263]: <info>  [1762142198.9210] dhcp4 (wlp1s0): state changed new lease, address=192.168.100.47
[2]+  Done                    firewall-config
root@peregrine:/etc/libvirt# systemctl status nm-priv-helper.service
○ nm-priv-helper.service - NetworkManager Privileged Helper
     Loaded: loaded (/usr/lib/systemd/system/nm-priv-helper.service; static)
     Active: inactive (dead)
root@peregrine:/etc/libvirt#

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/


Reply to: