Ask A Question

Notifications

You’re not receiving notifications from this thread.

Something has changed with Passenger that has left the guides unusuables

Juan S. Caro asked in General

It is the fifth time I try from scratch the deployment and have had deployed previously without any major problem. Think is, I don't know if it because now default repositories submit passenger 6, but I can find a way to get the app in passenger working. When I deploy with capistrano, It always fails in the point of restarting passenger:

05:16 passenger:restart
01 passenger-config restart-app /home/deploy/redvies --ignore-app-not-running
01 *** ERROR: Phusion Passenger(R) doesn't seem to be running. If you are sure that it
01 is running, then the causes of this problem could be one of:
01
01 1. You customized the instance registry directory using Apache's
01 PassengerInstanceRegistryDir option, Nginx's
01 passenger_instance_registry_dir option, or Phusion Passenger(R) Standalone's
01 --instance-registry-dir command line argument. If so, please set the
01 environment variable PASSENGER_INSTANCE_REGISTRY_DIR to that directory
01 and run this command again.
01 2. The instance directory has been removed by an operating system background
01 service. Please set a different instance registry directory using Apache's
01 PassengerInstanceRegistryDir option, Nginx's passenger_instance_registry_dir
01 option, or Phusion Passenger(R) Standalone's --instance-registry-dir command
01 line argument.
(Backtrace restricted to imported tasks)
cap aborted!
SSHKit::Runner::ExecuteError: Exception while executing as deploy@80.240.127.15: passenger-config exit status: 1
passenger-config stdout: Nothing written
passenger-config stderr: *** ERROR: Phusion Passenger(R) doesn't seem to be running. If you are sure that it
is running, then the causes of this problem could be one of...

Passenger status says everything is alright, but again, no app is running. I have triple check everything, but it seems something has changed. Any idea?

Reply

It is possible that the Passenger version you are using is not compatible with the version of Ruby you are using. Try updating both Passenger and Ruby to the latest versions and then redeploying your application. Additionally, check the Passenger documentation to make sure the Passenger configuration parameters are set correctly.

Reply
Join the discussion
Create an account Log in

Want to stay up-to-date with Ruby on Rails?

Join 85,376+ developers who get early access to new tutorials, screencasts, articles, and more.

    We care about the protection of your data. Read our Privacy Policy.