Language Selection

English French German Italian Portuguese Spanish

Best Practices for Diagnosing Linux Problems

Filed under
Linux
HowTos

1.1 Introduction

Your boss is screaming, your customers are screaming, you’re screaming ... Whatever the situation, there is a problem, and you need to solve it. Remember those old classic MUD games? For those who don’t, a Multi-User Dungeon or MUD was the earliest incarnation of the online video game. Users played the game through a completely non-graphical text interface that described the surroundings and options available to the player and then prompted the user with what to do next.


You are alone in a dark cubicle. To the North is your boss’s office, to the West is your Team Lead’s cubicle, to the East is a window opening out to a five-floor drop, and to the South is a kitchenette containing a freshly brewed pot of coffee. You stare at your computer screen in bewilderment as the phone rings for the fifth time in as many minutes indicating that your users are unable to connect to their server.

Command>

What will you do? Will you run toward the East and dive through the open window? Will you go grab a hot cup of coffee to ensure you stay alert for the long night ahead? A common thing to do in these MUD games was to examine your surroundings further, usually done by the look command.


Command> look

Your cubicle is a mess of papers and old coffee cups. The message waiting light on your phone is burnt out from flashing for so many months. Your email inbox is overflowing with unanswered emails. On top of the mess is the brand new book you ordered entitled "Self-Service Linux." You need a shower.


Command> read book "Self-Service Linux"

You still need a shower.

This tongue-in-cheek MUD analogy aside, what can this book really do for you? This book includes chapters that are loaded with useful information to help you diagnose problems quickly and effectively. This first chapter covers best practices for problem determination and points to the more in-depth information found in the chapters throughout this book. The first step is to ensure that your Linux system(s) are configured for effective problem determination.

Full Article.

More in Tux Machines

Oracle VirtualBox Updates to run on Linux 4.0 Kernel

The open-source VirtualBox virtualization project is out with its 4.3.24 update today providing a number of important updates and bug fixes. Read more

Qbo Is an AI-Driven Ubuntu-Powered Cute Little Robot - Video

We've seen some interesting devices coming out of the Mobile World Congress in Barcelona and the small Ubuntu-powered Qbo robot is just one them. Linux fans already kind of knew what to expected to see in Barcelona. Many Ubuntu fans were looking to check out the first Meizu MX4 Ubuntu Edition phone and their curiosity was satisfied, but now we have something that it's equally interesting, and that is a small robot. Read more

Ubuntu MATE Is One of the Last Major Distros to Officially Support PowerPC

Ubuntu MATE has been providing PowerPC support for some time now, but the developers have made some serious improvements to this particular feature in the latest 15.04 Beta 1 update. Read more

​No reboot patching comes to Linux 4.0

One reason to love Linux on your servers or in your data-center is that you so seldom needed to reboot it. True, critical patches require a reboot, but you could go months without rebooting. Now, with the latest changes to the Linux kernel you may be able to go years between reboots. Read more