Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Passenger standalone fails if no HOME env set #713
From xmitchx on January 27, 2011 01:22:08
What steps will reproduce the problem? 1. Unset HOME env variable
Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=614
From xmitchx on January 26, 2011 16:25:12
I should note the situation under which this occurs, specifically. I create upstart scripts ( http://upstart.ubuntu.com/ ) to manage my app servers. Say I have a project named "project-x," I can then just do "service project-x start" or "service project-x restart" and it just does the right thing.
Upstart doesn't send any environmental variables down into the executing process, so ENV['HOME'] isn't available.
I work around this at the moment by explicitly telling my upstart script to set HOME to "/root" but I feel that this shouldn't be necessary for passenger to work.
From email@example.com on October 14, 2011 20:20:40
This occurred for me. I was launching Passenger standalone from a userdata script using an Ubuntu Lucid EC2 instance. In that environment HOME is not set. I worked around it by setting HOME to blank in the userdata script just before starting Passenger. The error occurred at:
passenger-3.0.5/lib/phusion_passenger/standalone/command.rb:103:in `join': can't convert nil into String (TypeError)