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
About the Author
About the Reviewers

Preventing reoccurrence

Since we feel pretty confident about our hypothesis as to what happened, we now can move on to the final step of our root cause analysis; preventing the issue from reoccurring.

As we discussed in the beginning of our chapter, all useful root cause analysis reports include a plan of action. Sometimes, this plan of action is something to be performed immediately at the time of the issue. Sometimes, this plan is to be performed later as a long-term resolution.

For our issue, we are going to have both, immediate actions and long-term actions.

Immediate action

The first immediate action we need to take is to ensure that the systems primary function is healthy. In this case, the server's primary function is to serve the company's blog.

This is easy enough to check by going to the blog address in a browser. We can see from the preceding screenshot that the blog is working as expected. Just to be sure, we can validate that the Apache service is running as well:

# systemctl status...