Control: tag -1 + fixed-upstream Hi,
On Fri, 22 Aug 2014 01:38:26 +0200 Michael Biebl <bi...@debian.org> wrote: > Am 21.08.2014 20:26, schrieb Russ Allbery: > > Aug 21 10:33:19 wanderer NetworkManager[642]: <info> dhclient started with > > pid 17691 > > Aug 21 10:33:19 wanderer NetworkManager[642]: <info> Activation (wlan0) > > Stage 3 of 5 (IP Configure Start) complete. > > Aug 21 10:33:19 wanderer dhclient: Internet Systems Consortium DHCP Client > > 4.3.1 > > Aug 21 10:33:19 wanderer NetworkManager[642]: <info> (wlan0): DHCPv4 client > > pid 17691 exited with status -1 > > Aug 21 10:33:19 wanderer NetworkManager[642]: <warn> DHCP client died > > abnormally > > > > Downgrading network-manager to 0.9.10.0-1 fixes the problem. It looks > > like something went wrong with the NMU. Copying Micah. > > > Russ, > we just discussed this issue. It's most likely caused by a systemd > update where we restart journald in postinst. > That somehow seems to break the stdout->jounal forwarding, e.g. from NM > to its dhclient child process > If you restart NetworkManager.service, this will reset the state and fix > the issue. > By downgrading to -1, you triggered such a restart of NetworkManager, so > the downgrade is a red herring. > > To reproduce the problem, you can simply run > systemctl restart systemd-journald.service > and then try to re-connect a NM connection and you'll experience the > same issue even with -1. I've just been hit by this bug. The RedHat BTS says it is fixed upstream since september: https://bugzilla.redhat.com/show_bug.cgi?id=1136836#c3 Thanks, _g
signature.asc
Description: OpenPGP digital signature
