Your message dated Sat, 17 Jun 2017 15:08:57 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-utopia-maintainers] Bug#859147: network-manager:
restart failure on upgrade
has caused the Debian Bug report #859147,
regarding network-manager: restart failure on upgrade
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.)
--
859147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859147
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 ?
--- End Message ---
--- Begin Message ---
On Sat, 1 Apr 2017 16:17:02 +0200 (CEST) [email protected] wrote:
> 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
That sounds like it might be a bug in schroot.
Thanks for further investigating this issue, will close this bug report
as it doesn't seem to be caused by NetworkManager itself.
Michael
--
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
--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
