Hi and happy new year for everybody,

 

I'm having some trouble with the network going down recently.

My log is full of this kind of messages

 

Jan  5 15:12:57 Tower kernel: vethc78e917: renamed from eth0
Jan  5 15:12:57 Tower kernel: docker0: port 8(veth7321aac) entered disabled state
Jan  5 15:12:57 Tower kernel: docker0: port 8(veth7321aac) entered disabled state
Jan  5 15:12:57 Tower kernel: device veth7321aac left promiscuous mode
Jan  5 15:12:57 Tower kernel: docker0: port 8(veth7321aac) entered disabled state
Jan  5 15:13:04 Tower kernel: docker0: port 3(vethf8ae682) entered disabled state
Jan  5 15:13:04 Tower kernel: vethac1ba09: renamed from eth0
Jan  5 15:13:04 Tower kernel: docker0: port 3(vethf8ae682) entered disabled state
Jan  5 15:13:04 Tower kernel: device vethf8ae682 left promiscuous mode
Jan  5 15:13:04 Tower kernel: docker0: port 3(vethf8ae682) entered disabled state
Jan  5 15:15:54 Tower kernel: docker0: port 3(veth1d1b064) entered blocking state
Jan  5 15:15:54 Tower kernel: docker0: port 3(veth1d1b064) entered disabled state
Jan  5 15:15:54 Tower kernel: device veth1d1b064 entered promiscuous mode
Jan  5 15:15:54 Tower kernel: docker0: port 3(veth1d1b064) entered blocking state
Jan  5 15:15:54 Tower kernel: docker0: port 3(veth1d1b064) entered forwarding state
Jan  5 15:15:54 Tower kernel: docker0: port 3(veth1d1b064) entered disabled state
Jan  5 15:15:54 Tower kernel: eth0: renamed from vethae9317a
Jan  5 15:15:54 Tower kernel: docker0: port 3(veth1d1b064) entered blocking state
Jan  5 15:15:54 Tower kernel: docker0: port 3(veth1d1b064) entered forwarding state
Jan  5 15:16:44 Tower kernel: docker0: port 5(veth5be321d) entered blocking state
Jan  5 15:16:44 Tower kernel: docker0: port 5(veth5be321d) entered disabled state
Jan  5 15:16:44 Tower kernel: device veth5be321d entered promiscuous mode
Jan  5 15:16:44 Tower kernel: docker0: port 5(veth5be321d) entered blocking state
Jan  5 15:16:44 Tower kernel: docker0: port 5(veth5be321d) entered forwarding state
Jan  5 15:16:44 Tower kernel: docker0: port 5(veth5be321d) entered disabled state
Jan  5 15:16:44 Tower kernel: eth0: renamed from veth6993235

Is it normal?

I can't figure out what exactly put the network down. If I unplug the cable and plug it back it works again for some time.

Any help is appreciated.

 

Thank you.

tower-diagnostics-20180105-1521.zip

Networking issues like this are somethings difficult to fix.  I would suggest that you reboot your router and all of your switches.  These devices all employ some sort of computer chip to do their thing and they do get 'confused' at times.

 

(A quick personal experience.  On Dec 30th, when I got up, I discovered first that I had lost my internet connection for my PC. Further investigation disclosed that I had also lost the connection to everything else in the house including my unRAID servers.  Following my earlier advice, I rebooted all of the network devices--- No luck.  Several hours later, I had taken to isolating the network into segments and disconnecting virtually everything on the network and isolated the problem.  I found that power cycling a network-connected printer and leaving the home theater disconnected from the network, all was well.  Investigating the home theater much later, I found out that the BluRay player would not turn on.  Power cycling it fixed that situation and also corrected the issues on that branch of the network.  Later, I found out that both of my unRAID servers had had a "Trace Call" within a few seconds of each other during the night.  I can only surmise that there was some sort of a power anomaly about that time.)