Hi F24 users,
after a manual restart of NetworkManager (for some reasons) with
sudo systemctl restart NetworkManager.service
having some problems:
1. The Networkmanager icon disappeared from the dashboard of the GNOME3 desktop
2. DNS is no more operable: trying to access remote hosts by a hostname: "ping <hostname>" fails with "ping: <hostname>: Name or service not known"
Using the IP address instead of hostname works.
Status of NetworkManager:
sudo systemctl status NetworkManager.service NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2016-07-06 12:47:52 CEST; 10min ago Main PID: 5905 (NetworkManager) Tasks: 5 (limit: 512) CGroup: /system.slice/NetworkManager.service ├─1375 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-enp4s0.pid -lf /var/lib/NetworkManager/dhclient-7c3e2629-ab57-4b └─5905 /usr/sbin/NetworkManager --no-daemon
Jul 06 12:47:52 eule NetworkManager[5905]: <info> [1467802072.8854] device (enp4s0): Activation: successful, device activated. Jul 06 12:47:52 eule NetworkManager[5905]: <info> [1467802072.8862] device (virbr0): state change: secondaries -> activated (reason Jul 06 12:47:52 eule NetworkManager[5905]: <info> [1467802072.9191] device (virbr0): Activation: successful, device activated. Jul 06 12:47:52 eule NetworkManager[5905]: <info> [1467802072.9578] connectivity: check for uri 'http://fedoraproject.org/static/hot Jul 06 12:47:52 eule NetworkManager[5905]: <info> [1467802072.9581] connectivity: check for uri 'http://fedoraproject.org/static/hot Jul 06 12:47:52 eule NetworkManager[5905]: <info> [1467802072.9633] connectivity: check for uri 'http://fedoraproject.org/static/hot Jul 06 12:47:52 eule NetworkManager[5905]: <info> [1467802072.9635] connectivity: check for uri 'http://fedoraproject.org/static/hot Jul 06 12:47:52 eule NetworkManager[5905]: <info> [1467802072.9644] connectivity: check for uri 'http://fedoraproject.org/static/hot Jul 06 12:52:53 eule NetworkManager[5905]: <info> [1467802373.4568] connectivity: check for uri 'http://fedoraproject.org/static/hot Jul 06 12:57:53 eule NetworkManager[5905]: <info> [1467802673.4573] connectivity: check for uri 'http://fedoraproject.org/static/hotlines
Anybody sees this too?
Kind regards
Joachim Backes
Hi, Joachim,
Regarding DNS resolving: the /etc/resolv.conf, which is generated by Network Manager, as responsible for DNS resolving Can you please post the output of cat /etc/reslov.conf after fresh reboot, before restarting NetworkManager, when ping <hostname> succeeds, and after restargin NetworkManager, when "ping: <hostname> fails ?
Also can you also run "journal -f" before restarting NetworkManager as mentioned above, and post the output here (or via pastebin)?
Regards, Rami Rosen http://ramirose.wix.com/ramirosen
On 07/06/16 15:54, Rami Rosen wrote:
Hi, Joachim,
Regarding DNS resolving: the /etc/resolv.conf, which is generated by Network Manager, as responsible for DNS resolving Can you please post the output of cat /etc/reslov.conf after fresh reboot, before restarting NetworkManager, when ping <hostname> succeeds, and after restargin NetworkManager, when "ping: <hostname> fails ?
Hi Rami,
/etc/resolv.conf before NM restart ---------------------------------- # Generated by NetworkManager nameserver 192.168.100.1
/etc/resolv.conf after NM restart ---------------------------------- # Generated by NetworkManager
journalctl -f before and after NM restart: See attached file "journalctl-f" (the dashed line in "journalctl-f" marks the restart)
Kind regards
Joachim Backes
Hi, Joachim,
Apologies, I could only answer just now. The problem is, for sure, that restarting the Network Manager did not create the "nameserver 192.168.100.1" entry in /etc/resolv.conf. This is the entry which is solely responsible for DNS name resolving, and its omission deprives you from getting an answer to your ping request you mentioned.
I am unsure as to what is the exact reason. I would suggest the following three actions, to further try to understand the issue:
1) post here the content of /etc/NetworkManager/NetworkManager.conf 2) if this config file has "dns=dnsmasq" entry, try to comment it and restart NetworkManager, then see if /etc/resolv.conf is empty or not. 3) tell us if selinux is enabled on this machine (the output of "getenforce" from the command line)
Regards, Rami Rosen http://ramirose.wix.com/ramirosen
On 6 July 2016 at 17:29, Joachim Backes joachim.backes@rhrk.uni-kl.de wrote:
On 07/06/16 15:54, Rami Rosen wrote:
Hi, Joachim,
Regarding DNS resolving: the /etc/resolv.conf, which is generated by Network Manager, as responsible for DNS resolving Can you please post the output of cat /etc/reslov.conf after fresh reboot, before restarting NetworkManager, when ping <hostname> succeeds, and after restargin NetworkManager, when "ping: <hostname> fails ?
Hi Rami,
/etc/resolv.conf before NM restart
# Generated by NetworkManager nameserver 192.168.100.1
/etc/resolv.conf after NM restart
# Generated by NetworkManager
journalctl -f before and after NM restart: See attached file "journalctl-f" (the dashed line in "journalctl-f" marks the restart)
Kind regards
Joachim Backes
--
Fedora release 24 (Twenty Four) Kernel-4.6.3-300.fc24.x86_64
Joachim Backes joachim.backes@rhrk.uni-kl.de http://www-user.rhrk.uni-kl.de/~backes/
On 07/07/16 14:51, Rami Rosen wrote:
Hi, Joachim,
Apologies, I could only answer just now. The problem is, for sure, that restarting the Network Manager did not create the "nameserver 192.168.100.1" entry in /etc/resolv.conf. This is the entry which is solely responsible for DNS name resolving, and its omission deprives you from getting an answer to your ping request you mentioned.
I am unsure as to what is the exact reason. I would suggest the following three actions, to further try to understand the issue:
Hi Rami,
Today morning, I filed a BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1353184
The BZ seems now to be under examination.
- post here the content of /etc/NetworkManager/NetworkManager.conf
see attachment!
- if this config file has "dns=dnsmasq" entry, try to comment it and
restart NetworkManager, then see if /etc/resolv.conf is empty or not. 3) tell us if selinux is enabled on this machine (the output of "getenforce" from the command line)
/etc/selinux/config has a line:
SELINUX=disabled
Kind regards and thanks for your efforts
Joachim Backes
--
Fedora release 24 (Twenty Four) Kernel-4.6.3-300.fc24.x86_64
Joachim Backes joachim.backes@rhrk.uni-kl.de http://www-user.rhrk.uni-kl.de/~backes/
-
Joachim Backes -
Rami Rosen