خرید بک لینک

درباره سایت

feed all

آخرین مطالب

امکانات وب

NetworkManager fails to coect, but I can do it manually

This almost certainly looks like a bug in NetworkManager to me. I installed Ubuntu 16.04 and at first it coected to my WiFi just fine. But next day NetworkManager suddenly discoected and any attempt to recoect failed after a few seconds. So I was thinking, maybe software updated pulled in a bad keel driver, or perhaps it is some weird wifi issue, so I plugged my computer into etheet port instead, and discovered that I am having exactly the same issue with etheet interface.

syslog seems to indicate that coection fails when dhclient gets killed for some reason:

Code:

Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7535] device (enp2s0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7537] manager: NetworkManager state is now DISCONNECTED
Apr 30 19:26:17 eggsnow NetworkManager[919]: <wa>  [1462040777.7541] device (enp2s0): Activation: failed for coection 'Wired coection 2'
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7550] device (enp2s0): state change: failed -> discoected (reason 'none') [120 30 0]
Apr 30 19:26:17 eggsnow avahi-daemon[854]: Withdrawing address record for fe80::9829:8d7f:ac9:9374 on enp2s0.
Apr 30 19:26:17 eggsnow avahi-daemon[854]: Leaving mDNS multicast group on interface enp2s0.IPv6 with address fe80::9829:8d7f:ac9:9374.
Apr 30 19:26:17 eggsnow avahi-daemon[854]: Interface enp2s0.IPv6 no longer relevant for mDNS.
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7613] policy: auto-activating coection 'Wired coection 2'
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7645] device (enp2s0): Activation: starting coection 'Wired coection 2' (e7973309-a682-42c3-9503-d975c9a29722)
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7654] device (enp2s0): state change: discoected -> prepare (reason 'none') [30 40 0]
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7662] manager: NetworkManager state is now CONNECTING
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7676] device (enp2s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7690] device (enp2s0): state change: config -> ip-config (reason 'none') [50 70 0]
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7694] dhcp4 (enp2s0): activation: begiing transaction (timeout in 45 seconds)
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7741] dhcp4 (enp2s0): dhclient started with pid 2740
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7776] dhcp4 (enp2s0): client pid 2740 killed by signal 15
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7780] dhcp4 (enp2s0): state changed unknown -> fail
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7783] dhcp4 (enp2s0): canceled DHCP transaction
Apr 30 19:26:17 eggsnow NetworkManager[919]: <info>  [1462040777.7784] dhcp4 (enp2s0): state changed fail -> done
Apr 30 19:26:17 eggsnow keel: [ 1358.121594] audit: type=1400 audit(1462040777.770:40): apparmor="DENIED" operation="coect" profile="/usr/lib/NetworkManager/nm-dhcp-helper" name="/var/run/NetworkManager/private-dhcp" pid=2741 comm="nm-dhcp-helper" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0
Apr 30 19:26:18 eggsnow avahi-daemon[854]: Joining mDNS multicast group on interface enp2s0.IPv6 with address fe80::9829:8d7f:ac9:9374.
Apr 30 19:26:18 eggsnow avahi-daemon[854]: New relevant interface enp2s0.IPv6 for mDNS.
Apr 30 19:26:18 eggsnow avahi-daemon[854]: Registering new address record for fe80::9829:8d7f:ac9:9374 on enp2s0.*.
I then tried bringing network up from the command line by disabling NetworkManager and then using "ifconfig enp2s0 up" and "dhclient enp2s0" and that worked - I was able to coect to the network. So it seems that my system configuration got buggered somehow, even though I haven't touched any config files or installed any non-ubuntu packages.

I am looking for a community suggestion here - should I convert this into a bug report, or should I troubleshoot some more (but I caot find any good troubleshooting guides for 16.04, and the ones I found for 14.04 seem obsolete, things have moved, etc).

برچسب: نویسنده: استخدام کار تاريخ: يکشنبه 12 ارديبهشت 1395 ساعت: 2:46

صفحه بندی

آرشیو مطالب

پيوندهای روزانه

لینک دوستان

خبرنامه