Passenger troubleshooting

Read the following troubleshooting tips for common issues when using the Ruby agent and Passenger.

Restarting the agent

If all you do is edit the Passenger tmp/restart.txt file, it will not pick up the new agent. When you update the agent and restart Passenger, you must do a hard restart of Apache for the change to take effect.

Missing log files

For Passenger, the log file is newrelic_agent.passenger.log. Recommendation: For Apache users, provide write permissions for the entire /log directory.

Developer mode

When using Passenger in Developer mode, sometimes you may notice the list of requests may disappear, or that it seems like it misses some requests. Also, when selecting a request, you may see an error message indicating the trace is not available, suggesting maybe you restarted.

This occurs when Passenger spawns more than one handler process. The transaction traces get put in one of the processes, and if you connect to the other one, you will not see it.

The workaround is to set the max number of instances to 1 by using the PassengerMaxPoolSize parameter. Also, if you refresh several times, you have a good chance of getting the requests back.

For more help

Join the discussion about Ruby in the New Relic Online Technical Community! The Technical Community is a public platform to discuss and troubleshoot your New Relic toolset.

If you need additional help, get support at support.newrelic.com.