From: Greg Woods [mailto:woods@ucar.edu]
Sent: zaterdag 25 februari 2017 20:45
To: Community support for Fedora users
Subject: Re: automatically restart ethernet ?
On Sat, Feb 25, 2017 at 11:39 AM, fred roller <fredroller66@gmail.com> wrote:
Look into "heartbeat".
"heartbeat" has been deprecated for several years now and is no longer supported. There are no longer heartbeat packages in the F25 repos. The supported way to do HA on Linux is now corosync with pacemaker. But this is a pretty big thing to swallow just for
restarting a net connection. You might want to try a script that you can run more often than hourly that first checks to see if the net is up (maybe with a ping to your default gateway?), and only restarts NetworkManager if it's not. There are also other monitoring
applications such as "monit", but that's a pretty complex beast as well.
I presume you've looked into why your server keeps losing the net connection? That could be a bad cable, a bad switch port, or a bad NIC. Hardware issues tend to get worse over time; if that's what it is, even a cron kludge may eventually
not work any more.
--Greg
Pinging a local machine should tell you when machines become unreachable, probably because of a network failure.
But, as said before, it only treat consequences, not the real cause. Perhaps you should focus on that.
Why does restarting NM help? To bring the interface up again? Did it loose its IP-address for some reason? Duplications?
Did you consider / try a fixed IP-address?
Hans