automatically restart ethernet ?

[sean darcy]

On F25, a server keeps losing its internet connection. I've now added a 
cron.hourly script to restart NetworkManager. Is there a better way ? 
Some way to tell NetworkManager that if the connection goes down, it 
should try to bring it up every ___ seconds ?

sean

[fred roller]

Look into "heartbeat".  It keeps in touch with another server and if the
connection is lost you can define action i.e. restart network.

On Sat, Feb 25, 2017 at 10:53 AM, sean darcy <seandarcy2(a)gmail.com&gt; wrote:

>  On F25, a server keeps losing its internet connection. I've now
> added a
>  cron.hourly script to restart NetworkManager. Is there a better way ? Some
>  way to tell NetworkManager that if the connection goes down, it should try
>  to bring it up every ___ seconds ?
>
>  sean
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>

[Greg Woods]

On Sat, Feb 25, 2017 at 11:39 AM, fred roller <fredroller66(a)gmail.com&gt;
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