Passenger-install-apache2-module command not found

I have add a new instance with agent version v but now i am getting this error message:. Skipping Ganglia client configuration. Skipping MySQL client package installation.

The rails configure recipe works fine for me with postgresql. Do you have any custom cookbooks and is there any of them override the opsworks build-in cookbooks? The deploy and rails cookbooks which are cloned 6 months ago are out of sync with the latest agent cookbooks. The rails::configure requires a change in deploy cookbook, but it's overrided by your custom cookbook. I had done exactly the same and it works.

How can i prevent this happening again in future, for changes like rack gem updated to version 2. The problem is Passenger gem does not correctly pin their dependency rack gem. You can pin the rack gem version for passenger by installing rack gem before passenger. And this is how the latest agent fix this issue. Skip to content. Or, if you configured the PassengerLogFile directive, then the log file is in the referenced file.

The application or web framework may have its own log file that is independent from the Passenger log file. You should also check that file to see whether your application or web framework has logged any important messages. When an error occurs during request handling, it is typically logged here. Note that this file does not contain errors that Rails encounters during startup — those kinds of errors are typically written to STDERR, which means they end up in the Passenger log instead.

So if you're using Rails, please be sure to check production. Some problems are caused by bugs in Passenger. Passenger is under active maintenance and development, so there is a chance that — assuming you really ran into a bug — the bug is already fixed. Please upgrade Passenger to the latest version and check whether the problem is still there. If you suspect that your problem is a bug in Passenger, and upgrading didn't fix it, please report the bug to our Github issue tracker.

If upgrading Passenger didn't help, and you don't think your problem is caused by a bug, then please continue with this troubleshooting guide. Passenger takes care of a lot of things for you under the hood. If you don't know what Passenger does, then problems may seem opaque. Try learning more about the activities that Passenger perform ; it may help you with understanding the problem and with troubleshooting.

If you are stuck with a problem, please do not hesitate to contact one of the support resources. Passenger has a friendly community of users who look out for each other. We — Passenger's authors — are also ready to help you whenever we can. For most customers, this basic priority support has a response time of 3 working days, with a maximum of 1 support incident per month.

Please consult your contract for the exact support level that you are eligible for. The first request to your application takes more time than usual. Subsequent requests have the normal speed. Passenger starts your application the first time it is accessed, not during web server startup. Some applications can take several seconds to start. If you're using Ruby on Rails, then needing 10 seconds to start your application is normal. On slow or heavily loaded servers, or in case of large and heavy applications, the startup time may be even longer.

The operating system looks up commands using the PATH environment variable. However, sudo resets all environment variables to a default value, dictated by sudo. If Passenger was installed to a location that is not in the default sudo PATH value, then sudo will not be able to find the Passenger commands. In addition, if you installed Passenger using a Ruby interpreter that was installed through RVM, then you must use rvmsudo instead of sudo. As a rule, when you're an RVM user, always use rvmsudo instead of sudo.

Execute the command using its full path. You can use which as a normal user to lookup the full path:. Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search.

I'm using Ubuntu I've gotten to the part to where I need to install passenger and I've ran into a problem. When I execute gem install passenger --version 4. I'm not sure if or how to change the path to match the 2. The operating system looks up commands using the PATH environment variable. However, sudo resets all environment variables to a default value, dictated by sudo.

If Passenger was installed to a location that is not in the default sudo PATH value, then sudo will not be able to find the Passenger commands. In addition, if you installed Passenger using a Ruby interpreter that was installed through RVM, then you must use rvmsudo instead of sudo. As a rule, when you're an RVM user, always use rvmsudo instead of sudo.

I found my way to this page here They recommended typing out the path to the gem. After looking around a bit I found the gem located in