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

  • Virtualbox Error Cannot register the hard disk because a hard disk with UUID already exists solution
  • kernel: [549267.368859] mate-terminal[7871]: segfault at 2000000101 ip 00007f5d0a9548f0 sp 00007fff7012c610 error 4 in libgobject-2.0.so.0.4800.2[7f5d0a920000+52000]
  • apcupsd how to setup and monitor APC UPS units
  • How To Password Reset, Recover, Bypass, Remove and Unlock on Windows 10,8,7,Vista,XP,NT,2000,2003,2008,2012,2016,2019 Administrative Login Programs
  • Nvidia Ubuntu Linux Screentearing Video with solution driver
  • ?? Question Marks for time, permissions and size of a file?
  • mdadm how to stop a check
  • access denied by acl file qemu-kvm: bridge helper failed
  • Linux NIC connecting at 100M instead of 1000M gigabit speeds? It could be overheating
  • "This kernel requires the following features not present on the CPU: cmov Unable to boot - please use a kernel appropriate for your CPU.
  • http://vault.centos.org/5.9/os/i386/repodata/filelists.xml.gz: [Errno -1] Metadata file does not match checksum solution
  • Linux Ubuntu Wifi Disabled Only Works When Laptop Plugged Into Wall AC Power
  • CentOS 6 impossible to compile a newer libguestfs
  • chroot
  • How To Get Started on Ubuntu with gpt-2 OpenAI Text Prediction
  • Remove cloud-init in your VM
  • QEMU-KVM KVM Command Line Practical Guide
  • Linux How To Change NIC Name to eth0 instead of enps33 or enp0s25
  • virt-resize: error: libguestfs error: could not create appliance through libvirt.
  • Asterisk Does Not Retry When Authentication Fails