RUBYMINE DEBUG RAILS HOW TO
RUBYMINE DEBUG RAILS FULL
RUBYMINE DEBUG RAILS PLUS
RUBYMINE DEBUG RAILS SERIES

Where is STDOUT of the stuck process being sent?.

Before getting started, consider these questions:

This will give you the best possible chance of debugging the problem offline. Grab any logs that are availableĪgain, this may seem obvious, but the goal of the checklist is to remind you of everything you need to track. They give you a visual tree of the relationship between the stuck process, its sibling, and its parent process (e.g., a Unicorn master and its workers). Tools like htop and pstree can also be useful here. And the ps aux output is usually the first thing that goes into that transcript. I like to keep a transcript of the exact commands I’ve run, along with their output. The trusty ps utility is usually my first stop here-a quick ps aux | grep.

RUBYMINE DEBUG RAILS FULL

Identifying exactly which process is stuck is important in order to get a full picture of the behavior of the system as a whole.

RUBYMINE DEBUG RAILS PLUS

This sounds trivial, but it’s especially important for systems like Unicorn, Passenger, Resque, etc., where the system is composed of multiple processes that have different roles (often a single master process plus a number of workers). Here are the steps I follow when debugging a stuck Ruby process: Who said what?įirst, figure out exactly what process is stuck. So make sure you seize the opportunity when it’s available. Failing to capture enough information to reproduce a bug usually means you’ll hit it again. Create a “checklist” of things to run through so you don’t forget anything or skip any steps. Since encountering a stuck process (especially in production) is often stressful, I find it helps to think about the debugging steps you plan to take ahead of time. You might just discover the root cause of your problem, hone your debugging techniques, or discover a clue that helps you fix that tricky bug in your favorite open source project that no one has been able to pin down. Dig in and figure out what’s really going on. The next time this happens, don’t just kill that stuck process and move on. And the quickest path to that goal is usually to kill -9 the stuck process and restart it.īut I want you to make your future self a promise. When finding a stuck process, your primary goal usually is to just get the wheels of progress turning again. And giving you no obvious indication of what it was doing. If you’ve spent enough time working with a production system (or even just a continuous integration server), you’ve surely encountered a Ruby process that was “stuck.” You know the type-not crashing, but not making any real progress either.

RUBYMINE DEBUG RAILS SERIES

Don’t forget to check out the entire series so far: Cross Application Tracing, Thread Profiling, Living on the Edge with Rails 4 & Ruby 2, Thread Safe APIs & Sidekiq Support for Your Threading, and Security Banners (For If You Forgot to Apply the Latest CVE Patch).

RUBYMINE DEBUG RAILS HOW TO

Do I have to change the debug port / open another one for the second session? (I didn't found how to change the Rubymine attached debugger port, it's fixed to '3000:3000'), it is 'hardcoded in the appended -file.RailsConf 2013 has begun! To celebrate, we’re publishing a series of blog posts that highlight what’s new and exciting in the world of New Relic’s Ruby support.

It's no problem to start a regular rails console in Rubymine while a rails serverdebug session is runningĪll tutorials and videos I found were only covering the most basic cases, but not mine. (adding rails console in debug session while rails server's debug session is still running). I followed that tutorial ( ) to set up a singular debug session, but I was not able to find out how to use more than one debug session at once.

rails console AND rails server in debug sessionīut with the docker-compose-configuration I have to do that differently:.

That's no problem when working 'the old way' and works perfectly. Normally I can start these sessions for the 'rails server'- itself and one for debugging within the 'rails console'- and the 'rspec'-commands simultaneously. I normally do the 'usual' debugging, by using the and 'BUG'-buttons to start a debug session. I am experimenting with Rubymine's 'Docker-Compose' integration.

Rubymine debug rails