Apache restart hangs with Passenger 4.0.0.rc4 + ruby2.0.0p0

[joh...@law360.com]

I have a rails 3.2.13 app that runs fine with ruby1.9.3p392, passenger 3.0.19. I am upgrading the server to ruby 2.0.0p0 and passenger 4.0.0.rc4. 

https://gist.github.com/yubrew/5339097

On #44, the apache server restart hangs. Looking at /var/log/apache2/error.log reveals no errors. There are some notices and warnings though, which you can see in the second file of the gist.

Ubuntu 12.04.2 LTS

Apache2 2.2.22-1ubuntu1.3

passenger4.0.0.rc4

ruby2.0.0p0 installed with rvm

I am thinking it might have something to do with OpenSSL but I am not sure. 

`openssl version` returns OpenSSL 1.0.1 14 Mar 2012. 

`openssl version -d` returns OPENSSLDIR: "/usr/lib/ssl"

`which openssl` returns /usr/bin/openssl

[Hongli Lai]

We've received a report about Apache hanging on restart with Phusion
Passenger 4, but so far we haven't been able to reproduce the problem.

When you mention hanging, what exactly hangs? Is it the apachectl command?

> --
> You received this message because you are subscribed to the Google Groups
> "Phusion Passenger Discussions" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to phusion-passen...@googlegroups.com.
> To post to this group, send email to phusion-...@googlegroups.com.
> Visit this group at
> http://groups.google.com/group/phusion-passenger?hl=en-US.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



--
Phusion | Ruby & Rails deployment, scaling and tuning solutions

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)

[joh...@law360.com]

I retried with passenger-4.0.rc6, but the apache restart still hangs. I am pretty new to passenger and apache, so I apologize in advance for my ignorance.

Running `apachectl start` after `apachectl stop` hangs. It seems to be stuck on `apachectl start`

[Hongli Lai]

Can you show me the output of passenger-memory-stats and the last few
lines in your Apache error log right after you've called 'apachectl
stop'?

[joh...@law360.com]

`passenger-memory-stats`

------- Apache processes --------

### Processes: 0

### Total private dirty RSS: 0.00 MB

-------- Nginx processes --------

### Processes: 0

### Total private dirty RSS: 0.00 MB

--- Passenger processes ----

PID   VMSize  Private  Name

----------------------------

2636  4.3 MB  0.2 MB   PassengerWatchdog

3292  4.3 MB  0.2 MB   PassengerWatchdog

3302  4.3 MB  0.2 MB   PassengerWatchdog

### Processes: 3

### Total private dirty RSS: 0.55 MB

`/var/log/apache2/error.log`

[Wed Apr 17 14:54:42 2013] [notice] Apache/2.2.22 (Ubuntu) configured -- resuming normal operations

[Wed Apr 17 15:00:03 2013] [notice] caught SIGTERM, shutting down

[Wed Apr 17 15:00:05 2013] [warn] RSA server certificate CommonName (CN) `www.docketslaw360.com' does NOT match server name!?

[joh...@law360.com]

I simplified the workflow using rvm, but it still hangs on restart, with no errors in the logs. The following is the full shell script.

apt-get update

apt-get install curl

\curl -L https://get.rvm.io | bash -s head

source /etc/profile.d/rvm.sh

rvm requirements

rvm install 2.0.0

rvm rubygems current

gem install passenger --pre

apt-get -y install apache2-mpm-worker 

apt-get -y install apache2-prefork-dev libapr1-dev libaprutil1-dev

cat <<EOF > /etc/apache2/conf.d/passenger

LoadModule passenger_module /usr/local/rvm/gems/ruby-2.0.0-p0/gems/passenger-4.0.0.rc6/libout/apache2/mod_passenger.so

PassengerRoot /usr/local/rvm/gems/ruby-2.0.0-p0/gems/passenger-4.0.0.rc6

PassengerDefaultRuby /usr/local/rvm/wrappers/ruby-2.0.0-p0/ruby

EOF

/etc/init.d/apache2 restart

[Hongli Lai]

Everything looks normal so far. Can you set PassengerLogLevel to 3, run 'apachectl restart', and show me the log?

[joh...@law360.com]

I updated to the latest release of passenger 4.0.2 and now there are no issues.

[joh...@law360.com]

Also, to anyone else running into this issue, m1.small seemed to keep getting the error, but using any other instance of AWS ran fine. So using c1.medium or anything other than m1.small worked.