Passenger 500 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 policies of this site About Us Learn more about Stack Overflow the company Business Learn more rails 500 error page about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users rails 500 error no log Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping rails 500 error log 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 having a real tough time diagnosing a 500 error
Rails Internal Server 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 bundle exec rails console and perform Active Record actions (like retrieving data from rails 500 internal server error 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,95442247 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 went into config/environments/production.rb and changes these settings: # Full error reports are disabled and caching is turned on config.consider_all_requests_local = false # changed from true config.acti
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 http://stackoverflow.com/questions/9970028/how-to-properly-diagnose-a-500-error-rails-passenger-nginx-postgres minute: Sign up 500 internal server error in ruby on rails up vote 1 down vote favorite I am deploying my ruby 3.2.6 project using passenger 3.0.17 . My httpd.conf file is:
Start 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 http://serverfault.com/questions/423705/500-error-with-deploying-rails-application-via-apache2passenger Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question https://community.webfaction.com/questions/5138/check-rails-app-status-getting-internal-server-error-500 and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted 500 error up and rise to the top 500 error with deploying rails application via apache2+passenger up vote 0 down vote favorite I finally completed my own app, so the only work left is deploying the app. I'm using Ubuntu 10.04 and apache2(installed by apt-get), so I'm trying to deploy through passenger. I installed passenger gem like this: sudo gem install passenger rvmsudo passenger-install-apache2-module and I configured apache settings rails 500 error as what the installation message says. I added below lines in the middle of /etc/apache2/apache2.conf file. LoadModule passenger_module /home/admin/.rvm/gems/ruby-1.9.3-p194/gems/passenger-3.0.17/ext/apache2/mod_passenger.so PassengerRoot /home/admin/.rvm/gems/ruby-1.9.3-p194/gems/passenger-3.0.17 PassengerRuby /home/admin/.rvm/wrappers/ruby-1.9.3-p194/ruby and, I appended below lines in /etc/apache2/sites-available/default file.
(https://github.com/michaeldv/fat_free_crm). I installed a new Rails application (Rails 3.0.5 (nginx 0.8.54/Passenger 3.0.3/Ruby Enterprise Edition 1.8.7)) configured nginx to point to the application folder fat_free_crm created a new subdomain and website using that application. But now I get an internal server Error when i try to access the application How can I investigate the status of the rails app and find out about the error? Thanks (I tried to do wget localhost: