Why does my network cut out every 10-15 minutes?

[HALPtech]

I've been experiencing some issues with my Unraid rig losing its network connection every so often. It happens briefly, and when it does, I usually can't connect to the web interface and any streaming freezes until it comes back up.

 

Note: I've noticed this only happens when an application on it is being actively used. It doesn't happen overnight when everything is quiet.

 

Here are the relevant logs (with diagnostics attached) - I'm not sure what promiscuous mode is, but I can see that something is happening to my network device (eth0) during these times:

 

Jul 22 08:00:29 unraid kernel: device eth0 left promiscuous mode
Jul 22 08:00:29 unraid kernel: bond0: now running without any active interface!
Jul 22 08:00:29 unraid kernel: br0: port 1(bond0) entered disabled state
Jul 22 08:00:32 unraid ntpd[1770]: Deleting interface #228 br0, 192.168.121.12#123, interface stats: received=9, sent=9, dropped=0, active_time=56 secs
Jul 22 08:00:32 unraid ntpd[1770]: 216.239.35.0 local addr 192.168.121.12 -> <null>
Jul 22 08:00:32 unraid ntpd[1770]: 216.239.35.4 local addr 192.168.121.12 -> <null>
Jul 22 08:00:32 unraid ntpd[1770]: 216.239.35.8 local addr 192.168.121.12 -> <null>
Jul 22 08:00:32 unraid ntpd[1770]: 216.239.35.12 local addr 192.168.121.12 -> <null>
Jul 22 08:00:44 unraid kernel: r8169 0000:04:00.0 eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jul 22 08:00:44 unraid kernel: bond0: (slave eth0): link status definitely up, 100 Mbps full duplex
Jul 22 08:00:44 unraid kernel: bond0: (slave eth0): making interface the new active one
Jul 22 08:00:44 unraid kernel: device eth0 entered promiscuous mode
Jul 22 08:00:44 unraid kernel: bond0: active interface up!
Jul 22 08:00:44 unraid kernel: br0: port 1(bond0) entered blocking state
Jul 22 08:00:44 unraid kernel: br0: port 1(bond0) entered forwarding state
Jul 22 08:00:46 unraid ntpd[1770]: Listen normally on 229 br0 192.168.121.12:123
Jul 22 08:00:46 unraid ntpd[1770]: new interface(s) found: waking up resolver
Jul 22 08:07:04 unraid emhttpd: read SMART /dev/sdf
Jul 22 08:07:14 unraid emhttpd: read SMART /dev/sdd
Jul 22 08:07:14 unraid emhttpd: read SMART /dev/sdc
Jul 22 08:13:22 unraid kernel: r8169 0000:04:00.0 eth0: Link is Down
Jul 22 08:13:22 unraid kernel: bond0: (slave eth0): link status definitely down, disabling slave
Jul 22 08:13:22 unraid kernel: device eth0 left promiscuous mode
Jul 22 08:13:22 unraid kernel: bond0: now running without any active interface!
Jul 22 08:13:22 unraid kernel: br0: port 1(bond0) entered disabled state
Jul 22 08:13:25 unraid ntpd[1770]: Deleting interface #229 br0, 192.168.121.12#123, interface stats: received=28, sent=28, dropped=0, active_time=759 secs
Jul 22 08:13:25 unraid ntpd[1770]: 216.239.35.0 local addr 192.168.121.12 -> <null>
Jul 22 08:13:25 unraid ntpd[1770]: 216.239.35.4 local addr 192.168.121.12 -> <null>
Jul 22 08:13:25 unraid ntpd[1770]: 216.239.35.8 local addr 192.168.121.12 -> <null>
Jul 22 08:13:25 unraid ntpd[1770]: 216.239.35.12 local addr 192.168.121.12 -> <null>
Jul 22 08:13:36 unraid kernel: r8169 0000:04:00.0 eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Jul 22 08:13:37 unraid kernel: bond0: (slave eth0): link status definitely up, 100 Mbps full duplex
Jul 22 08:13:37 unraid kernel: bond0: (slave eth0): making interface the new active one
Jul 22 08:13:37 unraid kernel: device eth0 entered promiscuous mode
Jul 22 08:13:37 unraid kernel: bond0: active interface up!
Jul 22 08:13:37 unraid kernel: br0: port 1(bond0) entered blocking state
Jul 22 08:13:37 unraid kernel: br0: port 1(bond0) entered forwarding state
Jul 22 08:13:38 unraid ntpd[1770]: Listen normally on 230 br0 192.168.121.12:123
Jul 22 08:13:38 unraid ntpd[1770]: new interface(s) found: waking up resolver

 

unraid-diagnostics-20210722-0818.zip

Edited July 22, 2021 by HALPtech

[HALPtech]

For anyone who stumbles upon this topic - changing the ethernet cable (assuming it was faulty) and disabling network bonding (I only have one interface) seems to have done the trick. I'll update if I notice it happening again.