On Thu, 5 Jan 2017 15:55:29 -0700 stan <stanl-fedorauser@xxxxxxxxxxx> wrote: > I've started to have a problem sometime within the last month, where > on boot I get a message that the ethernet link is up, but when I try > to use it, sometimes it can't be accessed. Update - Using Joe and Samuel's suggestions, I booted rawhide and found that it did not have the problem. I then looked at journalctl -b to see how the network aspects of boot differed from f25. I found that there was an extra stop and start of NetworkManager. This triggered my memory, and I remembered that a long time ago (on different hardware) I had a problem with NetworkManager and created an rc.local file in /etc/rc.d with the command systemd restart NetworkManager in it to solve a similar problem. This was in the rawhide system (it has been rawhide for quite some time, just continuously bypassing release status). I moved it over to the F25 system, and voila, the problem went away. The F25 system was installed using BFO when it was still rawhide, and I didn't completely copy all the little fixes and tweaks I usually do. It's strange that NetworkManager would suddenly start having a problem, but it is probably another component change that led to a race, that NetworkManager loses. Another anomaly is that I tried a systemctl restart NetworkManager as root to fix the issue when it happened on the F25 system. And it didn't work. I stopped it, and started it, too. Also failed. The journalctl -b on F25 seemed to show that the network was successfully started, even though NetworkManager considered it unavailable. If I feel ambitious, I'll remove the workaround and try to trace the problem to its source. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
