Bug#859147: [Pkg-utopia-maintainers] Bug#859147: network-manager: restart failure on upgrade
Purged laptop-mode-tools, rebooted, no change. network-manager is properly started at boot time, service can be stopped, but not started again afterwards: systemd now has a "(kManager)" child at near-100% CPU. Found the culprit: I have a broken schroot configuration (talk about pending work and switching to other tasks...), where the chroot is under my home dir, which gets mounted in the chroot. Schroot does not detect the loop and recursively mounts all /home submounts, apparently until a 65535 mountpoint limit Thus I assume that systemd is attempting to mount something, and not dealing properly with the error ? - Mail original - > De: ydir...@free.fr > À: "Michael Biebl" > Cc: 859...@bugs.debian.org > Envoyé: Samedi 1 Avril 2017 10:49:08 > Objet: Re: [Pkg-utopia-maintainers] Bug#859147: network-manager: restart > failure on upgrade > > Will test this soon. > > Oh, just noticed that the fan was indeed noisy... and top reports > this: > > PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ > COMMAND > 6019 root 20 0 237608 96996 2368 R 100.0 1.2 0:30.49 > (kManager) > > I can't seem to find what a "kManager" process could be around here. > There > is but a common suffix with NetworkManager, but I admit I don't see > why it > would be truncated. Looking at /proc it just looks like a systemd > thread, and > it gets started and restarted again and again. > > - Mail original - > > De: "Michael Biebl" > > À: ydir...@free.fr > > Cc: 859...@bugs.debian.org > > Envoyé: Vendredi 31 Mars 2017 11:12:38 > > Objet: Re: [Pkg-utopia-maintainers] Bug#859147: network-manager: > > restart failure on upgrade > > > > Am 31.03.2017 um 11:08 schrieb ydir...@free.fr: > > > Here is the relevant journalctl -alb excerpt, sending more > > > details > > > in private mail > > > > > > Mar 30 20:22:06 yantop systemd[1]: Stopping Network Manager Wait > > > Online... > > > Mar 30 20:22:06 yantop systemd[1]: Stopping Network Manager... > > > Mar 30 20:22:06 yantop NetworkManager[4948]: > > > [1490898126.5839] caught SIGTERM, shutting down normally. > > > Mar 30 20:22:06 yantop NetworkManager[4948]: > > > [1490898126.6660] device (wlan0): state change: unavailable -> > > > unmanaged (reason 'unmanaged') [20 10 3] > > > Mar 30 20:22:06 yantop NetworkManager[4948]: > > > [1490898126.6663] device (wlan0): set-hw-addr: reset MAC address > > > to B4:6D:83:58:53:31 (unmanage) > > > Mar 30 20:22:06 yantop NetworkManager[4948]: > > > [1490898126.6676] device (E0:98:61:62:F4:53): state change: > > > disconnected -> unmanaged (reason 'unmanaged') [30 10 3] > > > Mar 30 20:22:06 yantop NetworkManager[4948]: > > > [1490898126.6761] device (44:00:10:24:8F:70): state change: > > > disconnected -> unmanaged (reason 'unmanaged') [30 10 3] > > > Mar 30 20:22:06 yantop NetworkManager[4948]: > > > [1490898126.8186] exiting (success) > > > Mar 30 20:22:07 yantop systemd[1]: Stopped Network Manager. > > > Mar 30 20:22:07 yantop systemd[1]: Starting Network Manager... > > > Mar 30 20:23:06 yantop systemd[1]: Starting Laptop Mode Tools - > > > Battery Polling Service... > > > Mar 30 20:23:06 yantop systemd[1]: Reloading Laptop Mode Tools. > > > Mar 30 20:23:06 yantop systemd[1]: Started Laptop Mode Tools - > > > Battery Polling Service. > > > Mar 30 20:23:06 yantop laptop_mode[5372]: Laptop mode > > > Mar 30 20:23:06 yantop laptop_mode[5372]: enabled, not active > > > [unchanged] > > > Mar 30 20:23:06 yantop systemd[1]: Reloaded Laptop Mode Tools. > > > Mar 30 20:23:37 yantop systemd-journald[398]: Suppressed 1050 > > > messages from /init.scope > > > Mar 30 20:23:37 yantop systemd[1]: NetworkManager.service: Start > > > operation timed out. Terminating. > > > > Your systemd instance seems to be in a confused state. I wonder if > > that's related to laptop-mode-tools. > > Try purging that package and reboot to reset the state. > > > > > > -- > > Why is it that all of the instruments seeking intelligent life in > > the > > universe are pointed away from Earth? > > > > >
Bug#859147: [Pkg-utopia-maintainers] Bug#859147: network-manager: restart failure on upgrade
Will test this soon. Oh, just noticed that the fan was indeed noisy... and top reports this: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 6019 root 20 0 237608 96996 2368 R 100.0 1.2 0:30.49 (kManager) I can't seem to find what a "kManager" process could be around here. There is but a common suffix with NetworkManager, but I admit I don't see why it would be truncated. Looking at /proc it just looks like a systemd thread, and it gets started and restarted again and again. - Mail original - > De: "Michael Biebl" > À: ydir...@free.fr > Cc: 859...@bugs.debian.org > Envoyé: Vendredi 31 Mars 2017 11:12:38 > Objet: Re: [Pkg-utopia-maintainers] Bug#859147: network-manager: restart > failure on upgrade > > Am 31.03.2017 um 11:08 schrieb ydir...@free.fr: > > Here is the relevant journalctl -alb excerpt, sending more details > > in private mail > > > > Mar 30 20:22:06 yantop systemd[1]: Stopping Network Manager Wait > > Online... > > Mar 30 20:22:06 yantop systemd[1]: Stopping Network Manager... > > Mar 30 20:22:06 yantop NetworkManager[4948]: > > [1490898126.5839] caught SIGTERM, shutting down normally. > > Mar 30 20:22:06 yantop NetworkManager[4948]: > > [1490898126.6660] device (wlan0): state change: unavailable -> > > unmanaged (reason 'unmanaged') [20 10 3] > > Mar 30 20:22:06 yantop NetworkManager[4948]: > > [1490898126.6663] device (wlan0): set-hw-addr: reset MAC address > > to B4:6D:83:58:53:31 (unmanage) > > Mar 30 20:22:06 yantop NetworkManager[4948]: > > [1490898126.6676] device (E0:98:61:62:F4:53): state change: > > disconnected -> unmanaged (reason 'unmanaged') [30 10 3] > > Mar 30 20:22:06 yantop NetworkManager[4948]: > > [1490898126.6761] device (44:00:10:24:8F:70): state change: > > disconnected -> unmanaged (reason 'unmanaged') [30 10 3] > > Mar 30 20:22:06 yantop NetworkManager[4948]: > > [1490898126.8186] exiting (success) > > Mar 30 20:22:07 yantop systemd[1]: Stopped Network Manager. > > Mar 30 20:22:07 yantop systemd[1]: Starting Network Manager... > > Mar 30 20:23:06 yantop systemd[1]: Starting Laptop Mode Tools - > > Battery Polling Service... > > Mar 30 20:23:06 yantop systemd[1]: Reloading Laptop Mode Tools. > > Mar 30 20:23:06 yantop systemd[1]: Started Laptop Mode Tools - > > Battery Polling Service. > > Mar 30 20:23:06 yantop laptop_mode[5372]: Laptop mode > > Mar 30 20:23:06 yantop laptop_mode[5372]: enabled, not active > > [unchanged] > > Mar 30 20:23:06 yantop systemd[1]: Reloaded Laptop Mode Tools. > > Mar 30 20:23:37 yantop systemd-journald[398]: Suppressed 1050 > > messages from /init.scope > > Mar 30 20:23:37 yantop systemd[1]: NetworkManager.service: Start > > operation timed out. Terminating. > > Your systemd instance seems to be in a confused state. I wonder if > that's related to laptop-mode-tools. > Try purging that package and reboot to reset the state. > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? > >
Bug#859147: [Pkg-utopia-maintainers] Bug#859147: network-manager: restart failure on upgrade
Am 31.03.2017 um 11:08 schrieb ydir...@free.fr: > Here is the relevant journalctl -alb excerpt, sending more details in private > mail > > Mar 30 20:22:06 yantop systemd[1]: Stopping Network Manager Wait Online... > Mar 30 20:22:06 yantop systemd[1]: Stopping Network Manager... > Mar 30 20:22:06 yantop NetworkManager[4948]: [1490898126.5839] caught > SIGTERM, shutting down normally. > Mar 30 20:22:06 yantop NetworkManager[4948]: [1490898126.6660] device > (wlan0): state change: unavailable -> unmanaged (reason 'unmanaged') [20 10 3] > Mar 30 20:22:06 yantop NetworkManager[4948]: [1490898126.6663] device > (wlan0): set-hw-addr: reset MAC address to B4:6D:83:58:53:31 (unmanage) > Mar 30 20:22:06 yantop NetworkManager[4948]: [1490898126.6676] device > (E0:98:61:62:F4:53): state change: disconnected -> unmanaged (reason > 'unmanaged') [30 10 3] > Mar 30 20:22:06 yantop NetworkManager[4948]: [1490898126.6761] device > (44:00:10:24:8F:70): state change: disconnected -> unmanaged (reason > 'unmanaged') [30 10 3] > Mar 30 20:22:06 yantop NetworkManager[4948]: [1490898126.8186] > exiting (success) > Mar 30 20:22:07 yantop systemd[1]: Stopped Network Manager. > Mar 30 20:22:07 yantop systemd[1]: Starting Network Manager... > Mar 30 20:23:06 yantop systemd[1]: Starting Laptop Mode Tools - Battery > Polling Service... > Mar 30 20:23:06 yantop systemd[1]: Reloading Laptop Mode Tools. > Mar 30 20:23:06 yantop systemd[1]: Started Laptop Mode Tools - Battery > Polling Service. > Mar 30 20:23:06 yantop laptop_mode[5372]: Laptop mode > Mar 30 20:23:06 yantop laptop_mode[5372]: enabled, not active [unchanged] > Mar 30 20:23:06 yantop systemd[1]: Reloaded Laptop Mode Tools. > Mar 30 20:23:37 yantop systemd-journald[398]: Suppressed 1050 messages from > /init.scope > Mar 30 20:23:37 yantop systemd[1]: NetworkManager.service: Start operation > timed out. Terminating. Your systemd instance seems to be in a confused state. I wonder if that's related to laptop-mode-tools. Try purging that package and reboot to reset the state. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#859147: [Pkg-utopia-maintainers] Bug#859147: network-manager: restart failure on upgrade
Here is the relevant journalctl -alb excerpt, sending more details in private mail Mar 30 20:22:06 yantop systemd[1]: Stopping Network Manager Wait Online... Mar 30 20:22:06 yantop systemd[1]: Stopping Network Manager... Mar 30 20:22:06 yantop NetworkManager[4948]: [1490898126.5839] caught SIGTERM, shutting down normally. Mar 30 20:22:06 yantop NetworkManager[4948]: [1490898126.6660] device (wlan0): state change: unavailable -> unmanaged (reason 'unmanaged') [20 10 3] Mar 30 20:22:06 yantop NetworkManager[4948]: [1490898126.6663] device (wlan0): set-hw-addr: reset MAC address to B4:6D:83:58:53:31 (unmanage) Mar 30 20:22:06 yantop NetworkManager[4948]: [1490898126.6676] device (E0:98:61:62:F4:53): state change: disconnected -> unmanaged (reason 'unmanaged') [30 10 3] Mar 30 20:22:06 yantop NetworkManager[4948]: [1490898126.6761] device (44:00:10:24:8F:70): state change: disconnected -> unmanaged (reason 'unmanaged') [30 10 3] Mar 30 20:22:06 yantop NetworkManager[4948]: [1490898126.8186] exiting (success) Mar 30 20:22:07 yantop systemd[1]: Stopped Network Manager. Mar 30 20:22:07 yantop systemd[1]: Starting Network Manager... Mar 30 20:23:06 yantop systemd[1]: Starting Laptop Mode Tools - Battery Polling Service... Mar 30 20:23:06 yantop systemd[1]: Reloading Laptop Mode Tools. Mar 30 20:23:06 yantop systemd[1]: Started Laptop Mode Tools - Battery Polling Service. Mar 30 20:23:06 yantop laptop_mode[5372]: Laptop mode Mar 30 20:23:06 yantop laptop_mode[5372]: enabled, not active [unchanged] Mar 30 20:23:06 yantop systemd[1]: Reloaded Laptop Mode Tools. Mar 30 20:23:37 yantop systemd-journald[398]: Suppressed 1050 messages from /init.scope Mar 30 20:23:37 yantop systemd[1]: NetworkManager.service: Start operation timed out. Terminating. Mar 30 20:23:37 yantop systemd[1]: Failed to start Network Manager. Mar 30 20:23:37 yantop systemd[1]: Dependency failed for Network Manager Wait Online. Mar 30 20:23:37 yantop systemd[1]: NetworkManager-wait-online.service: Job NetworkManager-wait-online.service/start failed with result 'dependency'. Mar 30 20:23:37 yantop systemd[1]: NetworkManager.service: Unit entered failed state. Mar 30 20:23:37 yantop systemd[1]: NetworkManager.service: Failed with result 'timeout'. Mar 30 20:23:37 yantop systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart. Mar 30 20:23:37 yantop systemd[1]: Stopped Network Manager. Mar 30 20:23:37 yantop systemd[1]: Starting Network Manager... Mar 30 20:23:38 yantop systemd[1]: Reloading. Mar 30 20:23:39 yantop systemd[1]: Failed to set up mount unit: Invalid argument Mar 30 20:23:39 yantop systemd[1]: Failed to set up mount unit: Invalid argument Mar 30 20:23:39 yantop systemd[1]: Failed to set up mount unit: Invalid argument Mar 30 20:23:39 yantop systemd[1]: Failed to set up mount unit: Invalid argument - Mail original - > De: "Michael Biebl" > À: ydir...@free.fr, 859...@bugs.debian.org > Envoyé: Vendredi 31 Mars 2017 00:12:59 > Objet: Re: [Pkg-utopia-maintainers] Bug#859147: network-manager: restart > failure on upgrade > > Am 30.03.2017 um 23:50 schrieb ydir...@free.fr: > > > Any other information would be useful ? > > Can you attach the following information > journalctl -alb > systemd-cgls > > > > > > > > -- > Why is it that all of the instruments seeking intelligent life in the > universe are pointed away from Earth? >
Bug#859147: [Pkg-utopia-maintainers] Bug#859147: network-manager: restart failure on upgrade
Am 30.03.2017 um 23:50 schrieb ydir...@free.fr: > Any other information would be useful ? Can you attach the following information journalctl -alb systemd-cgls -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Bug#859147: network-manager: restart failure on upgrade
Package: network-manager Version: 1.6.2-3 When upgrading from 1.6.2-2: Setting up network-manager (1.6.2-3) ... Job for NetworkManager.service failed because a timeout was exceeded. See "systemctl status NetworkManager.service" and "journalctl -xe" for details. invoke-rc.d: initscript network-manager, action "restart" failed. ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: timeout) since Thu 2017-03-30 23:43:52 CEST; 4ms ago Docs: man:NetworkManager(8) Process: 16706 ExecStart=/usr/sbin/NetworkManager --no-daemon (code=killed, signal=TERM) Main PID: 16706 (code=killed, signal=TERM) CPU: 1min 30.013s Mar 30 23:43:52 yantop systemd[1]: NetworkManager.service: Unit entered failed state. Mar 30 23:43:52 yantop systemd[1]: NetworkManager.service: Failed with result 'timeout'. dpkg: error processing package network-manager (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: network-manager === # cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback === # cat /etc/network/interfaces.d/LOCAL-lxc auto lxcbr0 iface lxcbr0 inet static address 10.100.0.1 bridge_ports none bridge_fd 0 bridge_maxwait 0 up iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE Any other information would be useful ?
