[arch-general] Bug NetworkManager when restart NetworkManager service
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.
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...
...
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.
Network goes down because NetworkManager leaves dhcpcd running. In fact my network remains up after running "systemctl stop NetworkManager.service" because dhcpcd is left managing enp0s25. If NetworkManager sees dhcpcd managing an interface when NetworkManager starts up, NetworkManager does funny things. So, why does "systemctl stop NetworkManager.service" leave dhcpcd running? The workaround: sudo systemctl stop NetworkManager.service sudo killall dhcpcd sudo systemctl start NetworkManager.service Here is a shell session where I (effectively) do the above: kyle@landru ~ $ sudo systemctl stop NetworkManager.service [sudo] password for kyle: kyle@landru ~ $ systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) Active: inactive (dead) since Tue 2014-04-08 15:41:08 PDT; 8s ago Process: 2792 ExecStart=/usr/bin/NetworkManager --no-daemon (code=exited, status=0/SUCCESS) Main PID: 2792 (code=exited, status=0/SUCCESS) Apr 08 15:14:14 landru NetworkManager[2792]: <info> Activation (enp0s25) suc.... Apr 08 15:14:21 landru dhcpcd[2822]: enp0s25: no IPv6 Routers available Apr 08 15:14:29 landru NetworkManager[2792]: <info> (enp0s25): IP6 addrconf .... Apr 08 15:14:29 landru NetworkManager[2792]: <info> Activation (enp0s25) Sta.... Apr 08 15:14:29 landru NetworkManager[2792]: <info> Activation (enp0s25) Sta.... Apr 08 15:14:29 landru NetworkManager[2792]: <info> Activation (enp0s25) Sta.... Apr 08 15:41:08 landru systemd[1]: Stopping Network Manager... Apr 08 15:41:08 landru NetworkManager[2792]: <info> caught signal 15, shutti.... Apr 08 15:41:08 landru NetworkManager[2792]: <info> Writing DNS information ...f Apr 08 15:41:08 landru systemd[1]: Stopped Network Manager. Hint: Some lines were ellipsized, use -l to show in full. kyle@landru ~ $ systemctl status | grep -A 1 NetworkManager.service │ │ └─3623 grep --color=auto -A 1 NetworkManager.service │ └─user@2290.service -- ├─NetworkManager.service │ └─2822 /usr/bin/dhcpcd -B -K -L -G -c /usr/lib/networkmanager/nm-dhcp-client.action enp0s25 kyle@landru ~ $ sudo kill 2822 kyle@landru ~ $ systemctl status | grep -A 1 NetworkManager.service │ │ └─3631 grep --color=auto -A 1 NetworkManager.service │ └─user@2290.service kyle@landru ~ $ systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) Active: inactive (dead) since Tue 2014-04-08 15:41:08 PDT; 4min 25s ago Process: 2792 ExecStart=/usr/bin/NetworkManager --no-daemon (code=exited, status=0/SUCCESS) Main PID: 2792 (code=exited, status=0/SUCCESS) Apr 08 15:14:29 landru NetworkManager[2792]: <info> (enp0s25): IP6 addrconf .... Apr 08 15:14:29 landru NetworkManager[2792]: <info> Activation (enp0s25) Sta.... Apr 08 15:14:29 landru NetworkManager[2792]: <info> Activation (enp0s25) Sta.... Apr 08 15:14:29 landru NetworkManager[2792]: <info> Activation (enp0s25) Sta.... Apr 08 15:41:08 landru systemd[1]: Stopping Network Manager... Apr 08 15:41:08 landru NetworkManager[2792]: <info> caught signal 15, shutti.... Apr 08 15:41:08 landru NetworkManager[2792]: <info> Writing DNS information ...f Apr 08 15:41:08 landru systemd[1]: Stopped Network Manager. Apr 08 15:43:59 landru dhcpcd[2822]: received signal TERM from PID 3626, st...ng Apr 08 15:43:59 landru dhcpcd[2822]: enp0s25: removing interface Hint: Some lines were ellipsized, use -l to show in full. kyle@landru ~ $ sudo systemctl start NetworkManager.service kyle@landru ~ $ --Kyle
2014-04-09 1:21 GMT+02:00 Kyle Terrien <kyleterrien@gmail.com>:
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...
...
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.
Network goes down because NetworkManager leaves dhcpcd running. In fact my network remains up after running "systemctl stop NetworkManager.service" because dhcpcd is left managing enp0s25.
If NetworkManager sees dhcpcd managing an interface when NetworkManager starts up, NetworkManager does funny things.
So, why does "systemctl stop NetworkManager.service" leave dhcpcd running?
The workaround:
sudo systemctl stop NetworkManager.service sudo killall dhcpcd sudo systemctl start NetworkManager.service
Here is a shell session where I (effectively) do the above:
kyle@landru ~ $ sudo systemctl stop NetworkManager.service [sudo] password for kyle: kyle@landru ~ $ systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) Active: inactive (dead) since Tue 2014-04-08 15:41:08 PDT; 8s ago Process: 2792 ExecStart=/usr/bin/NetworkManager --no-daemon (code=exited, status=0/SUCCESS) Main PID: 2792 (code=exited, status=0/SUCCESS)
Apr 08 15:14:14 landru NetworkManager[2792]: <info> Activation (enp0s25) suc.... Apr 08 15:14:21 landru dhcpcd[2822]: enp0s25: no IPv6 Routers available Apr 08 15:14:29 landru NetworkManager[2792]: <info> (enp0s25): IP6 addrconf .... Apr 08 15:14:29 landru NetworkManager[2792]: <info> Activation (enp0s25) Sta.... Apr 08 15:14:29 landru NetworkManager[2792]: <info> Activation (enp0s25) Sta.... Apr 08 15:14:29 landru NetworkManager[2792]: <info> Activation (enp0s25) Sta.... Apr 08 15:41:08 landru systemd[1]: Stopping Network Manager... Apr 08 15:41:08 landru NetworkManager[2792]: <info> caught signal 15, shutti.... Apr 08 15:41:08 landru NetworkManager[2792]: <info> Writing DNS information ...f Apr 08 15:41:08 landru systemd[1]: Stopped Network Manager. Hint: Some lines were ellipsized, use -l to show in full. kyle@landru ~ $ systemctl status | grep -A 1 NetworkManager.service │ │ └─3623 grep --color=auto -A 1 NetworkManager.service │ └─user@2290.service -- ├─NetworkManager.service │ └─2822 /usr/bin/dhcpcd -B -K -L -G -c /usr/lib/networkmanager/nm-dhcp-client.action enp0s25 kyle@landru ~ $ sudo kill 2822 kyle@landru ~ $ systemctl status | grep -A 1 NetworkManager.service │ │ └─3631 grep --color=auto -A 1 NetworkManager.service │ └─user@2290.service kyle@landru ~ $ systemctl status NetworkManager.service ● NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) Active: inactive (dead) since Tue 2014-04-08 15:41:08 PDT; 4min 25s ago Process: 2792 ExecStart=/usr/bin/NetworkManager --no-daemon (code=exited, status=0/SUCCESS) Main PID: 2792 (code=exited, status=0/SUCCESS)
Apr 08 15:14:29 landru NetworkManager[2792]: <info> (enp0s25): IP6 addrconf .... Apr 08 15:14:29 landru NetworkManager[2792]: <info> Activation (enp0s25) Sta.... Apr 08 15:14:29 landru NetworkManager[2792]: <info> Activation (enp0s25) Sta.... Apr 08 15:14:29 landru NetworkManager[2792]: <info> Activation (enp0s25) Sta.... Apr 08 15:41:08 landru systemd[1]: Stopping Network Manager... Apr 08 15:41:08 landru NetworkManager[2792]: <info> caught signal 15, shutti.... Apr 08 15:41:08 landru NetworkManager[2792]: <info> Writing DNS information ...f Apr 08 15:41:08 landru systemd[1]: Stopped Network Manager. Apr 08 15:43:59 landru dhcpcd[2822]: received signal TERM from PID 3626, st...ng Apr 08 15:43:59 landru dhcpcd[2822]: enp0s25: removing interface Hint: Some lines were ellipsized, use -l to show in full. kyle@landru ~ $ sudo systemctl start NetworkManager.service kyle@landru ~ $
--Kyle
Thanks for all. You're right. When stop NetworkManager, leave dhcpcd running: maykel-arch /home/maykel/ :( # systemctl stop NetworkManager maykel-arch /home/maykel/ # ps aux | grep dhcpcd root 8465 0.0 0.0 8648 1012 ? S 10:14 0:00 /usr/bin/dhcpcd -B -K -L -G -c /usr/lib/networkmanager/nm-dhcp-client.action enp4s0f2 root 8562 0.0 0.0 10924 1100 pts/1 S+ 10:17 0:00 grep --color=auto dhcpcd All ok and it works but...Why in Debian, Ubuntu, Opensuse, for example, when restart the networkma nager, I do not need to kill the process networkmanager. Smooth network is well restart. Thanks for all.
On Wed, Apr 9, 2014 at 10:22 AM, Maykel Franco <maykeldebian@gmail.com> wrote:
All ok and it works but...Why in Debian, Ubuntu, Opensuse, for example, when restart the networkma nager, I do not need to kill the process networkmanager. Smooth network is well restart.
Thanks for all.
Please try installing dhclient. It's NetworkManager's preferred DHCP client.
2014-04-09 10:30 GMT+02:00 Jan Alexander Steffens <jan.steffens@gmail.com>:
On Wed, Apr 9, 2014 at 10:22 AM, Maykel Franco <maykeldebian@gmail.com> wrote:
All ok and it works but...Why in Debian, Ubuntu, Opensuse, for example, when restart the networkma nager, I do not need to kill the process networkmanager. Smooth network is well restart.
Thanks for all.
Please try installing dhclient. It's NetworkManager's preferred DHCP client.
OK, but I uninstall dhcpcd? I have to do something to use dhclient networkmanager? Thanks.
On Wed, Apr 9, 2014 at 10:39 AM, Maykel Franco <maykeldebian@gmail.com> wrote:
OK, but I uninstall dhcpcd? I have to do something to use dhclient networkmanager?
No, just reboot or restart NetworkManager (cleaning up dhcpcd if needed).
On Wed, Apr 9, 2014 at 10:39 AM, Maykel Franco <maykeldebian@gmail.com> wrote:
OK, but I uninstall dhcpcd? I have to do something to use dhclient networkmanager?
you can explicitly configure the client to be used, as stated in [0]. cheers! mar77i [0] http://manpages.ubuntu.com/manpages/natty/man5/NetworkManager.conf.5.html
2014-04-09 10:56 GMT+02:00 Martti Kühne <mysatyre@gmail.com>:
On Wed, Apr 9, 2014 at 10:39 AM, Maykel Franco <maykeldebian@gmail.com> wrote:
OK, but I uninstall dhcpcd? I have to do something to use dhclient networkmanager?
you can explicitly configure the client to be used, as stated in [0].
cheers! mar77i
[0] http://manpages.ubuntu.com/manpages/natty/man5/NetworkManager.conf.5.html
Now It works only systemctl restart NetworkManager. Many thanks!!! I love arch, is fastest and the packages is latest...Sorry for my english.
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
participants (4)
-
Jan Alexander Steffens
-
Kyle Terrien
-
Martti Kühne
-
Maykel Franco