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

FoundationDB Source Code Shared

​Learn to use GitHub, ​GitHub Releases Atom 1.26

  • ​Learn to use GitHub with GitHub Learning Lab
    The most popular open-source development site in the world is GitHub. It's used by tens of millions of developers to work on over 80 million projects. It's not just a site where people use Linus Torvalds' Git open-source distributed version control system. It's also an online home for collaboration, a sandbox for testing, a launchpad for deployment, and a platform for learning new skills. The GitHub Training Team has now released an app, GitHub Learning Lab, so you can join the programming party. GitHub Learning Lab is not a tutorial or webcast. It's an app that gives you a hands-on learning experience within GitHub. According to GitHub, "Our friendly bot will take you through a series of practical, fun labs that will give you the skills you need in no time--and share helpful feedback along the way."
  • Atom 1.26
    Atom 1.26 has been released on our stable channel and includes GitHub package improvements, fuzzy-finder support for Teletype and file system watcher improvements.
  • Atom Hackable Text Editor Gets GitHub Package, Filesystem Watcher Improvements
    GitHub announced the release of the Atom 1.26 open-source and cross-platform hackable text editor for Linux, macOS, and Windows platforms with more improvements and bug fixes. In Atom 1.26, the GitHub package received various improvements and new features, among which we can mention the ability of the ’s Git pane to display a read-only list of recent commits for quick reference, and support for storing your GitHub username and password credentials in the Git authentication dialog.

Games Leftovers

Linux and Linux Foundation

  • V3D DRM Driver Steps Towards Mainline Kernel, Renamed From VC5
    The Broadcom VC5 driver stack is being renamed to V3D and developer Eric Anholt is looking at merging it into the mainline Linux kernel. The VC5 DRM/KMS and Mesa code has been for supporting the next-generation Broadcom VideoCore 5 graphics hardware that's only now beginning to appear in some devices, well, it seems one device so far. Though as I pointed out a few months back, there's already "VC6" activity going on too as the apparent successor to VC5 already being in development.
  • Azure Sphere Makes Microsoft an Arm Linux Player for IoT [Ed: Microsoft marketing at LF (only runs on/with Windows and Visual Studio etc.)]
  • Keynotes Announced for Automotive Linux Summit & OS Summit Japan [Ed: "Senior Software Engineer, Microsoft" in there; LF has once again let Microsoft infiltrate Linux events; in the words of Microsoft’s chief evangelist, “I’ve killed at least two Mac conferences. […] by injecting Microsoft content into the conference, the conference got shut down. The guy who ran it said, why am I doing this?”]
    Automotive Linux Summit connects those driving innovation in automotive Linux from the developer community with the vendors and users providing and using the code, in order to propel the future of embedded devices in the automotive arena.