Is your NIC really down and really dying? r8169: eth0: link up r8169: eth0: link down NetworkManager: (eth0): carrier now OFF (device state 1)

Apr 30 17:07:07 localhost kernel: [12265558.582378] r8169: eth0: link up
Apr 30 17:07:07 localhost NetworkManager: (eth0): carrier now ON (device state 1)
Apr 30 17:07:08 localhost kernel: [12265559.237961] r8169: eth0: link down
Apr 30 17:07:08 localhost NetworkManager: (eth0): carrier now OFF (device state 1)
Apr 30 17:07:11 localhost NetworkManager: (eth0): carrier now ON (device state 1)
Apr 30 17:07:11 localhost kernel: [12265562.162804] r8169: eth0: link up
Apr 30 17:07:11 localhost kernel: [12265562.577849] r8169: eth0: link down
Apr 30 17:07:12 localhost NetworkManager: (eth0): carrier now OFF (device state 1)
Apr 30 17:07:14 localhost kernel: [12265565.312582] r8169: eth0: link up
Apr 30 17:07:14 localhost NetworkManager: (eth0): carrier now ON (device state 1)

Apr 30 17:09:10 localhost kernel: [12265681.639307] r8169: eth0: link down
Apr 30 17:09:13 localhost kernel: [12265684.402984] r8169: eth0: link up
Apr 30 17:09:14 localhost kernel: [12265685.660805] r8169: eth0: link down
Apr 30 17:09:18 localhost kernel: [12265688.942400] r8169: eth0: link up
Apr 30 17:09:18 localhost kernel: [12265689.826486] r8169: eth0: link down
Apr 30 17:09:21 localhost kernel: [12265692.512789] r8169: eth0: link up
Apr 30 17:09:22 localhost kernel: [12265693.134914] r8169: eth0: link down
Apr 30 17:09:31 localhost kernel: [12265702.700430] r8169: eth0: link up
Apr 30 17:09:34 localhost kernel: [12265705.571668] r8169: eth0: link down
Apr 30 17:09:37 localhost kernel: [12265708.281532] r8169: eth0: link up

I was getting frustrated by when I checked the Cat5 cable it was a little bit loose on the NIC. This is a case where any tug somewhere on the line knocked it loose.

So I would double check with your datacenter or if you can, physically check the server yourself to see if the NIC's RJ45 cable is actually plugged in snugly and fully seated.


Tags:

nic, eth, networkmanager, carrier, apr, localhost, kernel, info, frustrated, tug, datacenter, server, rj, plugged, snugly, seated,

Latest Articles

  • Linux ln symlink how to update existing symbolic link
  • Ubuntu 18.04 / Linux Mint 19.1 Cannot Type or Login - solution
  • LUKS Hard Drive Encryption on Linux Mint Ubuntu Debian etc how to mount encrypted hard drive
  • How to use nmap locate other machines/computers/servers on your network using nmap
  • Linux Mint 18.2 Create Config File To Start Application Upon Login
  • Dell Wyse Thin Client BIOS Access Key
  • sudoers file in /etc warning about comments/includes!
  • Centos 7 Reallocate logical volume space to another
  • lvm how to reduce volume size
  • letsencrypt certbot error "Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80."
  • SSH error cannot Forward or Listen "bind: Cannot assign requested address"
  • X11 SSH Linux Forwarding Error
  • Using Microsoft's Group Policy Management Editor (GPME) To Change Default Permissions and Internet Explorer Security Settings
  • Thunderbird How To Disable An Email Account
  • iptables linux firewall recommended rules for public computing
  • LVM How To Create Pool (dynamically allocated and not fully allocated)
  • VMWare Pro Workstation Nic Disconnected and No IP Using NAT
  • Linux How To Create A RamDisk
  • mdadm force resync when resync=PENDING solution
  • Proxmox Breaks Storage/LVM Backing If Killing QEMU-IMG