Home > Store

Troubleshooting Ruby Processes: Leveraging System Tools when the Usual Ruby Tricks Stop Working (Digital Short Cut)

Register your product to gain access to bonus material or receive a coupon.

Troubleshooting Ruby Processes: Leveraging System Tools when the Usual Ruby Tricks Stop Working (Digital Short Cut)

eBook (Watermarked)

  • Your Price: $11.04
  • List Price: $12.99
  • About Watermarked eBooks
  • This PDF will be accessible from your Account page after purchase and requires the free Adobe® Reader® software to read it.

    The eBook requires no passwords or activation to read. We customize your eBook by discreetly watermarking it with your name, making it uniquely yours.

    Watermarked eBook FAQ


  • Copyright 2008
  • Edition: 1st
  • eBook (Watermarked)
  • ISBN-10: 0-321-54468-4
  • ISBN-13: 978-0-321-54468-1

This short cut introduces key system diagnostic tools to Ruby developers creating and deploying web applications. When programmers develop a Ruby application they commonly experience complex problems which require some understanding of the underlying operating system to be solved. Difficult to diagnose, these problems can make the difference between a project's failure or success. This short cut demonstrates how to leverage system tools available on Mac OS X, Linux, Solaris, BSD or any other Unix flavor. You will learn how to leverage the raw power of tools such as lsof, strace or gdb to resolve problems that are difficult to diagnose with the standard Ruby development tools. You will also find concrete examples that illustrate how these tools solve real-life problems in Ruby development. This expertise will prove especially relevant during the deployment phase of your application. In this way, should your production Mongrel cluster freeze and stop serving HTTP requests, it will not take you 2 days to figure out why!

Sample Content


Download the excerpt

Table of Contents

What This Shortcut Covers

Ruby Troubleshooting: The Usual Suspects

    raise, puts and debug()

    irb or script/console

    Writing a Test

    Log Files

    Sending Signals

    Debugger and Breakpointer


    What is It?


        Typical Usage Scenarios

        Combining Multiple Selections

    Concrete Examples Using lsof to Troubleshoot a Problem with a Ruby Process

        Checking that a Mongrel Cluster is Up and Listening on the Right Ports

        Checking that You Are Using a Native Database Driver

        Detecting Connection Leaks

    Exploring Other Tricks

    Exploring Other lsof Options

        Repeat Mode

        Field Output

        Terse Output

    What is lsof Good For?


    What is It?

    Interpreting strace Output

    How Do I Find Out About a Specific System Call?

    What is strace Good For?

    Some Concrete Examples

        Hanging Mongrel

        Where Did That Library Come From? Peeking at the Load Path

        Permission Denied

    Other Interesting strace Options

        Filtering Options

        Tracing Child Processes

        Basic System Level Profiling

    strace Siblings

        Mac OS X

        Solaris and OpenSolaris





    The Basics: Attaching to a Running Process and Getting the C-Level Backtrace

    Raising a Ruby Exception from gdb to Get the Ruby Stack Trace

    Easy Access to your gdb Tricks: Define Macros in .gdbinit

    Pushing the Envelope: Evaluate Arbitrary Ruby Code from gdb

        A Ruby Interpreter Within gdb

        Using gdb Inline Documentation

    Learning about Ruby Interpreter Internals

    What is gdb Good For?

    A Classic Gotcha: Unattachable Processes



About the Author


Submit Errata

More Information

Unlimited one-month access with your purchase
Free Safari Membership