Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Red Hat Enterprise Linux Troubleshooting Guide

You're reading from   Red Hat Enterprise Linux Troubleshooting Guide Identify, capture and resolve common issues faced by Red Hat Enterprise Linux administrators using best practices and advanced troubleshooting techniques

Arrow left icon
Product type Paperback
Published in Oct 2015
Publisher
ISBN-13 9781785283550
Length 458 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Benjamin Cane Benjamin Cane
Author Profile Icon Benjamin Cane
Benjamin Cane
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Troubleshooting Best Practices 2. Troubleshooting Commands and Sources of Useful Information FREE CHAPTER 3. Troubleshooting a Web Application 4. Troubleshooting Performance Issues 5. Network Troubleshooting 6. Diagnosing and Correcting Firewall Issues 7. Filesystem Errors and Recovery 8. Hardware Troubleshooting 9. Using System Tools to Troubleshoot Applications 10. Understanding Linux User and Kernel Limits 11. Recovering from Common Failures 12. Root Cause Analysis of an Unexpected Reboot Index

Hypothesis


Now that we understand how packets to 192.168.33.11 are routed, we should adjust our previous hypothesis to reflect that the route of 192.168.33.11 to enp0s3 is not correct and is causing our issue.

Essentially, what is happening (and we see this via tcpdump) is that, when the database server (192.168.33.12) receives a network packet from the blog server (192.168.33.11), it arrives on the enp0s8 device. However, when the database server is sending reply packets (SYN-ACK) to the web application server, the packets are being sent out via the enp0s3 interface.

Since the enp0s3 device is connected to the 10.0.2.0/24 network, it seems that the packet is being rejected (RESET) by another system or device on the 10.0.2.0/24 network. Most likely, this is due to the fact that this is a prime example of asynchronous routing.

Asynchronous routing is where a packet arrives on one interface but is replied to on another. In most network configurations, this is denied by default, but in some cases...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime