Quantcast
Viewing all articles
Browse latest Browse all 4825

Troubleshooting • Re: Failing services on Pi bootup - ModemManager and polkit

I'm currently on Bookworm.

I purged ModemManager and am still running into failures with NetworkManager and NetworkManager-wait-online.

I can see that NetworkManager attempts to start several times but fails.
systemctl:

Code:

× NetworkManager.service - Network Manager     Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; preset: enabled)     Active: failed (Result: signal) since Sat 2024-03-09 13:50:26 GMT; 2min 12s ago   Duration: 139ms       Docs: man:NetworkManager(8)    Process: 851 ExecStart=/usr/sbin/NetworkManager --no-daemon (code=killed, signal=ILL)   Main PID: 851 (code=killed, signal=ILL)        CPU: 164msMar 09 13:50:26 SALTY-PI systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 5.Mar 09 13:50:26 SALTY-PI systemd[1]: Stopped NetworkManager.service - Network Manager.Mar 09 13:50:26 SALTY-PI systemd[1]: NetworkManager.service: Start request repeated too quickly.Mar 09 13:50:26 SALTY-PI systemd[1]: NetworkManager.service: Failed with result 'signal'.Mar 09 13:50:26 SALTY-PI systemd[1]: Failed to start NetworkManager.service - Network Manager.
NetworkManager-wait-online systemctl:

Code:

× NetworkManager-wait-online.service - Network Manager Wait Online     Loaded: loaded (/lib/systemd/system/NetworkManager-wait-online.service; enabled; preset: enabled)     Active: failed (Result: signal) since Sat 2024-03-09 13:50:26 GMT; 2min 51s ago       Docs: man:nm-online(1)    Process: 858 ExecStart=/usr/bin/nm-online -s -q (code=killed, signal=TERM)   Main PID: 858 (code=killed, signal=TERM)        CPU: 51msMar 09 13:50:25 SALTY-PI systemd[1]: Starting NetworkManager-wait-online.service - Network Manager Wait Online...Mar 09 13:50:26 SALTY-PI systemd[1]: NetworkManager-wait-online.service: Main process exited, code=killed, status=15/TERMMar 09 13:50:26 SALTY-PI systemd[1]: NetworkManager-wait-online.service: Failed with result 'signal'.Mar 09 13:50:26 SALTY-PI systemd[1]: Stopped NetworkManager-wait-online.service - Network Manager Wait Online.Mar 09 13:50:26 SALTY-PI systemd[1]: Dependency failed for NetworkManager-wait-online.service - Network Manager Wait Online.Mar 09 13:50:26 SALTY-PI systemd[1]: NetworkManager-wait-online.service: Job NetworkManager-wait-online.service/start failed with result 'dependency'.
journalctl -xeu on the NetworkManager.service reports:

Code:

Mar 09 13:50:22 SALTY-PI systemd[1]: Starting NetworkManager.service - Network Manager...   Subject: A start job for unit NetworkManager.service has begun execution   Defined-By: systemd   Support: https://www.debian.org/support      A start job for unit NetworkManager.service has begun execution.      The job identifier is 112.Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.0125] NetworkManager (version 1.42.4) is starting... (boot:08f4838f-ce06-4806-b74c-8b9a11148649)Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.0146] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)Mar 09 13:50:23 SALTY-PI systemd[1]: Started NetworkManager.service - Network Manager.   Subject: A start job for unit NetworkManager.service has finished successfully   Defined-By: systemd   Support: https://www.debian.org/support      A start job for unit NetworkManager.service has finished successfully.      The job identifier is 112.Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.0559] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.1139] manager[0x55a9225000]: monitoring kernel firmware directory '/lib/firmware'.Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.1142] monitoring ifupdown state file '/run/network/ifstate'.Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.4386] hostname: hostname: using hostnamedMar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.4387] hostname: static hostname changed from (none) to "SALTY-PI"Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.4397] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink (auto)Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.4434] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/platform/soc/fe300000.mmcnr/mmc_host/mmc1/mmc1:0001/mmc1:0001:1/ieee80211/phy0/rfkill1) (driver brcmfmac)Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.4441] manager[0x55a9225000]: rfkill: Wi-Fi hardware radio set enabledMar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.4443] manager[0x55a9225000]: rfkill: WWAN hardware radio set enabledMar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.5498] Loaded device plugin: NMAtmManager (/usr/lib/aarch64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-adsl.so)Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.6203] Loaded device plugin: NMTeamFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-team.so)Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.6649] Loaded device plugin: NMWifiFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-wifi.so)Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.8303] Loaded device plugin: NMBluezManager (/usr/lib/aarch64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-bluetooth.so)Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.8456] Loaded device plugin: NMWwanFactory (/usr/lib/aarch64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-wwan.so)Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.8466] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state fileMar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.8468] manager: rfkill: WWAN enabled by radio killswitch; enabled by state fileMar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.8469] manager: Networking is enabled by state fileMar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.8840] settings: Loaded settings plugin: ifupdown ("/usr/lib/aarch64-linux-gnu/NetworkManager/1.42.4/libnm-settings-plugin-ifupdown.so")Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.8843] settings: Loaded settings plugin: keyfile (internal)Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.8844] ifupdown: management mode: unmanagedMar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.8844] ifupdown:       interface-parser: parsing file /etc/network/interfacesMar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.8845] ifupdown:       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.8846] ifupdown: interfaces file /etc/network/interfaces.d/* doesn't existMar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.8847] ifupdown:       interface-parser: finished parsing file /etc/network/interfacesMar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.9323] dhcp: init: Using DHCP client 'internal'Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.9332] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.9795] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.9834] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.9876] device (lo): Activation: starting connection 'lo' (93b14811-378e-4727-bb35-d32b631720ca)Mar 09 13:50:23 SALTY-PI NetworkManager[733]: <info>  [1709992223.9911] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)Mar 09 13:50:24 SALTY-PI NetworkManager[733]: <info>  [1709992224.0039] settings: (eth0): created default wired connection 'Wired connection 1'Mar 09 13:50:24 SALTY-PI NetworkManager[733]: <info>  [1709992224.0046] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')Mar 09 13:50:24 SALTY-PI NetworkManager[733]: <info>  [1709992224.0150] device (wlan0): driver supports Access Point (AP) modeMar 09 13:50:24 SALTY-PI NetworkManager[733]: <info>  [1709992224.0191] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)Mar 09 13:50:24 SALTY-PI NetworkManager[733]: <info>  [1709992224.0226] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')Mar 09 13:50:24 SALTY-PI systemd[1]: NetworkManager.service: Main process exited, code=killed, status=4/ILL   Subject: Unit process exited   Defined-By: systemd   Support: https://www.debian.org/support      An ExecStart= process belonging to unit NetworkManager.service has exited.      The process' exit code is 'killed' and its exit status is 4.Mar 09 13:50:24 SALTY-PI systemd[1]: NetworkManager.service: Failed with result 'signal'.   Subject: Unit failed   Defined-By: systemd   Support: https://www.debian.org/support      The unit NetworkManager.service has entered the 'failed' state with result 'signal'.Mar 09 13:50:24 SALTY-PI systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 1.
Fails with result 'signal'. I don't understand what the issue is.
I don't even know if it is another issue, but the only thing I see here is the state of both the ethernet and wireless interfaces changes from unmanaged to unavailable because they are 'managed'.

NetworkManager-wait-online seems to be a dependency service of NetworkManager, and fails because NetworkManager does.
It doesn't report any other issue other than the result of NetworkManager.
journalctl -xeu on NetworkManager-wait-online:

Code:

Mar 09 13:50:24 SALTY-PI systemd[1]: NetworkManager-wait-online.service: Main process exited, code=killed, status=15/TERM   Subject: Unit process exited   Defined-By: systemd   Support: https://www.debian.org/support      An ExecStart= process belonging to unit NetworkManager-wait-online.service has exited.      The process' exit code is 'killed' and its exit status is 15.Mar 09 13:50:24 SALTY-PI systemd[1]: NetworkManager-wait-online.service: Failed with result 'signal'.   Subject: Unit failed   Defined-By: systemd   Support: https://www.debian.org/support      The unit NetworkManager-wait-online.service has entered the 'failed' state with result 'signal'.Mar 09 13:50:24 SALTY-PI systemd[1]: Stopped NetworkManager-wait-online.service - Network Manager Wait Online.   Subject: A stop job for unit NetworkManager-wait-online.service has finished   Defined-By: systemd   Support: https://www.debian.org/support      A stop job for unit NetworkManager-wait-online.service has finished.

Statistics: Posted by jimjamz — Sat Mar 16, 2024 10:19 pm



Viewing all articles
Browse latest Browse all 4825

Trending Articles