From lipsiasoftsrv on April 14, 2008 12:13:08

I apreciate so much if RailsMaxPoolSize can be specifyed for each vhost.

Think to the hosting company, If I set RailsMaxPoolSize = 60 and Ive one user with a super large of
visitors it decrease the other hosted site.

Thanks!

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=17

From braghavan on April 12, 2008 16:11:15

What steps will reproduce the problem? 1. Remove default documents such as index.html from public
2. Enable RailsAllowModRewrite on
3. Have a rails controller to handle map.root
4. Access the http://www.example.com/ What is the expected output? What do you see instead? The expected output should be from rails, instead it is trying to get the request handled by
apache. However setting RailsAllowModRewrite off gets the request processed by rails. What version of the product are you using? On what operating system? Apache2 on Debian

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=11

From honglilai on April 19, 2008 15:10:26

Stack trace is shown here: http://groups.google.com/group/phusion-passenger/browse_thread/thread/3182678b1862c3f1?hl=en The problem is that AssetTagHelper runs something like this:

ASSET_DIR = Rails.public_directory

public_directory, in turn, relies on RAILS_ROOT, which isn't available
during preloading of the Rails framework.

A patch should be sent to Rails. The patch should remove the assumption
that RAILS_ROOT is available, and should add a method for allowing
re-initialization of constants such as ASSET_DIR, after RAILS_ROOT has been
set.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=29

From avaspell on April 17, 2008 02:16:09

What steps will reproduce the problem? 1. Install RubyGems 1.0.1 or higher
2. Install 2 rails versions
3. Configure an app to load the older rails version
4. Attempt to access app using older version

The Gem Specification for Passenger adds as a dependency rails. On RubyGems

= 1.0.1, it automatically loads all dependent gems. Since rails is listed
as a dependency, it gets auto-loaded. This is real bad, since an attempt to
load the older version will always fail. Suggest that the dependency be
removed ASAP until RubyGems provides a mechanism to prevent this.
Alternatively, Passenger could extend Gem itself, but that sounds like a
bad idea in general.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=25

From brejoc on April 22, 2008 15:31:17

What steps will reproduce the problem? 1. Start a rails application.
2. Leave it alone for a few hours. (perhaps 4-9 hours)
3. The first request should take nearly 1 minute. First the delivery of the html takes very long and
then it takes about 2 seconds for every picture to show up one after another.
4. After that first request everything is working fine and fast. What version of the product are you using? On what operating system? • Debian Etch 4.0
• Rails 1.2.6
• Ruby: ruby 1.8.6 (2008-03-03 patchlevel 114) [i686-linux]

Seems that it takes mod_rails rather long to start the first rails-instance. Perhaps it would help to
introduce the option RailsMinPoolSize for rails applications with a more critical response time that
are not often needed.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=32

From kennonballou on April 17, 2008 16:44:58

Some plugins (faster_csv in my case) expect the ResponseSender to have the << method, which
Passenger's doesn't appear to have yet.

This simple monkey patch I added to my rails config/environment.conf fixed the issue:

module Passenger
class RequestHandler
class ResponseSender
def <<(block)
@io.write(block)
end
end
end
end

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=26

From martin.carpenter on April 14, 2008 20:33:28

Running the command:

gem install passenger

fails at the build stage on Solaris 10 SPARC (possibly also x86:
untested). Errors and system information are below. A typical compiler
error is:

native_support.c:63: error: structure has no member named `msg_control'

See the following guard in <sys/socket.h>:

if defined(_XPG4_2) || defined(_KERNEL)

void msg_control; / ancillary data /
socklen_t msg_controllen; / ancillary data buffer len /
int msg_flags; / flags on received message */

else

gem install passenger

Updating metadata for 7 gems from http://gems.rubyforge.org/ .......
complete
Bulk updating Gem source index for: http://gems.rubyforge.org/ Building native extensions. This could take a while...
ERROR: Error installing passenger:
ERROR: Failed to build gem native extension.

/usr/local/bin/ruby extconf.rb install passenger
creating Makefile

make
gcc -I. -I/usr/local/lib/ruby/1.8/sparc-solaris2.10 -I/usr/local/lib/ruby/
1.8/sp
arc-solaris2.10 -I. -I/usr/local/include -I/usr/local/ssl/include -I/usr/
local/i
nclude/ncurses -I/usr/local/BerkeleyDB.4.2/include -I/usr/openwin/include -
fPIC
-O2 -L/usr/local/lib -R/usr/local/lib -L/usr/local/ssl/lib -R/usr/local/
ssl/lib
-L/usr/openwin/lib -R/usr/openwin/lib -c native_support.c
native_support.c: In function send_fd': native_support.c:63: error: structure has no member namedmsg_control'
native_support.c:64: error: structure has no member named msg_controllen' native_support.c:65: error: structure has no member namedmsg_flags'
native_support.c: In function recv_fd': native_support.c:107: error: structure has no member namedmsg_control'
native_support.c:108: error: structure has no member named msg_controllen' native_support.c:109: error: structure has no member namedmsg_flags'
native_support.c:120: error: structure has no member named `msg_controllen'
make: *** [native_support.o] Error 1

Gem files will remain installed in /usr/local/lib/ruby/gems/1.8/gems/
passenger-1
.0.1 for inspection.
Results logged to /usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.1/ext/
passenge
r/gem_make.out

System/environment information follows:

$ uname -a
SunOS ftl1sutst04 5.10 Generic_125100-06 sun4u sparc SUNW,UltraAX-i2
$
$ ruby -v
ruby 1.8.6 (2007-03-13 patchlevel 0) [sparc-solaris2.10]
ftl1sutst04 $ pkginfo -x SMCruby
SMCruby ruby
(sparc) 1.8.6
$
$ gem -v
1.1.1
$
$ gcc -v
Reading specs from /opt/sfw/lib/gcc/sparc-sun-solaris2.10/3.4.2/specs
Configured with: ../gcc-3.4.2/configure --prefix=/opt/sfw --with-ld=/usr/
ccs/bin/ld --with-gnu-as --with-as=/opt/sfw/bin/gas --enable-shared --
disable-libgcj
Thread model: posix
gcc version 3.4.2
$

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=18

From benabik on April 22, 2008 18:46:57

Using passenger on the root of a web server prevents userdir requests (such as ~user) from being
handled properly. Ideally, Passenger should allow mod_userdir to handle requests before
attempting to send them to the rails application.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=33

From albert.ramstedt on May 02, 2008 01:47:17

What steps will reproduce the problem? Seemingly random. I have observed the same behaviour in 1.0.1 and 1.0.4,
and it is probably evident in other releases. What is the expected output? What do you see instead? What version of the product are you using? On what operating system? 1.0.1 and 1.0.4 have both given the same problems on different applications Please provide any additional information below. I have, as prev. stated, seen this error appear in random places at random
times on two different servers, running different Linux distros and
completely different applications and rails versions (1.0.0 and 1.2.2).

Error desc in my app:

A ActiveRecord::StatementInvalid occurred in
static_image#index:
PGError: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
: SELECT * FROM base_contents WHERE (base_contents."id" IS NULL ) LIMIT 1
[RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:88:in
`log'

here is a backtrace, for what it is worth.

[RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract_adapter.rb:88:in
log' [RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb:137:in execute'
[RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb:351:in
select' [RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/connection_adapters/postgresql_adapter.rb:118:in select_all'
[RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/base.rb:431:in
find_by_sql' [RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/base.rb:395:infind'
[RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/base.rb:393:in find' [RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/deprecated_finders.rb:22:in find_first'
[RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/base.rb:982:in send' [RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/base.rb:982:in method_missing'
[RAILS_ROOT]/vendor/plugins/asken_engine/components/plugins/sidebars/static_image_controller.rb:27:in
content' [RAILS_ROOT]/vendor/plugins/asken_engine/components/plugins/sidebars/static_image_controller.rb:25:in each'
[RAILS_ROOT]/vendor/plugins/asken_engine/components/plugins/sidebars/static_image_controller.rb:25:in
content' [RAILS_ROOT]/vendor/plugins/asken_engine/components/sidebars/sidebar_controller.rb:46:in index'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:853:in
send' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:853:in perform_action_without_filters'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/filters.rb:332:in
perform_action_without_benchmark' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:69:in perform_action_without_rescue'
/usr/lib/ruby/1.8/benchmark.rb:293:in measure' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:69:in perform_action_without_rescue'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/rescue.rb:82:in
passenger_orig_perform_action' /usr/lib/ruby/gems/1.8/gems/passenger-1.0.4/lib/passenger/request_handler.rb:145:in perform_action'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:369:in
send' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:369:in process_without_session_management_support'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/session_management.rb:116:in
process' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:300:in process'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/components.rb:55:in
component_response' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/components.rb:42:in render_component_as_string'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/components.rb:81:in
component_logging' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/components.rb:41:in render_component_as_string'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/components.rb:28:in
send' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/components.rb:28:in render_component'
[RAILS_ROOT]/vendor/plugins/asken_engine/app/helpers/application_helper.rb:105:in
render_sidebar' [RAILS_ROOT]/vendor/plugins/asken_engine/components/sidebars/sidebar/display_plugins.rhtml:5:in _run_rhtml_sidebars_sidebar_display_plugins'
[RAILS_ROOT]/vendor/plugins/asken_engine/components/sidebars/sidebar/display_plugins.rhtml:2:in
each' [RAILS_ROOT]/vendor/plugins/asken_engine/components/sidebars/sidebar/display_plugins.rhtml:2:in _run_rhtml_sidebars_sidebar_display_plugins'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_view/base.rb:268:in send' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_view/base.rb:268:in compile_and_render_template'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_view/base.rb:244:in
render_template' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_view/base.rb:205:in render_file'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:655:in
render_file' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:627:in render_with_no_layout'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/layout.rb:228:in
render_without_benchmark' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:53:in render'
/usr/lib/ruby/1.8/benchmark.rb:293:in measure' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:53:in render'
[RAILS_ROOT]/vendor/plugins/asken_engine/components/sidebars/sidebar_controller.rb:94:in
display_plugins' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:853:in send'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:853:in
perform_action_without_filters' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/filters.rb:332:in perform_action_without_benchmark'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:69:in
perform_action_without_rescue' /usr/lib/ruby/1.8/benchmark.rb:293:inmeasure'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:69:in
perform_action_without_rescue' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/rescue.rb:82:in passenger_orig_perform_action'
/usr/lib/ruby/gems/1.8/gems/passenger-1.0.4/lib/passenger/request_handler.rb:145:in
perform_action' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:369:in send'
[RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:369:in
process_without_session_management_support' [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/session_management.rb:116:in process'
[RAILS_ROOT]/vendor/rails...

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=50

From drew.bomhof on May 01, 2008 17:50:13

System description: Ubuntu Gutsy Xen VM
Memory: 512
Setup as a test for mod_rails

The following error occurs when I attempt to run any of my rails apps (that
run fine using script/server

VHost config:

<VirtualHost *:80>
ServerName blah.blah.com
DocumentRoot /var/www
RailsBaseURI /analysis

Symlink in DocumentRoot:

analysis -> /usr/local/rails_apps/analysis/public

Error stack:

/var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/application_spawner.rb:229:
[BUG] Segmentation fault
ruby 1.8.6 (2007-06-07) [x86_64-linux]

*** Exception NoMethodError in Passenger::FrameworkSpawner (You have a nil
object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.[]) (process 3540):
from
/var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/application_spawner.rb:149:in
start' from /var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/framework_spawner.rb:278:in handle_spawn_application'
from
/var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/framework_spawner.rb:273:in
synchronize' from /var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/framework_spawner.rb:273:in handle_spawn_application'
from
/var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:291:in
__send__' from /var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:291:in main_loop'
from
/var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:147:in
start_synchronously' from /var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:114:in start'
from
/var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:108:in
fork' from /var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:108:in start'
from
/var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/framework_spawner.rb:104:in
start' from /var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/spawn_manager.rb:106:in spawn_application'
from
/var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/spawn_manager.rb:102:in
synchronize' from /var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/spawn_manager.rb:102:in spawn_application'
from
/var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/spawn_manager.rb:183:in
handle_spawn_application' from /var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:291:in send'
from
/var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:291:in
main_loop' from /var/lib/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:147:in start_synchronously'
from /var/lib/gems/1.8/gems/passenger-1.0.3/bin/passenger-spawn-server:32

It seems that my OS is missing something as this is a mod_rails issue and
not a problem with the apps themselves. Incidentally I have mod_rails
running wonderfully on a Gutsy install running in Parallels.

I would just like to know if anyone has seen this before or know of a
library I could be missing.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=47

From deanholdren on April 21, 2008 17:41:55

What steps will reproduce the problem? 1. app's root at /opt/my_app
2. docroot defined as /opt/docroot
3. Alias /my_app /opt/my_app/public
4. RailsBaseURI /my_app
5. http://myhost/my_app

I expect the app to work correctly, but instead I see the following:

Passenger error #2

Passenger thinks that the Rails application's "public" directory is "/
opt/docroot/my_app", but it doesn't seem to be valid.

using passenger 1.0.1 gem on CentOS

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=30

From manfred on April 17, 2008 17:27:53

I'm having so issues with running Passenger 1.0.1 on Mac OSX 10.5.2. When I duplicate the
configuration from my Mac Mini to my MacBook, I get the following in the Apache error log:

[19299:ApplicationPoolClientServer.h:394] Cannot send a file descriptor: Invalid argument (22) ---
aborting!
[Thu Apr 17 16:12:06 2008] [notice] seg fault or similar nasty error detected in the parent process

I believe that the main difference between the two is the fact that the MacBook has a case sensitive
filesystem.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=27

From honglilai on April 22, 2008 20:34:09

What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? Please use labels and text to provide additional information.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=34

From deepsky99 on April 15, 2008 14:33:10

What steps will reproduce the problem? 1. Access site using SSL, with no Client cert, just a server one

Exception is raised...

[14733:Application.h:264] Application 0x829e5d8: created.
*** Exception ArgumentError in application (odd number of arguments
for Hash) (process 18668):
from
/usr/lib/ruby/gems/1.8/gems/passenger-1.0.1/lib/passenger/request_handler.rb:286:in
[]' from /usr/lib/ruby/gems/1.8/gems/passenger-1.0.1/lib/passenger/request_handler.rb:286:in process_request'
.....

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=20

From fannar on May 01, 2008 17:48:16

Trying to find out the Rails_env. Using ENV['RAILS_ENV'] gets me development but RAILS_ENV gets
me production.

Using passenger 1.0.3

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=45

From Rawn027 on April 16, 2008 16:25:03

What steps will reproduce the problem? 1. Install Passenger on FreeBSD with Apache 2.2.8 Built from Ports
2. Setup your Apache config accordingly
3. Start Apache What is the expected output? What do you see instead? Apache is listening and your rails app is working when you connect to the virtual host. What version of the product are you using? On what operating system? Passenger 1.0.1 on FreeBSD 7.0-RELEASE with Apache 2.2.8 Please provide any additional information below. Submitter: [RIT]Rawn027

OS: FreeBSD 7.0-RELEASE (ULE Scheduler)

Packages

Apache 2.2.8 Prefork MPM
Ruby 1.8.6 p111
RubyGems 1.1.1

Gems

actionmailer (2.0.2)
actionpack (2.0.2)
activerecord (2.0.2)
activeresource (2.0.2)
activesupport (2.0.2)
capistrano (2.2.0)
fastthread (1.0.1)
god (0.7.3)
highline (1.4.0)
hoe (1.5.1)
needle (1.3.0)
net-sftp (1.1.1)
net-ssh (1.1.2)
passenger (1.0.1)
postgres (0.7.9.2008.01.28)
rails (2.0.2)
rake (0.8.1)
rspec (1.1.3)
rubyforge (0.4.5)
rubygems-update (1.1.1)

/var/log/httpd-error.log

*** Cannot initialize Passenger: write() failed: Bad file descriptor
(9)[5457:ApplicationPoolClientServer.h:394] Cannot send a file descriptor: Bad file descriptor (9)
--- aborting!
[Tue Apr 15 10:20:58 2008] [notice] seg fault or similar nasty error detected in the parent
process
[Tue Apr 15 10:20:58 2008] [notice] Apache/2.2.8 (FreeBSD) mod_ssl/2.2.8 OpenSSL/0.9.8e
DAV/2 Phusion_Passenger/1.0.1 configured -- resuming normal operations

Attachment: freebsd_httpd.core

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=23

From ben%[email protected] on April 12, 2008 22:00:19

There is currently a RailsUser option which will all you to specify which
effective user the Rails app runs as, but it doesn't seem you can specify
the effective group. Many of us (I'm running Ubuntu 7.10) like to utilize
groups to manage permissions and leverage the www-data group for certain
purposes (in Debian).

I actually discovered this when I learned that Passenger was setting itself
to run the Rails application as bhughes but also using an effective group
ID of bhughes instead of www-data. Since I had global read permissions
off, this lead to a situation whereby Rails was complaining that RAILS_ROOT
is not a directory. After some digging I discovered this was the problem.
I detail this a little more in my blog entry: http://www.railsgarden.com/2008/04/12/configurating-passenger-mod_rails-on-slicehost-with-ubuntu-710/ So it might be nice to have:

• A RailsGroup option for explicitly setting the effective GID
• Have Passenger grab the group owner of the evironment.rb file and use
  this by default instead of just the primary group of the user ID grabbed
  the same way.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=13

From ilborro on May 01, 2008 00:56:04

What steps will reproduce the problem? 1. Intall apache2+passenger 1.0.3
2. Create some rails application, and setup a massive apache hosting, as
shown into official apache2 docs: http://httpd.apache.org/docs/2.0/vhosts/mass.html (both using
VirtualDocumentRoot and mod_rewrite + mapping file) What is the expected output? What do you see instead? Expected output: rails applications running
What i see instead: every rails application fails to start, with error
"Application error - Rails application failed to start properly" What version of the product are you using? On what operating system? Server version: Apache/2.2.3
Server built: Jan 27 2008 18:13:21
passenger: 1.0.3

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=44

From sikandsak on April 12, 2008 16:25:16

What steps will reproduce the problem?

1. On the machine that doesn't have Apache, install MAMP in /Applications
2. Install Passenger from ruby gem
3. run passenger-install-apache2-module

What is the expected output? What do you see instead?

I expected that the apache in /Application/MAMP/bin/apache2 got detected. However, it said
that there's no Apache installed in my machine. On the other hand, Apache 2 development
headers has been found at /Applications/MAMP/Library/bin/apxs, which should be mean that I
have apache installation in my machine

Also, at the first line of installation program it said that:

cannot open /Applications/MAMP/Library/build/config_vars.mk: No such file or directory at 
/Applications/MAMP/Library/bin/apxs line 218.

What version of the product are you using? On what operating system?

Passenger 1.0.1 / Mac OS X Leopard 10.5.2

Please provide any additional information below.

I've tried to export the variable APXS and APXS2 to Applications/MAMP/bin/apache2/bin/apxs,
but the error still there and it can't find the apache2 still ..

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=12

From kanarie on April 15, 2008 13:01:48

What steps will reproduce the problem? 1. Install the frozen gems generator
( http://blog.thinkrelevance.com/2008/3/6/frozen-gems-generator )
2. Install a gem using script/gem install
3. Run script/server, check to see the gem works
4. Run the same application using mod_rails
5. The gem installed using script/gem install is not available from mod_rails What is the expected output? What do you see instead? It would be great if Passenger supported the frozen gems, especially for
shared hosting.
Normally the frozen gems get loaded through config/preinitializer.rb =>
config/gems.rb, but it seems mod_rails doesn't do this. What version of the product are you using? On what operating system? Passenger 1.0.1, tried on Ubuntu and Debian

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=19

From tutormatch on April 11, 2008 22:33:22

1. Configure mod_rails per the documentation.
2. Note that <rails_home>/log/production.log does not get written to.
3. Be completely incapable of tracking the behavior of your app in the way
   to which you are accustomed. What is the expected output? What do you see instead? Expected is stuff in production.log, e.g.
   Processing AssessmentAttemptsController#answer_diagnostic (for 65.78.144.6
   at 2008-04-11 13:31:34) [GET]
   Session ID: a8cf2c6f8aa538c5d5f1156483be7823
   Parameters: {"current_state"=>"Diagnostic phase 1",
   "current_diagnostic_id"=>"1082", "diagnostic_answer_choice"=>"4533",
   "action"=>"answer_diagnostic", "controller"=>"assessment_attempts",
   "_"=>"1207945765937"}
   Actual: nothing What version of the product are you using? On what operating system? Passenger 1.0.1, Rails 2.0.2, CentOS 5.1, Apache 2 Please provide any additional information below. We love the performance but can't use this without the log!

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=4

From iwarshak on April 11, 2008 22:22:33

What steps will reproduce the problem? 1. Install apache in a non-standard directory (i.e. /Users/ian/apache)
2. export APXS2=/Users/ian/apache/bin/apxs (just like the instructions say)
3. Install passenger What is the expected output? What do you see instead? The passenger install does not recognize the APXS2 variable. It still complains that it is going to
install in the default Mac OSX Apache install. Changing the variable to APXS seems to fix the
problem What version of the product are you using? On what operating system? Please provide any additional information below.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=3

From schlueter on April 11, 2008 19:15:54

What steps will reproduce the problem? 1. Install Passenger
2. Configure following the instructions
3. Hit website What is the expected output? What do you see instead? I got an error saying my server wasn't running. I was hoping to see my
website :) What version of the product are you using? On what operating system? 1.0.1
Mac OSX Leopard Please provide any additional information below. Here is a stack trace from the error_log including debugging, let me know
if you need any more information.

[Fri Apr 11 13:12:43 2008] [info] Init: Seeding PRNG with 144 bytes of entropy
[Fri Apr 11 13:12:43 2008] [info] Init: Generating temporary RSA private
keys (512/1024 bits)
[Fri Apr 11 13:12:43 2008] [info] Init: Generating temporary DH parameters
(512/1024 bits)
[Fri Apr 11 13:12:43 2008] [warn] Init: Session Cache is not configured
[hint: SSLSessionCache]
[Fri Apr 11 13:12:43 2008] [info] Init: Initializing (virtual) servers for SSL
[Fri Apr 11 13:12:43 2008] [info] mod_ssl/2.2.8 compiled against Server:
Apache/2.2.8, Library: OpenSSL/0.9.7l
[Fri Apr 11 13:12:43 2008] [info] Init: Seeding PRNG with 144 bytes of entropy
[Fri Apr 11 13:12:43 2008] [info] Init: Generating temporary RSA private
keys (512/1024 bits)
[Fri Apr 11 13:12:44 2008] [info] Init: Generating temporary DH parameters
(512/1024 bits)
[Fri Apr 11 13:12:44 2008] [info] Init: Initializing (virtual) servers for SSL
[Fri Apr 11 13:12:44 2008] [info] mod_ssl/2.2.8 compiled against Server:
Apache/2.2.8, Library: OpenSSL/0.9.7l
[Fri Apr 11 13:12:44 2008] [notice] Digest: generating secret for digest
authentication ...
[Fri Apr 11 13:12:44 2008] [notice] Digest: done
[Fri Apr 11 13:12:44 2008] [warn] pid file /private/var/run/httpd.pid
overwritten -- Unclean shutdown of previous Apache run?
[Fri Apr 11 13:12:44 2008] [notice] Apache/2.2.8 (Unix) mod_ssl/2.2.8
OpenSSL/0.9.7l DAV/2 Phusion_Passenger/1.0.1 configured -- resuming normal
operations
[Fri Apr 11 13:12:44 2008] [info] Server built: Feb 20 2008 12:01:56
[Fri Apr 11 13:12:44 2008] [debug] prefork.c(991): AcceptMutex: flock
(default: flock)
[27991:ApplicationPoolClientServer.h:394] Cannot send a file descriptor:
Invalid argument (22) --- aborting!
[Fri Apr 11 13:12:44 2008] [notice] seg fault or similar nasty error
detected in the parent process

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=2

From frigginusername on April 13, 2008 18:35:13

What steps will reproduce the problem? 1. Restart Apache
2. Use 2 tabs in a browser to pull up 2 concurrent requests to your application. (Helps if one of the requests is slow)
3. 500 errors from MySQL : Mysql::Error: Lost connection to MySQL server during query What is the expected output? What do you see instead? What version of the product are you using? On what operating system? Rails 2.0.2, Mac OSX, Apache 2.2.8 built from source, MySQL 5 Please provide any additional information below. This only seems to happen after apache is started/restarted for the first time. I can't force the MySQL connection
problem on subsequent requests to the application, they just work after that fine.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=14

From hilligsoe on April 25, 2008 15:29:23

What steps will reproduce the problem? 1. Install Passenger
2. create a rails app and let Passenger serve it
3. add the following to the view somewhere: <%=h id %>
4. Fire up your browser and have a look at that page.

What is the expected output?
uid, gid and groups of the user owning the rails app

What do you see instead?
uid and gid of the user owning the rails app, but the groups which root belongs to. What version of the product are you using? On what operating system? 1.0.1 on Gentoo Linux x86_64 Please provide any additional information below. Problem started showing up as I tried to run CruiseControl.rb under Passenger. It failed to run the build process automatically
from CC.rb since it failed to run a subversion checkout because of no access to /root/.subversion/auth (the initial checkout was
NOT made by root) - Not sure thats related though...

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=39

From erbmicha on April 15, 2008 15:38:48

What steps will reproduce the problem? 1. gem install passenger
2. passenger-install-apache2-module What is the expected output? What do you see instead? Installation instructions for required software

• To install Apache 2 development headers:
  Please run yum install httpd-devel as root.
• To install Apache Portable Runtime (APR) development headers:
  Please run yum install apr-devel as root.

can be changed to:

• To install Apache 2 development headers and Apache Portable Runtime (APR) development
  headers:
  Please run up2date -i httpd-devel as root. What version of the product are you using? On what operating system? Passenger 1.0.0 - RHEL 4 Please provide any additional information below.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=21

From koziarski on April 26, 2008 06:12:33

What steps will reproduce the problem? 1. Enable RailsAllowModRewrite
2. Remove crufty-old rails rules What is the expected output? What do you see instead? I expect to see my blog's homepage, instead I see either a directory
listing or a permissions error depending on whether Options -Indexes is
specified. What version of the product are you using? On what operating system? 1.0.1 on ubuntu.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=40

From albert.ramstedt on April 12, 2008 14:33:49

What steps will reproduce the problem? 1. add the following inside the block in environment.rb:
config.action_controller.page_cache_directory = RAILS_ROOT+"/public/cache/"
2. add some page caching directives on a page
3. load page What is the expected output? What do you see instead? It is supposed to write to the page_cache_directory, but instead it writes
to the default /public directory. What version of the product are you using? On what operating system? passenger (1.0.1), Linux Debian Sarge, apache 2.0.54-5sarge2 Please provide any additional information below. If this really is a bug in passenger, and is adressed, maybe having it
serve the pages from the cache dir is something relevant too. To do that
now I have to use rewrite directives.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=9

From albert.ramstedt on April 30, 2008 01:32:21

What steps will reproduce the problem? 1. Setup rails application with rails 1.1.6 in vendor
2. Use the Pagination class
3. Get error What is the expected output? What do you see instead? I expect it to not throw error. instead i get:

NameError (uninitialized constant Pagination):
/vendor/rails/activesupport/lib/active_support/dependencies.rb:123:in
`const_missing' What version of the product are you using? On what operating system? 1.0.3, Lunix debian sarge Please provide any additional information below. Works with mongrel.

Full trace:

/vendor/rails/activesupport/lib/active_support/dependencies.rb:123:in

const_missing' /app/controllers/public_controller.rb:256:inpaginate_published'
/app/controllers/public_controller.rb:198:in film' /vendor/rails/actionpack/lib/action_controller/base.rb:941:insend'
/vendor/rails/actionpack/lib/action_controller/base.rb:941:in
perform_action_without_filters' /vendor/rails/actionpack/lib/action_controller/filters.rb:368:in perform_action_without_benchmark'
/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:69:in
perform_action_without_rescue' /usr/local/lib/ruby/1.8/benchmark.rb:293:inmeasure'
/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:69:in
perform_action_without_rescue' /vendor/rails/actionpack/lib/action_controller/rescue.rb:82:in passenger_orig_perform_action'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/request_handler.rb:145:in
perform_action' /vendor/rails/actionpack/lib/action_controller/base.rb:408:insend'
/vendor/rails/actionpack/lib/action_controller/base.rb:408:in
process_without_filters' /vendor/rails/actionpack/lib/action_controller/filters.rb:377:in process_without_session_management_support'

/vendor/rails/actionpack/lib/action_controller/session_management.rb:117:in
process' /vendor/rails/railties/lib/dispatcher.rb:38:indispatch'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/request_handler.rb:304:in
`process_request'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/request_handler.rb:180:in
`main_loop'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/application_spawner.rb:320:in
`start_request_handler'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/application_spawner.rb:282:in
`handle_spawn_application'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/application_spawner.rb:280:in
`fork'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/application_spawner.rb:280:in
`handle_spawn_application'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/application_spawner.rb:278:in
`fork'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/application_spawner.rb:278:in
`handle_spawn_application'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:291:in
`send'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:291:in
`main_loop'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:147:in
`start_synchronously'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:114:in
`start'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:108:in
`fork'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:108:in
`start'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/application_spawner.rb:147:in
`start'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/framework_spawner.rb:278:in
`handle_spawn_application'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/framework_spawner.rb:273:in
`synchronize'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/framework_spawner.rb:273:in
`handle_spawn_application'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:291:in
`send'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:291:in
`main_loop'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:147:in
`start_synchronously'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:114:in
`start'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:108:in
`fork'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:108:in
`start'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/framework_spawner.rb:104:in
`start'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/spawn_manager.rb:106:in
`spawn_application'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/spawn_manager.rb:102:in
`synchronize'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/spawn_manager.rb:102:in
`spawn_application'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/spawn_manager.rb:183:in
`handle_spawn_application'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:291:in
`send'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:291:in
`main_loop'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:147:in
`start_synchronously'

/usr/local/lib/ruby/gems/1.8/gems/passenger-1.0.3/bin/passenger-spawn-server:32

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=42

From adam.q.salter on April 12, 2008 12:50:34

In order for mod_rails to be deployed in shared hosting environments it
needs to better respect currect shared hosting evironments...

The simplest way to do this would be to allow mod_rails to be configured
through .htaccess files

mod_rails would be 'off' by default, unless turned on by .htaccess. This
would allow current shared hosting providers to work exactly the same as
before.

The configuration would also be relative to current directory, so
RailsBaseURI would be '.' or 'required_dir' instead of '/required_dir'

e.g.

RailsENV staging
RailsBaseURI .

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=7

From jim.zajkowski on April 11, 2008 23:18:52

What steps will reproduce the problem? 1. Built a minimal CentOS 5 VM, installed gcc, gcc-c++, httpd, httpd-devel, ruby and rubygems.
2. While compiling passenger, linking fails because libuuid not installed.

Solution is to install e2fsprogs-devel. Ideally this should be checked for.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=5

From honglilai on April 22, 2008 20:36:51

A packager's guide should be written for Linux distributors who wish to
create packages for Passenger.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=35

From albert.ramstedt on April 29, 2008 23:02:09

What steps will reproduce the problem? 1. freeze any version of rails < 1.2 into vendor
2. start rails
3. watch it go boom What is the expected output? What do you see instead? I expect it to start, it fails. What version of the product are you using? On what operating system? passenger 1.0.2 Please provide any additional information below. I get:
undefined method `alias_method_chain' for Rails::Initializer:Class, because
this method was introduced into 1.2 branch of rails.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=41

From salisan on April 12, 2008 13:11:20

Rails will fail to load if the apache user lacks read permission to to
public/ or config/environment.rb.

When this happens the somewhat cryptic message:
"Passenger thinks that the Rails application's "public" directory is
"/www/path/public", but it doesn't seem to be valid."

Will be displayed. The documentation should note that the apache user needs
read access to these files or the message should be changed to something a
bit less cryptic.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=8

From brunchboy on April 16, 2008 22:58:38

What steps will reproduce the problem? 1. I ran sudo gem install passenger, which seemed to work fine.
2. I then ran sudo /var/lib/gems/1.8/bin/passenger-install-apache2-module, which failed (see
below)
3. I tried sudo gem update, followed by reattempting to install the module, which failed with a
different error (also see below).
4. Based on a posting in the discussion thread, I tried downloading the passenger tarball and
installing the module from that, which seemed to work. I still don't know why the gem version
does not work. What is the expected output? What do you see instead? I would expect to see an attempt to build the apache module, instead I saw the following output:

slice:~> sudo /var/lib/gems/1.8/bin/passenger-install-apache2-module
/var/lib/gems/1.8/gems/activesupport-1.4.2/lib/active_support/dependencies.rb:422:in
remove_const': cannot remove Object::ConsoleTextTemplate (NameError) from /var/lib/gems/1.8/gems/activesupport- 1.4.2/lib/active_support/dependencies.rb:422:insend'
from /var/lib/gems/1.8/gems/activesupport-
1.4.2/lib/active_support/dependencies.rb:422:in remove_constant' from /var/lib/gems/1.8/gems/activesupport- 1.4.2/lib/active_support/dependencies.rb:368:innew_constants_in'
from /var/lib/gems/1.8/gems/activesupport-
1.4.2/lib/active_support/dependencies.rb:368:in each' from /var/lib/gems/1.8/gems/activesupport- 1.4.2/lib/active_support/dependencies.rb:368:innew_constants_in'
from /var/lib/gems/1.8/gems/activesupport-
1.4.2/lib/active_support/dependencies.rb:488:in `load'
from /var/lib/gems/1.8/bin/passenger-install-apache2-module:18

After updating my gems, trying again produced this error:

slice:~> sudo /var/lib/gems/1.8/bin/passenger-install-apache2-module
/var/lib/gems/1.8/gems/activesupport-2.0.2/lib/active_support/dependencies.rb:263:in
load_missing_constant': uninitialized constant Dependencies::GCC (NameError) from /var/lib/gems/1.8/gems/activesupport- 2.0.2/lib/active_support/dependencies.rb:453:inconst_missing'
from /var/lib/gems/1.8/gems/passenger-1.0.1/bin/passenger-install-apache2-module:39
from /var/lib/gems/1.8/gems/activesupport-
2.0.2/lib/active_support/dependencies.rb:489:in load' from /var/lib/gems/1.8/gems/activesupport- 2.0.2/lib/active_support/dependencies.rb:489:inload'
from /var/lib/gems/1.8/gems/activesupport-
2.0.2/lib/active_support/dependencies.rb:342:in new_constants_in' from /var/lib/gems/1.8/gems/activesupport- 2.0.2/lib/active_support/dependencies.rb:489:inload'
from /var/lib/gems/1.8/bin/passenger-install-apache2-module:18 What version of the product are you using? On what operating system? Version 1.0.1, on Slicehost VPS Debian Etch/4.0 (uname -a yields: Linux slice.brunchboy.com
2.6.16.29-xen #1 SMP Sun Sep 30 04:00:13 UTC 2007 x86_64 GNU/Linux) Please provide any additional information below. If there's anything else that would help, feel free to ask for more information on the discussion
list; I've signed up.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=24

From albert.ramstedt on May 01, 2008 21:48:13

What steps will reproduce the problem? 1. Use Rails 1.0.0 (in my case)
2. Start app
3. See it complain about VERSION What is the expected output? What do you see instead? No worka What version of the product are you using? On what operating system? 1.0.3, Linux Please provide any additional information below. Since Rails::VERSION was named Rails::Version in < 1.1, and also defined in
another place, to have passenger work, it must handle that. It seems to
work with the following code in framework_spawner.rb:266

begin
  if ::Rails::VERSION::MAJOR >= 2
    require 'active_resource'
  else
    require 'action_web_service'
  end
# Means rails < 1.1
rescue NameError
  require 'action_web_service'
end

Maybe solving it a bit more elegantly by actually looking for
Rails::Version would be nicer, but this worked for me

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=48

From xipher1 on April 30, 2008 21:00:47

What steps will reproduce the problem? 1. Install passenger on a 64 bit CentOS5 machine
2. Rinse repeat What is the expected output? What do you see instead? The site throws a 500 error (even rails base site when getting more info) What version of the product are you using? On what operating system? 1.0.3
CentOS release 5 (Final) Please provide any additional information below. This error is in the apache logs;
[3166:Hooks.cpp:400] Processing HTTP request: /
[3153:SpawnManager.h:326] Spawn server died. Attempting to restart it...
[3153:SpawnManager.h:121] Spawn server did not exit in time, killing it...
[3153:SpawnManager.h:131] Spawn server has exited.
[3153:SpawnManager.h:328] Restart seems to be successful.
*** Exception Errno::EBADF in spawn manager (Bad file descriptor -
sendmsg(2)) (process 3724):
from
/usr/lib64/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/utils.rb:201:in
send_fd' from /usr/lib64/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/utils.rb:201:in send_io'
from
/usr/lib64/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/message_channel.rb:199:in
send_io' from /usr/lib64/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/spawn_manager.rb:216:in handle_spawn_application'
from
/usr/lib64/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:291:in
__send__' from /usr/lib64/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:291:in main_loop'
from
/usr/lib64/ruby/gems/1.8/gems/passenger-1.0.3/lib/passenger/abstract_server.rb:147:in
`start_synchronously'
from
/usr/lib64/ruby/gems/1.8/gems/passenger-1.0.3/bin/passenger-spawn-server:32
[Wed Apr 30 14:52:05 2008] [error] [client XX.XX.XX.XX] *** Unexpected
error in Passenger: Cannot spawn application '[SITE DIRECTORY]': Could not
receive the spawned application's owner pipe from the spawn server: No
valid file descriptor received.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=43

From dallass on April 24, 2008 02:19:11

What steps will reproduce the problem? 1. Remove the LoadModule line from the httpd.conf
2. restart apache. This must be a restart, and not a graceful restart (reload).
3. Put the LoadModule line back into httpd.conf
4. Do a graceful restart (also known as reload), or just a USR1 kill signal. What is the expected output? What do you see instead? Most apache modules will load and unload with a graceful restart so you don't have to take the
server completely down to switch them. mod_passenger requires a restart or two reloads.
Subsequent reloads after the first two will load and unload the module. What version of the product are you using? On what operating system? 1.0.1, Debian Linux (Sarge) Please provide any additional information below. In some testing I noticed mod_fastcgi exhibits this same behavior. Both mod_fastcgi and
mod_passenger spawn separate process managers.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=37

From sanford.barr on April 13, 2008 19:09:52

My hosting provider needs worker MPM support.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=15

From jaramillo.joseph on April 12, 2008 00:15:15

What steps will reproduce the problem? 1. Install Passenger
2. Configure a virtualhost for a Rails app
3. Set the RailsEnv directive to production
4. Set the RAILS_ENV in config/environment.rb to 'development'
5. Load a path that does not exist ( http://myapp.com/does-not-exist ) What is the expected output? What do you see instead? Expected: Rails backtrace for NoMethodError
Instead: Default Rails 404 page. What version of the product are you using? On what operating system? 1.0.1 on Centos 4.5 w/ Apache 2.0

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=6

From nauhaie on April 12, 2008 15:56:11

Or allow a EnforcedRailsUser directive for every virtualhost that would override both
RailsDefaultUser and RailsUserSwitching users.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=10

From [email protected] on April 14, 2008 05:41:24

What steps will reproduce the problem? 1. Install Ruby, Apache 2.2.8 from ports on FreeBSD 7.0
2. Install Passenger via ruby-gems
4. Configure Apache as instructed from 'passenger-install-apache2-module'
5. Start Apache What is the expected output? What do you see instead? Expected to see (in httpd-error.log):

[36970:ApplicationPoolClientServer.h:426] Client 0x8291200: received message: ['setMax', '20']
[36970:ApplicationPoolClientServer.h:426] Client 0x8291200: received message:
['setMaxIdleTime', '120']

However, instead I get:

[Mon Apr 14 15:36:29 2008] [notice] Apache/2.2.8 (FreeBSD) mod_ssl/2.2.8 OpenSSL/0.9.8e
DAV/2 Phusion_Passenger/1.0.1 configured -- resuming normal operations
*** Cannot initialize Passenger: write() failed: Bad file descriptor
(9)[77505:ApplicationPoolClientServer.h:394] Cannot send a file descriptor: Bad file descriptor
(9) --- aborting!
[Mon Apr 14 15:36:29 2008] [notice] seg fault or similar nasty error detected in the parent
process

And the Apache parent process dies, thus Apache does not accept anymore incoming
connections. What version of the product are you using? On what operating system? FreeBSD supertax 7.0-BETA3 FreeBSD 7.0-BETA3 #0: Thu Nov 22 14:59:36 NZDT 2007
root@supertax:/usr/obj/usr/src/sys/GENERIC amd64

Ruby 1.8.6
RubyGems 1.1.1
Passenger 1.0.1
Apache 2.2.8

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=16

From marcin.bodzioch on April 22, 2008 14:06:20

What steps will reproduce the problem? 1. gem install passenger
2. passenger-install-apache2-module
3. build failed with error:

In ext/apache2:

g++ -shared Utils.o Logging.o Configuration.o Hooks.o mod_passenger.o -fPIC
-o mod_passenger.so -lstdc++ -lpthread ../boost/src/libboost_thread.a
-laprutil-1 -lldap -llber -ldb-4.6 -lexpat -lapr-1 -luuid -lcrypt -lpthread
-ldl
/usr/bin/ld: cannot find -luuid
collect2: ld returned 1 exit status
rake aborted!

Software versions:
passenger (1.0.1)
rails (2.0.2)
rake (0.8.1)
OS Fedora 8 x86_64

To solve this issue you have to install e2fsprogs-devel.
It should be in install notes.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=31

From honglilai on April 10, 2008 18:12:13

The RailsEnv configuration option is currently a global option instead of
per-virtual host. Some people have expressed interest in making it
per-virtual host instead, even though they know that RAILS_ENV can be
changed in environment.rb.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=1

From mazdakr on April 16, 2008 16:22:50

Due to a conflict between and action_web_service and some custom code, we have disabled it in our
code, but the preload_rails function in framework_spawner loads every component of Rails!

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=22

From netzdamon on April 19, 2008 05:24:30

What steps will reproduce the problem? 1. Write mod_rewrite rule to display a directory listing inside site.com/junk/
2. Visit http://www.site.com/junk/ 3. Rails has a error about missing route. What is the expected output? What do you see instead? Rewrite rule should be displaying a listing of the files in /junk/, instead
rails is insisting on looking in my routes.rb What version of the product are you using? On what operating system? Pulled from Git April 15th, for page_caches fix. Please provide any additional information below. #/path/to/sites/public/.htaccess
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} stuff.site.com [NC]
RewriteCond %{REQUEST_URI} !^/junk/.*
RewriteRule ^(.*)$ /junk/$1 [QSA,L]

/path/to/sites/public/junk/.htaccess

RewriteBase /junk/
Options +Indexes
IndexOptions +FancyIndexing +FoldersFirst
IndexIgnore

I think this is mod_rails because after a lot of swearing at apache I
commented out my mod_rails configuration in apache and it immediately
started to work.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=28

From kivanio on April 24, 2008 00:34:24

Stack trace is shown here: http://groups.google.com/group/phusion-passenger/t/59fb5fbe1537d23d?hl=en What steps will reproduce the problem? 1. All night at 00:00 when syslog rotate logs
2. Sometimes when i restart apache2 manually What is the expected output? What do you see instead? The apache just freeze and don't show errors in log. What version of the product are you using? On what operating system? Phusion version of git repository in: Sun Apr 20 12:44:26 2008 +0200

commit 81a4850
Author: Hongli Lai (Phusion) [email protected]
Date: Sun Apr 20 12:44:26 2008 +0200

SO:
FreeBSD server.org.br 6.3-RELEASE-p1 FreeBSD 6.3-RELEASE-p1 #0: Wed Feb 13 02:56:56 UTC
2008

Server version: Apache/2.2.8 (FreeBSD)
Server built: Jan 30 2008 07:50:10
Server's Module Magic Number: 20051115:11
Server loaded: APR 1.2.12, APR-Util 1.2.12
Compiled using: APR 1.2.12, APR-Util 1.2.12
Architecture: 32-bit
Server MPM: Prefork
threaded: no
forked: yes (variable process count)
Server compiled with....
-D APACHE_MPM_DIR="server/mpm/prefork"
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses enabled)
-D APR_USE_FLOCK_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=128
-D HTTPD_ROOT="/usr/local"
-D SUEXEC_BIN="/usr/local/bin/suexec"
-D DEFAULT_PIDLOG="/var/run/httpd.pid"
-D DEFAULT_SCOREBOARD="/var/run/apache_runtime_status"
-D DEFAULT_LOCKFILE="/var/run/accept.lock"
-D DEFAULT_ERRORLOG="/var/log/httpd-error.log"
-D AP_TYPES_CONFIG_FILE="etc/apache22/mime.types"
-D SERVER_CONFIG_FILE="etc/apache22/httpd.conf" Please provide any additional information below. in group: http://groups.google.com/group/phusion-passenger/t/59fb5fbe1537d23d?hl=en

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=36

From kennonballou on April 24, 2008 15:16:43

What steps will reproduce the problem? 1. In environment.rb, set config.action_controller.page_cache_directory = RAILS_ROOT +
"/public/cache/"
2. Turn on page caching for a page, for instance your index page
3. Index.html is generated in /public instead of /public/cache What is the expected output? What do you see instead? Running under Mongrel, index.html is created in public/cache What version of the product are you using? On what operating system? passenger-1.0.1, Debian etch, Apache 2.2, Ruby 1.8, Rails 2.0.2

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=38

From fannar on May 01, 2008 17:49:50

If mod_rewrite is enabled and not used in the VirtualHost, Passenger won't start my Rails
application and nothing is in the Apache's error.log.

Disabling mod_rewrite and everything works fine.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=46

From xipher1 on May 01, 2008 21:56:37

What steps will reproduce the problem? 1. Install passenger
2. Set a different RAILS_ENV in environment.rb
3. luanch What is the expected output? What do you see instead? The log file of #{RAILS_ENV}.log should be written, instead the system wide
setting is used (default of production) What version of the product are you using? On what operating system? 1.0.3, 1.0.4 both have this issue. CentOS 5 64bit

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=49