Jump to content

eth0 goes down, then comes back up?


coppit

Recommended Posts

unRAID OS Version: 6.0-rc3

 

Description: I was ssh'd in to my box, working on some docker containers, and I lost my ssh session. After a few seconds I was able to ssh back in. An hour ago I had my docker img fill up, crashing some containers. Perhaps that's related? In the past I've had a putty window open for days on end without any problems. So that makes a failing NIC less likely.

 

How to reproduce: Sorry, I don't know.

 

Expected results: Solid ssh connection.

 

Actual results: NIC goes down for a few seconds, then comes back up.

 

Other information: Portion of syslog below.

 

Jun  2 22:47:10 storage kernel: eth0: renamed from veth4e9704c
Jun  2 22:47:10 storage kernel: docker0: port 2(vethd3bf89e) entered forwarding state
Jun  2 22:47:10 storage kernel: docker0: port 2(vethd3bf89e) entered forwarding state
Jun  2 22:47:25 storage kernel: docker0: port 2(vethd3bf89e) entered forwarding state
Jun  2 23:14:47 storage kernel: docker0: port 2(vethd3bf89e) entered disabled state
Jun  2 23:14:47 storage avahi-daemon[27338]: Withdrawing workstation service for vethd3bf89e.
Jun  2 23:14:47 storage kernel: device vethd3bf89e left promiscuous mode
Jun  2 23:14:47 storage kernel: docker0: port 2(vethd3bf89e) entered disabled state
Jun  2 23:15:08 storage kernel: device veth303f455 entered promiscuous mode
Jun  2 23:15:08 storage avahi-daemon[27338]: Withdrawing workstation service for veth1271cba.
Jun  2 23:15:08 storage kernel: eth0: renamed from veth1271cba
Jun  2 23:15:08 storage kernel: docker0: port 2(veth303f455) entered forwarding state
Jun  2 23:15:08 storage kernel: docker0: port 2(veth303f455) entered forwarding state
Jun  2 23:15:23 storage kernel: docker0: port 2(veth303f455) entered forwarding state
Jun  2 23:32:26 storage kernel: tg3 0000:05:00.0 eth0: Link is down
Jun  2 23:32:26 storage kernel: br0: port 1(eth0) entered disabled state
Jun  2 23:32:29 storage kernel: tg3 0000:05:00.0 eth0: Link is up at 1000 Mbps, full duplex
Jun  2 23:32:29 storage kernel: tg3 0000:05:00.0 eth0: Flow control is on for TX and on for RX
Jun  2 23:32:29 storage kernel: tg3 0000:05:00.0 eth0: EEE is disabled
Jun  2 23:32:29 storage kernel: br0: port 1(eth0) entered listening state
Jun  2 23:32:29 storage kernel: br0: port 1(eth0) entered listening state
Jun  2 23:32:44 storage kernel: br0: port 1(eth0) entered learning state
Jun  2 23:33:00 storage kernel: br0: topology change detected, propagating
Jun  2 23:33:00 storage kernel: br0: port 1(eth0) entered forwarding state
Jun  2 23:33:14 storage sshd[3017]: Accepted password for root from 192.168.1.2 port 54393 ssh2

Link to comment

It's extremely difficult for me to see this as anything but a normal network issue.  The syslog clearly shows tg3 reporting the loss of the link to the outside world, then regaining it 3 seconds later.  The link is the negotiated link between the NIC and the other end of the connected cable.  There's no evidence of a failing NIC at all, or one that's been reset.

 

I would do the normal network tests, check for a router reboot, a loose connection somewhere, interference on a network cable somewhere.  Try the ifconfig command, and look for errors, drops, and collisions.

Link to comment
  • 11 months later...

Did you ever find a fix for this? I am experiencing this over and over on my box. The link lights never dropped even put a camera on it watching them

This is an old report on a version of unRAID that I hope you aren't running, it also only contained a snippet from the log file.

 

I don't think an solution was found. What would be helpful is if you could post your diagnostic file so that we can look at more of the logs and see what is going on. 

Link to comment
  • 2 weeks later...

It seems to have stabilized. I'm running 6.1.9 now. It may have stabilized in an earlier version.

 

My machine is plugged into an enterprise-grade 16-port switch that has been solid for years now, so I doubt that it's a problem there. I'm guessing some sort of hardware+kernel issue that has since resolved itself.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...