On 04/08/2014 04:31 AM, Maykel Franco wrote: > Hi, I change for example dns in networkmanager, when restart > NetworkManager , "systemctl restart NetworkManager" the network not > works... > > [maykel@maykel-arch ~]$ sudo systemctl status NetworkManager > ● NetworkManager.service - Network Manager > Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) > Active: active (running) since mar 2014-04-08 12:24:13 CEST; 19s ago > Main PID: 3082 (NetworkManager) > CGroup: /system.slice/NetworkManager.service > ├─1223 /usr/bin/dhcpcd -B -K -L -G -c > /usr/lib/networkmanager/nm-dhcp-client.action enp4s0f2 > └─3082 /usr/bin/NetworkManager --no-daemon > > abr 08 12:24:22 maykel-arch NetworkManager[3082]: <info> (enp4s0f2): > DHCPv4 client pid 3093 exited with status 1 > abr 08 12:24:22 maykel-arch NetworkManager[3082]: <info> Activation > (enp4s0f2) Stage 4 of 5 (IPv4 Configure Timeout) scheduled... > abr 08 12:24:22 maykel-arch NetworkManager[3082]: <info> Activation > (enp4s0f2) Stage 4 of 5 (IPv4 Configure Timeout) started... > abr 08 12:24:22 maykel-arch NetworkManager[3082]: <info> (enp4s0f2): > device state change: ip-config -> failed (reason > 'ip-config-unavailable') [70 120 5] > abr 08 12:24:22 maykel-arch NetworkManager[3082]: <info> > NetworkManager state is now DISCONNECTED > abr 08 12:24:22 maykel-arch NetworkManager[3082]: <info> Marking > connection 'MO2O' invalid. > abr 08 12:24:22 maykel-arch NetworkManager[3082]: <warn> Activation > (enp4s0f2) failed for connection 'MO2O' > abr 08 12:24:22 maykel-arch NetworkManager[3082]: <info> Activation > (enp4s0f2) Stage 4 of 5 (IPv4 Configure Timeout) complete. > abr 08 12:24:22 maykel-arch NetworkManager[3082]: <info> (enp4s0f2): > device state change: failed -> disconnected (reason 'none') [120 30 0] > abr 08 12:24:22 maykel-arch NetworkManager[3082]: <info> (enp4s0f2): > deactivating device (reason 'none') [0] > > I have reboot my computer for network on again. > > Is a bug networkmanager? > > The version is: > > maykel-arch /home/maykel # NetworkManager --version > 0.9.8.8 > > Thanks in advanced. > I did some more poking around. This is a bug in NetworkManager [1]. When dhcpcd is running before NetworkManager (e.g. left running by a previous instance of NetworkManager), NetworkManager does not properly restart dhcpcd. The workaround is to install dhclient. [1] https://bugzilla.gnome.org/show_bug.cgi?id=723746 --Kyle
Attachment:
signature.asc
Description: OpenPGP digital signature
