On Samstag, 13. Juli 2024 16:11:41 MESZ mh@mike.franken.de wrote:
Hi *,
starting with the last two NetworkManager versions, my dispatcher script does not finish when going to sleep. It finishes on resume, though, causing some strange effects. It's runtime is 1 or 2 seconds only, so this is not a problem of hitting the dispatcher timeout. Anyway in this case it wouldn't continue after resume, I believe.
Any idea, what is happening here, and how to avoid it?
It seems, that NM takes down the dhcp lease, even before the dispatcher service starts. So there is no chance to umount nfs shares due to a lack of connectivity. Jun 30 01:21:12 transformer systemd-logind[2036]: Lid closed. Jun 30 01:21:12 transformer systemd-logind[2036]: The system will suspend now! Jun 30 01:21:12 transformer NetworkManager[2543]: <info> [1719703272.8559] manager: sleep: sleep requested (sleeping: n o enabled: yes) Jun 30 01:21:12 transformer ModemManager[2236]: <info> [sleep-monitor-systemd] system is about to suspend Jun 30 01:21:12 transformer NetworkManager[2543]: <info> [1719703272.8561] device (wlp0s20f3): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed') Jun 30 01:21:12 transformer NetworkManager[2543]: <info> [1719703272.8566] device (wlp0s20f3): set-hw-addr: reset MAC address to 20:1E:88:D2:9F:5B (unmanage) Jun 30 01:21:12 transformer NetworkManager[2543]: <info> [1719703272.9772] manager: NetworkManager state is now ASLEEP Jun 30 01:21:12 transformer NetworkManager[2543]: <info> [1719703272.9774] device (enp62s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed') Jun 30 01:21:12 transformer NetworkManager[2543]: <info> [1719703272.9775] dhcp4 (enp62s0): canceled DHCP transaction Jun 30 01:21:12 transformer NetworkManager[2543]: <info> [1719703272.9775] dhcp4 (enp62s0): activation: beginning transaction (timeout in 45 seconds) Jun 30 01:21:12 transformer NetworkManager[2543]: <info> [1719703272.9775] dhcp4 (enp62s0): state changed no lease Jun 30 01:21:12 transformer dbus-daemon[1994]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' (uid=0 pid=2543 comm="/usr/sbin/NetworkManager --no-daemon") Jun 30 01:21:12 transformer netconfig[12337]: Executing 'modify --service NetworkManager' for pid 2543 Jun 30 01:21:12 transformer NetworkManager[12337]: <13>Jun 30 01:21:12 netconfig: Executing 'modify --service NetworkManager' for pid 2543 Jun 30 01:21:12 transformer NetworkManager[12335]: debug: lockfile created (/run/netconfig.pid) for PID 12335 Jun 30 01:21:12 transformer NetworkManager[12335]: debug: lockfile created Jun 30 01:21:13 transformer NetworkManager[12335]: debug: write new STATE file /run/netconfig//NetworkManager.netconfig Jun 30 01:21:13 transformer NetworkManager[12335]: debug: Module order: dns-resolver dns-bind dns-dnsmasq nis ntp-runtime Jun 30 01:21:13 transformer systemd[1]: Starting Network Manager Script Dispatcher Service... Or do I misunderstand the journal entries?
TIA.
Bye. Michael.