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

An update on Plasma Addons

Since my last blog post on plasma addons there has been a lot of activity, existing contributors are active on their own plasmoids, and there are many new faces coming on to take up the challenge of maintaining their own small part of Plasma. Read more

Motorola frenzy with up to 9 devices possibly launching at ‘Moto Launch Exprience’

We have seen a number of sources revealing upcoming releases and device-launches set for September. However today, we are hearing seriously scary reports that Motorola are set to release EIGHT devices before Christmas. Yes folks, Motorola are about to get extremely serious in terms of the market releasing no less than eight devices over the next few months. Read more

Most popular open-source cloud projects of 2014

At CloudOpen, a Linux Foundation tradeshow held in conjunction with LinuxCon, the Foundation announced that an online survey of open-source cloud professionals found OpenStack to be the most popular overall project. Read more

Walmart's investment in open source isn't cheap

This is not done for the love of humanity. Walmart takes the effort to work in the open because there is a return to be had from that investment. When other companies adopt Hapi, Walmart expects their internal implementations will lead them to improve the code to better suit their needs. Since the majority of these improvements are likely to be integral to the code in the commons, any rational actor will make pull requests attempting to have their work integrated in the project trunk. Of course -- otherwise, the team making the changes would be eternally burdened with the need to refactor and test their changes each time the trunk is updated. Successful pull requests lead to merges that bring the whole community together for the upkeep of the code, not just the developers who originally wrote it. Read more