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

Open source software: The question of security

The logic is understandable - how can a software with source code that can easily be viewed, accessed and changed have even a modicum of security? opensource-security-question Open source software is safer than many believe. But with organizations around the globe deploying open source solutions in even some of the most mission-critical and security-sensitive environments, there is clearly something unaccounted for by that logic. According to a November 28 2013 Financial News article, some of the world's largest banks and exchanges, including Deutsche Bank and the New York Stock Exchange, have been active in open source projects and are operating their infrastructure on Linux, Apache and similar systems. Read more

Beer and open source with Untappd

Greg Avola loves beer and coding. He loves beer so much that he made an app, Untappd, where users track their favorite brews. He loves coding so much that he wrote a book about mobile web development. According to him, if it weren't for open source software, his app—and the projects of many other developers—simply wouldn't exist. Read more in my interview with Greg about his open source journey, his favorite beer, and why check-in apps are still relevant. Read more

What is Docker, Really? Founder Solomon Hykes Explains

Docker has quickly become one of the most popular open source projects in cloud computing. With millions of Docker Engine downloads, hundreds of meetup groups in 40 countries and dozens upon dozens of companies announcing Docker integration, it's no wonder the less-than-two-year-old project ranked No. 2 overall behind OpenStack in Linux.com and The New Stack's top open cloud project survey. This meteoric rise is still puzzling, and somewhat problematic, however, for Docker, which is “just trying to keep up” with all of the attention and contributions it's receiving, said founder Solomon Hykes in his keynote at LinuxCon and CloudOpen on Thursday. Most people today who are aware of Docker don't necessarily understand how it works or even why it exists, he said, because they haven't actually used it. “Docker is very popular, it became popular very fast, and we're not really sure why,” Hykes said. “My personal theory … is that it was in the right place at the right time for a trend that's much bigger than Docker, and that is very important for all of us, that has to do with how applications are built.” Read more