this is workaround for me that runs correctly:
in rc.local:
(systemctl stop networking.service; systemctl start networking.service;
systemctl restart networking.service; true) &
if i put the commands one by one, rc.local unit will fail because
systemctl start exits non-zero. notice the 'restart'
** Attachment added: "dpkg-l.txt"
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1551415/+attachment/4812135/+files/dpkg-l.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551415
Title:
how do I debug this?
if i manually run 'ifup -a --read-environment' or 'systemctl start networking'
it brings all stuff up cleanly.
by 'debug' i mean more than just looking at journalctl -u networking
below contents of network/interfaces, journalctl -u networking and
contents of netwroking unit
That sounds like it is related. While doing more debug I found that
network-manager starts dhclient in forground mode (-d) and that is not
affected by bug 1551351. But regardless of how it was started, dhclient
seem not to react on SIGHUP. Maybe disconnecting from the network
manually uses a more a
Have no idea if related to here but just recently on plain old Ubuntu Desktop
installs of 16.04 restarts have slowed done considerably.
For me about 4-5 times slower, actual numbers are 2-3 sec. normally, now 10-15
secs. Others seemed affected with different numbers.
If I disconnect from Network,
Stefan, yeah. kill -11 "fix"es
root@test-x1:~# systemctl start networking
root@test-x1:~# pidof dhclient
1332
root@test-x1:~# kill -11 $(pidof dhclient)
root@test-x1:~# time systemctl stop networking
real0m0.212s
user0m0.008s
sys 0m0.000s
--
You received this bug notification because
** Description changed:
I noticed today on lxd that the latest xenial image is failing to bring down
networking
$ cat /etc/cloud/build.info
build_name: server
serial: 20160227-141431
to reproduce:
$ lxd-images import ubuntu --alias xenial xenial --stream=daily
$ lxc launch
Maybe that is actually related to the dhclient problem. I wonder, if you
kill that manually before the ifdown (kill -11) does get rid of the long
delay?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
does not seem to be lxc specific. Ii reproduced on a cloud-image also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551415
Title:
systemctl stop networking hang / timeout
To manage notifications
it does reproduce after that with simply:
% systemctl start networking
% systemctl stop networking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1551415
Title:
systemctl stop networking hang / timeo
10 matches
Mail list logo
