Passenger 500 Error Log
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 rails 500 error page Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation rails 500 error log Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like rails internal server error 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 having a real tough time
Passenger Logs
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 bundle exec rails console and perform Active rails 500 internal server error 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,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 cac
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 http://stackoverflow.com/questions/9970028/how-to-properly-diagnose-a-500-error-rails-passenger-nginx-postgres Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Rails 500 errors are not handled by rails and log to apache error log up vote 0 down vote favorite Everytime there is a 500 error on my test http://stackoverflow.com/questions/36597307/rails-500-errors-are-not-handled-by-rails-and-log-to-apache-error-log website I receive the errer "Incomplete response received from application" (coming from Apache or Passenger I guess), and the error gets logged to apache/error.log # environments/test.rb Rails.application.configure do config.cache_classes = true config.eager_load = false config.public_file_server.enabled = true config.public_file_server.headers = { 'Cache-Control' => 'public, max-age=3600' } config.consider_all_requests_local = true config.action_controller.perform_caching = false config.action_dispatch.show_exceptions = false config.action_controller.allow_forgery_protection = false config.action_mailer.perform_caching = false config.action_mailer.raise_delivery_errors = false config.action_mailer.default_url_options = { host: ENV['TEST_HOST'], port: ENV['TEST_PORT'] } config.action_mailer.delivery_method = :ses config.active_support.deprecation = :stderr CarrierWave.configure do |config| config.permissions = 0666 config.directory_permissions = 0777 config.storage = :file end end Nothing else that seems relevant in other initializers, app.rb or env.rb Apache conf
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 Us Learn more about Stack Overflow the company Business http://serverfault.com/questions/316103/problem-with-apache-passenger-500-error-where-to-look Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question 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 up and rise to the top problem with Apache / Passenger - 500 error - where 500 error to look? up vote 1 down vote favorite I installed passenger with rails 1.9.2 in a rvm but I'm getting errors when trying to load anything. (We're sorry but something went wrong). I'm able to load a txt file out of the public directory. It looks like passenger is working: jon@ve:~$ apache2ctl -t -D DUMP_MODULES Loaded Modules: ... passenger_module (shared) Syntax OK jon@ve:~$ In the top level apache error log, I see the non-descript: cache: [GET 500 error log /jt] miss [Tue Sep 27 13:36:50 2011] [notice] caught SIGTERM, shutting down The vhost container is: