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

Summary


In this chapter, we started to use some advanced Linux commands that we explored in Chapter 2, Troubleshooting Commands and Sources of Useful Information such as iostat and vmstat. We also became very familiar with a fundamental utility within Linux, the ps command, while troubleshooting a vague performance issue.

While in Chapter 3, Troubleshooting a Web Application we were able to follow the full troubleshooting process from Data Collection to Trial and Error, in this chapter, our actions were primarily focused on the Data Collection and Establishing a Hypothesis stages. It is quite common to find yourself only troubleshooting an issue and not performing corrective actions. There are many issues that should be resolved by a user of the system and not the systems administrator, but it is still the administrator's role to identify the source of the issue.

In Chapter 5, Network Troubleshooting we will be troubleshooting some very interesting network issues. Networking is critical to...