Passenger Not Picking Up Website Call

[Curt Rowe]

I tried to bring up one of my Ruby sites and just got a listing of the public directory to which vhosts points. I checked the help and verfied passenger was running. I restarted Apache and had the same problem. It's been a long time since I've run my development sites. I'm thinking I installed a major release of OS X and it replaced my httpd.conf file. I moved my chages to the new version and my PHP websites worked fine. I don't remember testing my Ruby ones. The problem may not have anything to do with Passenger as it's not even invoked.

The is the tail of the Apache log file after a restart:

[ 2016-05-16 18:37:55.8624 15808/0x7fff776a2000 agents/LoggingAgent/Main.cpp:321 ]: PassengerLoggingAgent online, listening at unix:/tmp/passenger.1.0.15795/generation-0/logging

[ 2016-05-16 18:37:55.8626 15804/0x7fff776a2000 agents/Watchdog/Main.cpp:728 ]: All Phusion Passenger agents started!

[Mon May 16 18:37:55.886220 2016] [core:crit] [pid 15795] (22)Invalid argument: AH00069: make_sock: for address [::]:80, apr_socket_opt_set: (IPV6_V6ONLY)

[ 2016-05-16 18:37:55.8906 15811/0x7fff776a2000 agents/Watchdog/Main.cpp:538 ]: Options: { 'analytics_log_user' => 'nobody', 'default_group' => 'nobody', 'default_python' => 'python', 'default_ruby' => '/Users/curt/.rbenv/versions/2.2.0/bin/ruby', 'default_user' => 'nobody', 'log_level' => '0', 'max_pool_size' => '6', 'passenger_root' => '/Users/curt/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/passenger-4.0.57', 'passenger_version' => '4.0.57', 'pool_idle_time' => '300', 'temp_dir' => '/tmp', 'union_station_gateway_address' => 'gateway.unionstationapp.com', 'union_station_gateway_port' => '443', 'user_switching' => 'true', 'web_server_passenger_version' => '4.0.57', 'web_server_pid' => '15795', 'web_server_type' => 'apache', 'web_server_worker_gid' => '70', 'web_server_worker_uid' => '70' }

[ 2016-05-16 18:37:55.9029 15813/0x7fff776a2000 agents/HelperAgent/Main.cpp:650 ]: PassengerHelperAgent online, listening at unix:/tmp/passenger.1.0.15795/generation-1/request

[ 2016-05-16 18:37:55.9097 15815/0x7fff776a2000 agents/LoggingAgent/Main.cpp:321 ]: PassengerLoggingAgent online, listening at unix:/tmp/passenger.1.0.15795/generation-1/logging

[ 2016-05-16 18:37:55.9098 15811/0x7fff776a2000 agents/Watchdog/Main.cpp:728 ]: All Phusion Passenger agents started!

[Mon May 16 18:37:55.965981 2016] [mpm_prefork:notice] [pid 15795] AH00163: Apache/2.4.18 (Unix) Phusion_Passenger/4.0.57 PHP/5.5.31 configured -- resuming normal operations

My additions to the httpd config file:

   LoadModule passenger_module /Users/curt/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/passenger-4.0.57/buildout/apache2/mod_passenger.so

   <IfModule mod_passenger.c>

     PassengerRoot /Users/curt/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/passenger-4.0.57

     PassengerDefaultRuby /Users/curt/.rbenv/versions/2.2.0/bin/ruby

     PassengerUser Curt

   </IfModule>

 One of my vhosts entries that I tried:

<VirtualHost *:80>

    ServerName amcolan.loc

    DocumentRoot "/Volumes/Data/htdocs/amcolan/public"

  RailsEnv development

  <directory /Volumes/Data/htdocs/amcolan/public>

    Allow from all

    Options -MultiViews

    Require all granted

  </directory>

</VirtualHost>

OS X 10.11.4

I'm using rbenv

[Daniel Knoppel]

It would be best to switch to Passenger 5 and check the deployment guide.

Version 5 has better troubleshooting options as well.

- Daniel

[Curt Rowe]

I upgraded passenger using brew upgrade passenger. I completed normally and installed version 5.0.24. When I run passenger version, I'm still seeing the old version. As mentaioned I also use rbenv. I also did rbenv rehash to no avail. I read in one place that you can use brew to install passenger, in another to only do passenger -init once, and in a third to install it like one would install any other gem. This seems contrary to other documentation that one does not have to put passenger in the projects gem file. Can you shed any light on what might be the right way or at least one of the right ways.

[Curt Rowe]

Never mind. It turns out I have two copies of passenger: one installed using brew and one installed using gem. When I updated the gem version, I saw the latest version number. Now to get it to work with apache.

[Curt Rowe]

OK, I got further. Passenger now gives me an error screen. I've got a missing gem. This is something I can fix  hopefully. Should I get rid of the brew installed version of passenger since the gem one is being used?

[Daniel Knoppel]

We recommend not having multiple versions installed to avoid confusion, so yeah, you can uninstall whichever one you like.

- Daniel