Troubleshooting from historic issues
The first instinct for a Data Collector would be to simply run through the same troubleshooting steps from Chapter 5, Network Troubleshooting. The Adaptor and Educated Gusser troubleshooters, however, knowing the issue a few days ago was due to a static route would simply log in to the database server first and check for the same static route.
Maybe someone simply re-added it by mistake, or the route was not fully removed from the system's configuration files:
[db]# ip route show default via 10.0.2.2 dev enp0s3 proto static metric 1024 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 169.254.0.0/16 dev enp0s8 scope link metric 1003 192.168.33.0/24 dev enp0s8 proto kernel scope link src 192.168.33.12 ...
Get Red Hat Enterprise Linux Troubleshooting Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
