Your message dated Tue, 10 Aug 2021 01:44:43 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#992048:
NetworkManager-wait-online.service: fails to start correctly
has caused the Debian Bug report #992048,
regarding NetworkManager-wait-online.service: fails to start correctly
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 [email protected]
immediately.)
--
992048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992048
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 1.30.0-2
Severity: important
File: NetworkManager-wait-online.service
$ systemctl status NetworkManager-wait-online.service
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/lib/systemd/system/NetworkManager-wait-online.service;
enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-08-10 07:49:41 AEST;
5min ago
Docs: man:nm-online(1)
Main PID: 1333 (code=exited, status=1/FAILURE)
CPU: 64ms
Aug 10 07:47:01 canidae systemd[1]: Starting Network Manager Wait Online...
Aug 10 07:49:41 canidae systemd[1]: NetworkManager-wait-online.service: Main
process exited, code=exited, status=1/FAILURE
Aug 10 07:49:41 canidae systemd[1]: NetworkManager-wait-online.service: Failed
with result 'exit-code'.
Aug 10 07:49:41 canidae systemd[1]: Failed to start Network Manager Wait Online.
$ systemctl restart NetworkManager-wait-online.service
[wait awhile ]
Job for NetworkManager-wait-online.service failed because the control process
exited with error code.
See "systemctl status NetworkManager-wait-online.service" and "journalctl -xe"
for details.
$ systemctl status NetworkManager-wait-online.service
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/lib/systemd/system/NetworkManager-wait-online.service;
enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2021-08-10 07:59:21 AEST; 45s
ago
Docs: man:nm-online(1)
Process: 7992 ExecStart=/usr/bin/nm-online -s -q (code=exited,
status=1/FAILURE)
Main PID: 7992 (code=exited, status=1/FAILURE)
CPU: 15ms
Aug 10 07:58:21 canidae systemd[1]: Starting Network Manager Wait Online...
Aug 10 07:59:21 canidae systemd[1]: NetworkManager-wait-online.service: Main
process exited, code=exited, status=1/FAILURE
Aug 10 07:59:21 canidae systemd[1]: NetworkManager-wait-online.service: Failed
with result 'exit-code'.
Aug 10 07:59:21 canidae systemd[1]: Failed to start Network Manager Wait Online.
$ journalctl -xe
[ no additional information ]
But networking - as soley setup by networkmanager - is working perfectly.
So why is NetworkManager-wait-online.service failing?
Possibly something here might help:
$ systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: enabled)
Active: active (running) since Tue 2021-08-10 07:47:01 AEST; 17min ago
Docs: man:NetworkManager(8)
Main PID: 1255 (NetworkManager)
Tasks: 3 (limit: 76880)
Memory: 11.1M
CPU: 907ms
CGroup: /system.slice/NetworkManager.service
└─1255 /usr/sbin/NetworkManager --no-daemon
Aug 10 07:50:21 canidae NetworkManager[1255]: <info> [1628545821.6920] device
(wlo1): state change: activated -> deactivating (reason 'user>
Aug 10 07:50:21 canidae NetworkManager[1255]: <info> [1628545821.6952] audit:
op="device-disconnect" interface="wlo1" ifindex=3 pid=3195 ui>
Aug 10 07:50:21 canidae NetworkManager[1255]: <info> [1628545821.7749] device
(wlo1): supplicant interface state: completed -> disconnected
Aug 10 07:50:21 canidae NetworkManager[1255]: <info> [1628545821.7749] device
(p2p-dev-wlo1): supplicant management interface state: comple>
Aug 10 07:50:21 canidae NetworkManager[1255]: <info> [1628545821.7752] device
(wlo1): state change: deactivating -> disconnected (reason 'u>
Aug 10 07:50:21 canidae NetworkManager[1255]: <info> [1628545821.8051] dhcp4
(wlo1): canceled DHCP transaction
Aug 10 07:50:21 canidae NetworkManager[1255]: <info> [1628545821.8052] dhcp4
(wlo1): state changed bound -> done
Aug 10 07:50:21 canidae NetworkManager[1255]: <info> [1628545821.8077] device
(wlo1): set-hw-addr: set MAC address to 9E:31:07:27:BC:D6 (sc>
Aug 10 07:57:14 canidae NetworkManager[1255]: <info> [1628546234.7268] device
(wlo1): set-hw-addr: set MAC address to FE:E3:80:DD:B8:84 (sc>
Aug 10 08:04:07 canidae NetworkManager[1255]: <info> [1628546647.7041] device
(wlo1): set-hw-addr: set MAC address to B2:36:55:FB:94:15 (sc>
$ ps auwx | grep -i NetworkManager
root 1255 0.0 0.0 255040 17732 ? Ssl 07:48 0:00
/usr/sbin/NetworkManager --no-daemon
$ /usr/bin/nm-online -s
Connecting............... 0s [startup-pending]
$ echo $?
1
canidae#
For some reaason nm-online - which is used by
NetworkManager-wait-online.service - doesn't seem to be able to connect,
but I have no idea why.
strace isn't much help - it doesn't appear to be doing anything but
writing messages on the screen:
[...]
eventfd2(0, EFD_CLOEXEC|EFD_NONBLOCK) = 3
[...]
Connecting) = 11e(1, "\rConnecting", 11
[pid 11384] write(1, ". 29s", 21. 29s) = 21
[pid 11384] poll([{fd=3, events=POLLIN}], 1, 998) = 0 (Timeout)
Connecting) = 11e(1, "\rConnecting", 11
[pid 11384] write(1, ".. 28s", 21.. 28s) = 21
[pid 11384] poll([{fd=3, events=POLLIN}], 1, 998) = 0 (Timeout)
Connecting) = 11e(1, "\rConnecting", 11
[...]
-- System Information:
Debian Release: 11.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-8-amd64 (SMP w/20 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages network-manager depends on:
ii adduser 3.118
ii dbus 1.12.20-2
ii libaudit1 1:3.0-2
ii libbluetooth3 5.55-3.1
ii libc6 2.31-13
ii libcurl3-gnutls 7.74.0-1.3+b1
ii libglib2.0-0 2.66.8-1
ii libgnutls30 3.7.1-5
ii libjansson4 2.13.1-1.1
ii libmm-glib0 1.14.12-0.2
ii libndp0 1.6-1+b1
ii libnewt0.52 0.52.21-4+b3
ii libnm0 1.30.0-2
ii libpsl5 0.21.0-1.2
ii libreadline8 8.1-1
ii libselinux1 3.1-3
ii libsystemd0 247.3-6
ii libteamdctl0 1.31-1
ii libudev1 247.3-6
ii libuuid1 2.36.1-8
ii policykit-1 0.105-31
ii udev 247.3-6
ii wpasupplicant 2:2.9.0-21
Versions of packages network-manager recommends:
ii dnsmasq-base [dnsmasq-base] 2.85-1
ii iptables 1.8.7-1
ii libpam-systemd 247.3-6
ii modemmanager 1.14.12-0.2
ii ppp 2.4.9-1+1
ii wireless-regdb 2020.04.29-2
Versions of packages network-manager suggests:
ii isc-dhcp-client 4.4.1-2.3
pn libteam-utils <none>
-- debconf-show failed
--- End Message ---
--- Begin Message ---
Thanks for following up. Closing accordingly.
Am 10.08.21 um 01:18 schrieb Brian May:
OK, I think I worked it out.
I followed instructions from
https://www.cyberciti.biz/faq/how-to-add-network-bridge-with-nmcli-networkmanager-on-linux/
On how to create a bridge.
These instructions while they tell you to shutdown the "Wired connection
1":
sudo nmcli con down "Wired connection 1"
They neglect to tell you how to ensure that the wired network connection
doesn't come up again after a reboot.
This meant that the bridge couldn't come up:
br0: connecting (getting IP configuration) to bridge-br0
"br0"
bridge, 06:55:A7:3D:DE:04, sw, mtu 1500
Which is why this service wasn't starting.
Once I shutdown the "Wired Connection 1" the "br0" could come up and
this service started working.
network-manager really needs to be a bit more transparent when things go
wrong. Such as printing a message "Waiting for br0 to come online" would
have really helped.
Have you checked the NetworkManager journal log and
nmcli / nmcli g status / ...
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
