Re: Fedora 24: Network inoperable after a manual NetworkManager restart
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. 1) post here the content of /etc/NetworkManager/NetworkManager.conf see attachment! 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) /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 http://www-user.rhrk.uni-kl.de/~backes/ # Configuration file for NetworkManager. # # See "man 5 NetworkManager.conf" for details. # # The directory /usr/lib/NetworkManager/conf.d/ can contain additional configuration # snippets installed by packages. These files are read before NetworkManager.conf # and have thus lowest priority. # The directory /etc/NetworkManager/conf.d/ can contain additional configuration # snippets. Those snippets override the settings from this main file. # # The files within one conf.d/ directory are read in asciibetical order. # # If /etc/NetworkManager/conf.d/ contains a file with the same name as # /usr/lib/NetworkManager/conf.d/, the latter file is shadowed and thus ignored. # Hence, to disable loading a file from /usr/lib/NetworkManager/conf.d/ you can # put an empty file with the same name. # # If two files define the same key, the one that is read afterwards will overwrite # the previous one. [main] #plugins=ifcfg-rh,ibft [logging] # When debugging NetworkManager, enabling debug logging is of great help. # # Logfiles contain no passwords and little sensitive information. But please # check before posting the file online. You can also personally hand over the # logfile to a NM developer to treat it confidential. Meet us on #nm on freenode. # Please post full logfiles except minimal modifications of private data. # # You can also change the log-level at runtime via # $ nmcli general logging level TRACE domains ALL # However, usually it's cleaner to enable debug logging # in the configuration and restart NetworkManager so that # debug logging is enabled from the start. # # You will find the logfiles in syslog, for example via # $ journalctl -u NetworkManager # #level=TRACE #domains=ALL -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 24: Network inoperable after a manual NetworkManager restart
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 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 succeeds, >> and after restargin NetworkManager, when >> "ping: 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 > http://www-user.rhrk.uni-kl.de/~backes/ -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Fedora 24: Network inoperable after a manual NetworkManager restart
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 succeeds, > and after restargin NetworkManager, when > "ping: 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 http://www-user.rhrk.uni-kl.de/~backes/ -- Logs begin at Wed 2016-03-30 14:05:49 CEST. -- Jul 06 16:16:08 eule audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 06 16:16:10 eule chronyd[912]: Selected source 87.106.126.46 Jul 06 16:16:14 eule audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-localed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 06 16:16:15 eule realmd[1707]: quitting realmd service after timeout Jul 06 16:16:15 eule realmd[1707]: stopping service Jul 06 16:16:23 eule blueman-mechanism[2564]: Exiting Jul 06 16:16:51 eule dbus-daemon[1809]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' Jul 06 16:16:51 eule systemd[1768]: Starting GNOME Terminal Server... Jul 06 16:16:51 eule dbus-daemon[1809]: Successfully activated service 'org.gnome.Terminal' Jul 06 16:16:51 eule systemd[1768]: Started GNOME Terminal Server. --Jul 06 16:18:07 eule sudo[2721]: backes : TTY=pts/1 ; PWD=/home/backes ; USER=root ; COMMAND=/sbin/service NetworkManager restart Jul 06 16:18:07 eule audit[2721]: USER_CMD pid=2721 uid=1000 auid=4294967295 ses=4294967295 msg='cwd="/home/backes" cmd=73657276696365204E6574776F726B4D616E616765722072657374617274 terminal=pts/1 res=success' Jul 06 16:18:07 eule audit[2721]: CRED_REFR pid=2721 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_env,pam_fprintd acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success' Jul 06 16:18:07 eule sudo[2721]: pam_systemd(sudo:session): Cannot create session: Already occupied by a session Jul 06 16:18:07 eule audit[2721]: USER_START pid=2721 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_open grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success' Jul 06 16:18:07 eule sudo[2721]: pam_unix(sudo:session): session opened for user root by (uid=0) Jul 06 16:18:07 eule polkitd[937]: Registered Authentication Agent for unix-process:2722:22771 (system bus name :1.75 [/usr/bin/pkttyagent --notify-fd 4 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.utf8) Jul 06 16:18:07 eule systemd[1]: Stopping Network Manager... Jul 06 16:18:07 eule NetworkManager[1191]: [1467814687.2564] caught SIGTERM, shutting down normally. Jul 06 16:18:07 eule NetworkManager[1191]: [1467814687.2578] device (virbr0-nic): released from master device virbr0 Jul 06 16:18:07 eule NetworkManager[1191]: [1467814687.2581] exiting (success) Jul 06 16:18:07 eule systemd[1]: Stopped Network Manager. Jul 06 16:18:07 eule audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 06 16:18:07 eule org.gnome.Shell.desktop[1545]: Gjs-Message: JS LOG: Removing a network device that was not added Jul 06 16:18:07 eule audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Jul 06 16:18:07 eule org.gnome.Shell.desktop[2059]: Gjs-Message: JS LOG: Removing a network device that was not added Jul 06 16:18:07 eule org.gnome.Shell.desktop[2059]: Gjs-Message: JS LOG: Removing a network device that was not added Jul 06 16:18:07 eule org.gnome.Shell.desktop[2059]: Gjs-Message: JS LOG: Removing a network device that was not added Jul 06 16:18:07 eule audit[2721]: USER_END pid=2721 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:session_close grantors=pam_keyinit,pam_limits,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success' Jul 06 16:18:07 eule audit[2721]: CRED_DISP pid=2721 uid=0 a
Re: Fedora 24: Network inoperable after a manual NetworkManager restart
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 succeeds, and after restargin NetworkManager, when "ping: 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 -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://lists.fedoraproject.org/admin/lists/users@lists.fedoraproject.org Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
