Rails Passenger 500 Internal Server Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and rails completed 500 internal server error policies of this site About Us Learn more about Stack Overflow the
Rails Internal Server Error
company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up 500 Internal Server Error with Rails Production up vote 2 down vote favorite I recently uploaded some new files to my production server (and overriding the old ones) and am now getting 500 Internal Server Error. The server is running phusion passenger (even though I am not getting that error message anymore) and in my local test environment everything seems to be working fine. Here is the site: http://www.pandonews.com/ When I looked in my apache log i see this error: [ pid=3106 thr=140057117177664 file=ext/apache2/Hooks.cpp:884 time=2013-09-01 17:37:24.84 ]: Unexpected error in mod_passenger: Cannot spawn application '/var/www/feedme': The spawn server died unexpectedly, and restarting it failed. Backtrace: in 'virtual Passenger::SessionPtr Passenger::ApplicationPool::Client::get(const Passenger::PoolOptions&)' (Client.h:742) in 'Passenger::SessionPtr Hooks::getSession(const Passenger::PoolOptions&)' (Hooks.cpp:312) in 'int Hooks::handleRequest(request_rec*)' (Hooks.cpp:585) I have no idea what the problem is. It has been running fine up until now. I don't really know where to start in order to fix this. I tried running gem passenger install again but nothing happened. Recent activities: Installed pg gem (but removed it from gem file after deciding to stay with sqlite3 for now) the yml file should be ok... Tried running bundle update on server and locally but it keeps hanging Changed some javascript and css files... Tried resetting the server with RAILS_ENV=production rake:db reset - no change! EDIT: when running rails s production i get the following error: /home/otto/.rvm/gems/ruby-1.9.3-p392/gems/activesupport-3.2.7/lib/active_support/dependencies.rb:251:in `require': cannot load such file -- rack/handler/production (LoadError) from /home/otto/.rvm/gems/ruby-1.9.3-p392/gems/activesupport-3.2.7/lib/active_support/dependencies.rb:251:in `block in require' from /home/otto/.rvm/gems/ruby-1.9.3-p392/gems/activesupport-3.2.7/lib/active_support/dependenci
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How to properly diagnose a 500 error (Rails, Passenger, Nginx, Postgres) up vote 3 down vote favorite 2 I'm http://stackoverflow.com/questions/18561245/500-internal-server-error-with-rails-production having a real tough time diagnosing a 500 error from my application running in production. I've had it working before, but after re-deploying via Capastrano I am unable to get it going. Here are the facts: The server is setup with nginx + passenger, and I'm using PostgreSQL. Static assets are working properly, as in I'm able to access them just fine in a browser. I can access the rails console via RAILS_ENV=production http://stackoverflow.com/questions/9970028/how-to-properly-diagnose-a-500-error-rails-passenger-nginx-postgres bundle exec rails console and perform Active Record actions (like retrieving data from the db). Within console, I can run app.get("/"), which returns a 500 error as well (after first showing the query that was run to load the model). The production.log file is never written to. I've set permissions 777 on it just for the hell of it. I've also set the log level to :debug with nothing to show for it. The nginx log (which passenger also uses) shows no indication of errors, it just notifies about cache misses. Because nothing of use is being logged, I have no idea what to do here. I've tried setting full permission on the entire app directory with no help. Restarted the server multiple times, nothing. The database is there and rails can clearly communicate with it. I'm not sure what I did to get it to run the first time around. I just don't know why rails isn't outputting anything to the log. ruby-on-rails ruby-on-rails-3 nginx passenger capistrano share|improve this question asked Apr 2 '12 at 1:49 Brian 1,95942247 add a comment| 3 Answers 3 active oldest votes up vote 6 down vote accepted Okay, I figured this out. The app ran fine in development mode, so I knew something production-specific was screwing it up. I we
Sign in Pricing Blog Support Search GitHub This repository Watch 137 Star 3,598 Fork 452 phusion/passenger Code https://github.com/phusion/passenger/issues/332 Issues 156 Pull requests 5 Projects 0 Wiki Pulse Graphs New issue Apache reports 500 Internal Server Error - Permission denied #332 Closed FooBarWidget opened this Issue May 29, 2014 · 7 comments Labels None yet Milestone No milestone Assignees No one assigned 1 participant Phusion B.V. member FooBarWidget commented internal server May 29, 2014 From oliver.maurhart@gmx.net on March 30, 2009 15:06:00 I've installed Phusion Passenger 2.1.2 on a Debian Lenny. My Apache conf contains a VirtualHost within --->snip---> DocumentRoot /var/www/SOME-FOLDER