Whenever there's a network outage, the machine loses access to the network, and it doesn't get back onto the network when the network outage is resolved. When this happens, you can't ping it, but it's not frozen. Subsequently, approximately once per day, it's able to access the network again during a brief window. I know this because the computer sends me emails during this window. I wanted to try to ping it during one of these windows, but I wasn't able to try that before it was rebooted.
Rebooting always fixes the problem until the next network outage. None of the other Linux boxes on the same LAN have this problem, but I note that this is one of a select few with a static IP address. Almost all of the others use DHCP.
My sys admin seems convinced that it's hardware-related, either a problem with the Ethernet jack in the wall, some patch cable, or the computer itself. I just don't see how that is consistent with the evidence though. I think it's some kind of configuration issue. I would like some additional opinions.
Here's the output of `ifconfig -a` (some values redacted for security reasons):
Code: Select all
enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 1xx.xxx.53.160 netmask 255.255.255.255 broadcast 1xx.xxx.53.160
inet6 fe80::xxxx:xxxx:xxxx:509b prefixlen 64 scopeid 0x20<link>
ether b8:xx:xx:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 122001 bytes 40089765 (38.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 73284 bytes 12721881 (12.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xfb200000-fb220000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 406 bytes 26212 (25.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 406 bytes 26212 (25.5 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.122.1 netmask 255.255.255.0 broadcast 192.168.122.255
ether 52:xx:xx:xx:xx:47 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
virbr0-nic: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 52:xx:xx:xx:xx:47 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Code: Select all
GENERAL.DEVICE: enp0s25
GENERAL.TYPE: ethernet
GENERAL.HWADDR: b8:xx:xx:xx:xx:xx
GENERAL.MTU: 1500
GENERAL.STATE: 100 (connected)
GENERAL.CONNECTION: Wired connection 1
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.CARRIER: on
IP4.ADDRESS[1]: 1xx.xxx.53.160/32
IP4.GATEWAY: 1xx.xxx.52.1
IP4.ROUTE[1]: dst = 1xx.xxx.53.160/32, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]: dst = 1xx.xxx.52.1/32, nh = 0.0.0.0, mt = 100
IP4.ROUTE[3]: dst = 0.0.0.0/0, nh = 1xx.xxx.52.1, mt = 100
IP4.DNS[1]: 1xx.xxx.10.134
IP4.DNS[2]: 1xx.xxx.50.17
IP6.ADDRESS[1]: fe80::xxxx:xxxx:xxxx:509b/64
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = ff00::/8, nh = ::, mt = 256, table=255
IP6.ROUTE[2]: dst = fe80::/64, nh = ::, mt = 256
GENERAL.DEVICE: virbr0
GENERAL.TYPE: bridge
GENERAL.HWADDR: 52:xx:xx:xx:xx:47
GENERAL.MTU: 1500
GENERAL.STATE: 100 (connected)
GENERAL.CONNECTION: virbr0
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/2
IP4.ADDRESS[1]: 192.168.122.1/24
IP4.GATEWAY: --
IP4.ROUTE[1]: dst = 192.168.122.0/24, nh = 0.0.0.0, mt = 0
IP6.GATEWAY: --
GENERAL.DEVICE: lo
GENERAL.TYPE: loopback
GENERAL.HWADDR: 00:00:00:00:00:00
GENERAL.MTU: 65536
GENERAL.STATE: 10 (unmanaged)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
IP4.ADDRESS[1]: 127.0.0.1/8
IP4.GATEWAY: --
IP6.ADDRESS[1]: ::1/128
IP6.GATEWAY: --
GENERAL.DEVICE: virbr0-nic
GENERAL.TYPE: tun
GENERAL.HWADDR: 52:xx:xx:xx:xx:47
GENERAL.MTU: 1500
GENERAL.STATE: 10 (unmanaged)
Thanks!