Book Image

Red Hat Enterprise Linux Troubleshooting Guide

By : Benjamin Cane
Book Image

Red Hat Enterprise Linux Troubleshooting Guide

By: Benjamin Cane

Overview of this book

Red Hat Enterprise Linux is an operating system that allows you to modernize your infrastructure, boost efficiency through virtualization, and finally prepare your data center for an open, hybrid cloud IT architecture. It provides the stability to take on today's challenges and the flexibility to adapt to tomorrow's demands. In this book, you begin with simple troubleshooting best practices and get an overview of the Linux commands used for troubleshooting. The book will cover the troubleshooting methods for web applications and services such as Apache and MySQL. Then, you will learn to identify system performance bottlenecks and troubleshoot network issues; all while learning about vital troubleshooting steps such as understanding the problem statement, establishing a hypothesis, and understanding trial, error, and documentation. Next, the book will show you how to capture and analyze network traffic, use advanced system troubleshooting tools such as strace, tcpdump & dmesg, and discover common issues with system defaults. Finally, the book will take you through a detailed root cause analysis of an unexpected reboot where you will learn to recover a downed system.
Table of Contents (19 chapters)
Red Hat Enterprise Linux Troubleshooting Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Déjà vu


In Chapter 5, Network Troubleshooting, our troubleshooting started after a developer called in and reported that the company's blog was reporting a database connectivity error. After troubleshooting, we found that this error was due to a misconfigured static route on the database server. Yet again, today (several days later), we receive a call from the same developer reporting the same issue.

When the developer goes to http://blog.example.com, he receives an error stating there is a database connectivity issue. Not again!

Since the first step in data collection is to duplicate the issue, the first thing we should do is to pull up the company blog on our own browser.

It seems, in fact, that the same error is showing yet again; now to figure out why.