Posted almost 5 years ago. Visible to the public.

Debugging your application

If there is an error or if you need to check whether requests are arriving at your server you should check the corresponding logfiles.

Don't forget that you may have multiple application servers and that the log entries will only appear on the server handling the request. You should check on the logfiles on all servers your application is deployed to.


There are several logfiles belonging to your deployments ( stands for your application name). The logfiles will be stored for each deployment separately.


Here you will find the access.log and the error.log of the webserver in use..


The logfiles written by your application should be stored here.


Passenger is the application server used to run your rails application. If your application can not start due to a critical error you will find the error message here (for e.g. syntax errors or missing secret_key_base). Log messages from different applications are all gathered together in this one log file, as the configuration option of passenger can be configured globally only. Due to that, this log is not available on shared hosting servers.

Live Debugger

This feature of Passenger needs Passenger Enterprise Archive . We can set this up if you provide the necessary license.

With this you are able to attach a irb shell to a running passenger process.

Current state of passenger processes

You can get information about current running passenger processes. As this information is displaying details for all running passenger processes and could be called by every deploy user, it is not allowed by default.
If you want to use this feature please contact our Operations Team.

Claus-Theodor Riegg
Last edit
Over 1 year ago
Marius Schuller
About this deck
We are makandra and do test-driven, agile Ruby on Rails software development.
Posted by Claus-Theodor Riegg to opscomplete (2018-01-22 12:52)