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

CuBox-i4Pro Review

A bundled microSD card arrives preinserted into the rear of the CuBox-i, and it’s loaded with a version of Google’s Android operating system. Interestingly, SolidRun has gone to the effort of seeking the certifications required to load the Google Apps suite onto the card, meaning users receive Google Mail, YouTube, Google Maps and full access to Google Play straight out of the box. An even newer build, based on the latest Android 4.4 KitKat branch, can be downloaded from SolidRun’s website and provides an entirely useable desktop Android experience. Read more

Working on 3.19 – the kernel column

Linus Torvalds announced the release of Linux kernel version 3.18 in time for the holidays. In his mail, Linus noted that the previous RC, release candidate 7, had been “tiny” (in terms of changes and bugfixes), so it was time to get the final release out. The latest kernel includes support for storing AMD Radeon GPU buffers in regular application memory (building upon similar work done by Intel for kernel 3.16), and overlayfs (which we have covered previously), amongst a number of other less interesting new features. A full summary is provided at Kernel Newbies. Read more

The top 10 rookie open source projects

Open source has become the industry's engine of innovation. This year, for example, growth in projects related to Docker containerization trumped every other rookie area -- and not coincidentally reflected the most exciting area of enterprise technology overall. At the very least, the projects described here provide a window on what the global open source developer community is thinking, which is fast becoming a good indicator of where we're headed. Read more

First thoughts on KaOS 2014.12

The latest snapshot of this rolling release distribution includes initial support for UEFI, the KDE 4.14 desktop, systemd version 218 and the Qupzilla web browser. I mention Qupzilla because I feel it is a rare gem in the open source world, a quick capable browser that perhaps does not get the attention it deserves. KaOS is available in just one edition, a 64-bit x86 build. The ISO we download for KaOS is 1.6GB in size. Read more