Search icon CANCEL
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 FREE CHAPTER 2. Troubleshooting Commands and Sources of Useful Information 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

The reported problem

Today's chapter, much like the other chapters, will start with someone reporting an issue. The issue being reported is that Apache is no longer running on the server, which serves the company's blog: blog.example.com.

A fellow systems administrator who is reporting the issue has explained that someone reported that the blog was down and when he logged into the server he could see Apache was no longer running. At that point, our peer was unsure what to do to continue and asked for our help.

Is Apache really down?

The first thing that we should do when a service is reported as down is to validate that it really is down. This is essentially our duplicate it for ourselves step from our troubleshooting process. With a service such as Apache, we should also validate that it is in fact down fairly quickly.

In my experience, I have often been told that a service is down when it really was not. The server may have been having an issue but it was not technically down....

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