I built an api-only rails app using rails-api. It works great locally. However, when I deploy it to heroku, it produces error saying We're sorry, but something went wrong. If you are the application owner check the logs for more information..
I then checked logs with command heroku logs in CLI:
2016-01-26T22:11:39.472621+00:00 app[web.1]: Puma starting in single mode...
2016-01-26T22:11:39.472645+00:00 app[web.1]: * Version 2.15.3 (ruby 2.0.0-p648), codename: Autumn Arbor Airbrush
2016-01-26T22:11:39.472647+00:00 app[web.1]: * Min threads: 5, max threads: 5
2016-01-26T22:11:39.472647+00:00 app[web.1]: * Environment: production
2016-01-26T22:11:40.839892+00:00 app[web.1]: * Listening on tcp://0.0.0.0:12329
2016-01-26T22:11:40.840054+00:00 app[web.1]: Use Ctrl-C to stop
2016-01-26T22:11:40.994291+00:00 heroku[web.1]: State changed from starting to up
2016-01-26T22:11:42.865549+00:00 heroku[router]: at=info method=GET path="/" host=hereze.herokuapp.com request_id=2823dd98-073a-40b5-9faa-1caed3ed263f fwd="89.166.7.101" dyno=web.1 connect=0ms service=38ms status=404 bytes=1744
2016-01-26T22:11:50.101468+00:00 heroku[router]: at=info method=GET path="/reviews" host=hereze.herokuapp.com request_id=2d0d04a6-90c5-4ae7-84a8-2fd1e6287ea3 fwd="89.166.7.101" dyno=web.1 connect=1ms service=16ms status=500 bytes=1669
2016-01-26T22:12:41.819043+00:00 heroku[router]: at=info method=GET path="/reviews" host=hereze.herokuapp.com request_id=854512e4-7a19-4453-9254-2ce09472b5bb fwd="89.166.7.101" dyno=web.1 connect=1ms service=36ms status=500 bytes=1669
But I don't see anything wrong in the logs, can you help me out? Thank you.
You can do Cntrl+F and then search for error. The code you listed does not include any errors.
But if it is working locally but not in Heroku you probably have forgotten to run
heroku run rake db:migrate
or
heroku run rake db:seed
Related
I try to run my simple Web-App as Docker Container within Heroku.
When build and run the container locally all works fine.
But on accessing the generated endpoint https://html5-landingpage-buddah.herokuapp.com/ Heroku responses with HTTP 400 Bad Request and the message "Not authoritative"
Logs inside Heroku don't help much:
2020-09-19T14:45:45.269487+00:00 heroku[router]: at=info method=GET path="/" host=html5-landingpage-buddah.herokuapp.com request_id=5f07ea7e-d925-4fbe-b7ba-29387a3284cc fwd="XX.XX.XX.XXX" dyno=web.1 connect=1ms service=1ms status=400 bytes=212 protocol=https
I did a research for the error but found no helpful information.
Also re-creating the App in Heroku, renaming the URL and moving the App to another Region did not help.
Here is the log from restart to the first request on the web app:
2021-06-15T17:11:36.977277+00:00 heroku[web.1]: Starting process with command `./app`
2021-06-15T17:11:39.852345+00:00 app[web.1]: [main] INFO de.clique.westwood.example.html5.landingpage.buddah.App - Server started on port 54225
2021-06-15T17:11:39.852374+00:00 app[web.1]: [main] INFO de.clique.westwood.example.html5.landingpage.buddah.App - Serving albums from ./static/album
2021-06-15T17:11:41.363857+00:00 heroku[web.1]: State changed from starting to up
2021-06-15T17:11:48.162254+00:00 heroku[router]: at=info method=GET path="/" host=html5-landingpage-buddah.herokuapp.com request_id=85c642cb-a48d-41ac-89e1-7a520749e9bc fwd="94.31.82.142" dyno=web.1 connect=1ms service=4ms status=421 bytes=219 protocol=https
2021-06-15T17:11:48.275223+00:00 heroku[router]: at=info method=GET path="/" host=html5-landingpage-buddah.herokuapp.com request_id=406e9e77-f40e-47b9-a33b-af0af5b8f171 fwd="94.31.82.142" dyno=web.1 connect=1ms service=3ms status=421 bytes=219 protocol=https
2021-06-15T17:11:48.520876+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=html5-landingpage-buddah.herokuapp.com request_id=d3782734-765c-45f1-98a8-04e2098e7267 fwd="94.31.82.142" dyno=web.1 connect=1ms service=4ms status=421 bytes=219 protocol=https
2021-06-15T17:11:48.906097+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=html5-landingpage-buddah.herokuapp.com request_id=79e4404f-e505-4c16-9778-9f72882d74be fwd="94.31.82.142" dyno=web.1 connect=1ms service=4ms status=421 bytes=219 protocol=https
The error Not Authoritative simply means that Heroku is unable to redirect the traffic from the said domain name to your application.
According to Heroku,
The web process must listen for HTTP traffic on $PORT, which is set by Heroku. EXPOSE in Dockerfile is not respected, but can be used for local testing. Only HTTP requests are supported.
You will need to replace your EXPOSE and ENTRYPOINT as such
CMD [ "sh", "-c", "java -jar ./app --bind 0.0.0.0:$PORT" ]
I have already searched around StackOverflow and have been trying for a while to solve this, but none of them works.
Although I reordered the line in application.js and set precompile in production.rb to "true", it still does not work when pushed to Heroku. Locally, however, it is wokring fine.
Please take a look at my project file --> https://github.com/star747jet/sbadmin2.1.git
I'm using ruby 2.2.4 and rails 4.2.6 on Ubuntu 14.04. Thanks
Update:
I reorder the line in application.js to be
//= require jquery
//= require bootstrap
//= require bootstrap_sb_admin_base_v2
and publish to Heroku
Heroku logs after publish (I think there is no error here)
2016-05-02T04:41:14.505700+00:00 heroku[api]: Enable Logplex by tanapon.aree#gmail.com
2016-05-02T04:41:14.505700+00:00 heroku[api]: Release v2 created by tanapon.aree#gmail.com
2016-05-02T04:44:19.410522+00:00 heroku[api]: Release v3 created by tanapon.aree#gmail.com
2016-05-02T04:44:19.410522+00:00 heroku[api]: Set LANG, RACK_ENV, RAILS_ENV, RAILS_SERVE_STATIC_FILES, SECRET_KEY_BASE config vars by tanapon.aree#gmail.com
2016-05-02T04:44:20.107984+00:00 heroku[api]: Attach DATABASE (#ref:postgresql-contoured-49654) by tanapon.aree#gmail.com
2016-05-02T04:44:20.107984+00:00 heroku[api]: Release v4 created by tanapon.aree#gmail.com
2016-05-02T04:44:20.562428+00:00 heroku[api]: Scale to web=1 by tanapon.aree#gmail.com
2016-05-02T04:44:20.562897+00:00 heroku[api]: Deploy 58726b3 by tanapon.aree#gmail.com
2016-05-02T04:44:20.562897+00:00 heroku[api]: Release v5 created by tanapon.aree#gmail.com
2016-05-02T04:44:20.939703+00:00 heroku[slug-compiler]: Slug compilation started
2016-05-02T04:44:20.939708+00:00 heroku[slug-compiler]: Slug compilation finished
2016-05-02T04:44:23.584547+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 18464 -e production`
2016-05-02T04:44:27.214026+00:00 app[web.1]: [2016-05-02 04:44:27] INFO WEBrick 1.3.1
2016-05-02T04:44:27.214047+00:00 app[web.1]: [2016-05-02 04:44:27] INFO ruby 2.2.4 (2015-12-16) [x86_64-linux]
2016-05-02T04:44:27.214304+00:00 app[web.1]: [2016-05-02 04:44:27] INFO WEBrick::HTTPServer#start: pid=3 port=18464
2016-05-02T04:44:27.741557+00:00 heroku[web.1]: State changed from starting to up
2016-05-02T04:48:33.746996+00:00 heroku[api]: Starting process with command `bundle exec rake db:migrate` by tanapon.aree#gmail.com
2016-05-02T04:48:37.688192+00:00 heroku[run.6174]: Awaiting client
2016-05-02T04:48:37.768392+00:00 heroku[run.6174]: Starting process with command `bundle exec rake db:migrate`
2016-05-02T04:48:37.919170+00:00 heroku[run.6174]: State changed from starting to up
2016-05-02T04:48:45.675830+00:00 heroku[run.6174]: Process exited with status 0
2016-05-02T04:48:45.696153+00:00 heroku[run.6174]: State changed from up to complete
Heroku logs after do "heroku run rake assets:precompile
" and reload the webpage.(all six line below begin with red colr timestamp)
2016-05-02T04:53:40.727583+00:00 heroku[router]: at=info method=GET path="/" host=seastest.herokuapp.com request_id=2940cf64-16c8-48ea-ae87-7113bd76315f fwd="58.11.221.244" dyno=web.1 connect=1ms service=10ms status=302 bytes=994
2016-05-02T04:53:41.143685+00:00 heroku[router]: at=info method=GET path="/users/sign_in" host=seastest.herokuapp.com request_id=0907e800-2894-4c56-b674-8c3760b89794 fwd="58.11.221.244" dyno=web.1 connect=1ms service=10ms status=200 bytes=6010
2016-05-02T04:53:41.517598+00:00 heroku[router]: at=info method=GET path="/assets/application-7a9d5ae8202aacde4376876c4b8f86770fdb15d3cb2f361e5504142bbe04c9b1.css" host=seastest.herokuapp.com request_id=fcc95013-635b-4b8f-a680-f1c2f4ed3077 fwd="58.11.221.244" dyno=web.1 connect=1ms service=4ms status=200 bytes=31608
2016-05-02T04:53:42.124687+00:00 heroku[router]: at=info method=GET path="/assets/application-eb16686e7fa82584bf03646c97a53b5a11d7aaa29cc889d8a18ab556c25b2ee8.js" host=seastest.herokuapp.com request_id=8581be8f-a249-49ec-b59a-f243a9fb7622 fwd="58.11.221.244" dyno=web.1 connect=1ms service=11ms status=200 bytes=141559
2016-05-02T04:53:44.312552+00:00 heroku[router]: at=info method=GET path="/images/banner.png" host=seastest.herokuapp.com request_id=ec07c53f-a46b-45a1-8492-4b00d55e3be9 fwd="58.11.221.244" dyno=web.1 connect=1ms service=18ms status=200 bytes=263984
2016-05-02T04:53:44.505642+00:00 heroku[router]: at=info method=GET path="/assets/fontawesome-webfont-v=4.2.0.woff" host=seastest.herokuapp.com request_id=ea63ce17-70d8-412b-9ff0-e2cc806431a4 fwd="58.11.221.244" dyno=web.1 connect=1ms service=175ms status=200 bytes=65845
ve been working on Ruby on Rails application development using NitrousIO for my environment and Heroku for Deployment. For some of the modules I could successfully deploy on Heroku and it's working fine but for some of the modules, it says We're sorry, but something went wrong.
I've been all the steps like heroku run rake db:migrate after pushing the latest code to heroku but no success But on NitrousIO, everything works perfect
What are the ways now to reset my db on Heroku such that It can work for all the modules without issues. Guide/Point me the step-by-step procedure please
Is there only db reset option to get going or do we have any intermediate solution which gets me out of this situation ?
These are my Heroku Logs with heroku logs -n 250
action#rksrailszone-182221:~/enterpriseape(nesting-purchases)$ heroku logs -n 250
2015-01-16T16:35:08.590482+00:00 heroku[web.1]: Unidling
2015-01-16T16:35:08.591399+00:00 heroku[web.1]: State changed from down to starting
2015-01-16T16:35:12.002231+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 46010 -e production`
2015-01-16T16:35:16.619546+00:00 app[web.1]: [2015-01-16 16:35:16] INFO WEBrick 1.3.1
2015-01-16T16:35:16.619962+00:00 app[web.1]: [2015-01-16 16:35:16] INFO WEBrick::HTTPServer#start: pid=3 port=46010
2015-01-16T16:35:16.619570+00:00 app[web.1]: [2015-01-16 16:35:16] INFO ruby 2.0.0 (2014-11-13) [x86_64-linux]
2015-01-16T16:35:16.950487+00:00 heroku[web.1]: State changed from starting to up
2015-01-16T16:35:17.990652+00:00 heroku[router]: at=info method=GET path="/" host=enterpriseape-ramakballa.herokuapp.com request_id=6a0355dc-73fd-4b10-9a2e-066ae51a403a fwd="49.205.144.212" dyno=web
.1 connect=2ms service=115ms status=200 bytes=1896
2015-01-16T16:35:24.243086+00:00 heroku[router]: at=info method=GET path="/assets/application-f71602a6cb0cb5ada02d834e1b9e35cb.css" host=enterpriseape-ramakballa.herokuapp.com request_id=6251571f-d5
6c-4af4-bc4a-7bf0b4ea1961 fwd="49.205.144.212" dyno=web.1 connect=2ms service=5817ms status=304 bytes=231
2015-01-16T16:35:24.699601+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=enterpriseape-ramakballa.herokuapp.com request_id=0cc95f6f-5255-4345-8f63-e53c43bad31f fwd="49.205.144.21
2" dyno=web.1 connect=1ms service=9ms status=404 bytes=1829
2015-01-16T16:35:50.967577+00:00 heroku[router]: at=info method=GET path="/invoices" host=enterpriseape-ramakballa.herokuapp.com request_id=e8cdea65-e2f0-4a5a-acbd-cbd599a5e8a6 fwd="49.205.144.212"
dyno=web.1 connect=2ms service=108ms status=200 bytes=2765
2015-01-16T16:35:51.378408+00:00 heroku[router]: at=info method=GET path="/assets/application-f71602a6cb0cb5ada02d834e1b9e35cb.css" host=enterpriseape-ramakballa.herokuapp.com request_id=9d2facec-b8
cb-40d5-aebf-264154e5e59e fwd="49.205.144.212" dyno=web.1 connect=2ms service=14ms status=304 bytes=231
action#rksrailszone-182221:~/enterpriseape(nesting-purchases)$
Based on the 'Missing host to link to' error message in your screenshot it looks like you are missing some configuration. The link_to method needs to know the hostname to use to generate the full URL for the given link. You can configure this in each environment file, in this case you need to add something like this to your config/environments/production.rb:
config.action_mailer.default_url_options = { :host => "enterpriseape-ramakballa.herokuapp.com" }
I'm trying to use Rails Admin on heroku. It works perfectly in both production and development, but when I try to access /admin through heroku, the Dashboard renders completely empty(it has the basic Rails Admin scaffolding, but none of my content). The rest of the site is working fine. There are no errors in heroku logs, which look like this:
2013-01-03T09:05:48+00:00 app[web.1]:
2013-01-03T09:05:48+00:00 app[web.1]:
2013-01-03T09:05:48+00:00 app[web.1]: Started GET "/admin/" for 76.93.177.75 at 2013-01-03 09:05:48 +0000
2013-01-03T09:05:48+00:00 app[web.1]: Processing by RailsAdmin::MainController#dashboard as HTML
2013-01-03T09:05:48+00:00 app[web.1]: Rendered vendor/bundle/ruby/1.9.1/gems/rails_admin-0.0.3/app/views/rails_admin/main/dashboard.html.haml within layouts/rails_admin/application (0.3ms)
2013-01-03T09:05:48+00:00 app[web.1]: Rendered vendor/bundle/ruby/1.9.1/gems/rails_admin-0.0.3/app/views/layouts/rails_admin/_secondary_navigation.html.haml (1.3ms)
2013-01-03T09:05:48+00:00 app[web.1]: Rendered vendor/bundle/ruby/1.9.1/gems/rails_admin-0.0.3/app/views/layouts/rails_admin/pjax.html.haml (2.1ms)
2013-01-03T09:05:48+00:00 app[web.1]: Completed 200 OK in 20ms (Views: 17.2ms | ActiveRecord: 1.4ms)
2013-01-03T09:05:48+00:00 heroku[router]: at=info method=GET path=/admin/ host=rocky-oasis-1876.herokuapp.com fwd=76.93.177.75 dyno=web.1 queue=0 wait=0ms connect=12ms service=43ms status=200 bytes=2603
2013-01-03T09:05:48+00:00 heroku[router]: at=info method=GET path=/assets/rails_admin/rails_admin-b54745219c9cfcf789963ed61310c222.css host=rocky-oasis-1876.herokuapp.com fwd=76.93.177.75 dyno=web.1 queue=0 wait=0ms connect=1ms service=29ms status=200 bytes=129747
2013-01-03T09:05:48+00:00 heroku[router]: at=info method=GET path=/assets/rails_admin/rails_admin-713b6f759f0edf80a0c69b3ced027e1e.js host=rocky-oasis-1876.herokuapp.com fwd=76.93.177.75 dyno=web.1 queue=0 wait=0ms connect=1ms service=34ms status=200 bytes=283158
2013-01-03T09:05:49+00:00 heroku[router]: at=info method=GET path=/assets/glyphicons-halflings-f6675c325532ec11a984d58e172b8e2a.png host=rocky-oasis-1876.herokuapp.com fwd=76.93.177.75 dyno=web.1 queue=0 wait=0ms connect=1ms service=7ms status=200 bytes=13826
I'm not sure what else to include, since everything is "working". I am using rails 3.2.9 and
rails_admin 0.0.3, and the up-to-date heroku toolbelt. If anyone has any ideas, I would greatly appreciate the help!
You're not alone. I had this, too, and it seems others have. The solution that worked for me was to upgrade rails_admin. This works because fixes have been committed to rails_admin in later versions; here's a link:
https://github.com/sferik/rails_admin/pull/1184
This pull request went in after version 0.0.3, which you say you are using, so I think upgrading will help you.
bundle update rails_admin
After you do this, remember to commit your Gemfile.lock, precompile assets (if you normally do this, it depends on your set up) and run your tests before you deploy.
I am trying to deploy my Rails web application on Heroku.
I used scaffold to generate two tables. On my machine it all works perfect using SQLite.
I uploaded my app to heroku and now have a weird problem. When I use:
heroku config:add RACK_ENV=development
it works with SQL tables. When I change it back to production it shows:
We're sorry, but something went wrong.
We've been notified about this issue and we'll take a look at it shortly.
I typed in the terminal:
heroku logs
Output:
2011-09-07T13:44:31+00:00 app[web.1]: >> Maximum connections set to 1024
2011-09-07T13:44:31+00:00 app[web.1]: >> Listening on 0.0.0.0:16691, CTRL+C to stop
2011-09-07T13:44:31+00:00 heroku[web.1]: State changed from starting to up
2011-09-07T13:44:32+00:00 app[web.1]: cache: [GET /users] miss
2011-09-07T13:44:32+00:00 heroku[router]: GET falling-winter-505.heroku.com/users dyno=web.1 queue=0 wait=0ms service=193ms status=500 bytes=728
2011-09-07T13:44:47+00:00 app[web.1]: >> Stopping ...
2011-09-07T13:56:25+00:00 app[web.1]: cache: [GET /users] miss
2011-09-07T13:56:25+00:00 heroku[router]: GET falling-winter-505.heroku.com/users dyno=web.1 queue=0 wait=0ms service=26ms status=500 bytes=728
2011-09-07T13:56:25+00:00 heroku[nginx]: 95.26.72.50 - - [07/Sep/2011:06:56:25 -0700] "GET /users HTTP/1.1" 500 728 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:6.0.2) Gecko/20100101 Firefox/6.0.2" falling-winter-505.heroku.com
2011-09-07T15:00:53+00:00 heroku[web.1]: Idling
2011-09-07T15:00:54+00:00 heroku[web.1]: State changed from up to down
2011-09-07T15:00:54+00:00 heroku[web.1]: State changed from down to created
2011-09-07T15:00:54+00:00 heroku[web.1]: State changed from created to starting
2011-09-07T15:00:55+00:00 heroku[web.1]: Stopping process with SIGTERM
2011-09-07T15:00:55+00:00 app[web.1]: >> Stopping ...
2011-09-07T15:00:55+00:00 heroku[web.1]: Process exited
2011-09-07T15:00:59+00:00 heroku[web.1]: Starting process with command `thin -p 8370 -e production -R /home/heroku_rack/heroku.ru start`
2011-09-07T15:01:03+00:00 app[web.1]: >> Thin web server (v1.2.6 codename Crazy Delicious)
2011-09-07T15:01:03+00:00 app[web.1]: >> Maximum connections set to 1024
2011-09-07T15:01:03+00:00 app[web.1]: >> Listening on 0.0.0.0:8370, CTRL+C to stop
2011-09-07T15:01:04+00:00 heroku[web.1]: State changed from starting to up
2011-09-07T16:07:12+00:00 heroku[web.1]: State changed from up to down
2011-09-07T16:07:13+00:00 heroku[web.1]: Stopping process with SIGTERM
2011-09-07T16:07:13+00:00 app[web.1]: >> Stopping ...
2011-09-07T16:07:14+00:00 heroku[web.1]: Process exited
2011-09-07T17:10:28+00:00 heroku[web.1]: Unidling
2011-09-07T17:10:28+00:00 heroku[web.1]: State changed from down to created
2011-09-07T17:10:28+00:00 heroku[web.1]: State changed from created to starting
2011-09-07T17:10:40+00:00 heroku[web.1]: Starting process with command `thin -p 35396 -e production -R /home/heroku_rack/heroku.ru start`
2011-09-07T17:10:44+00:00 app[web.1]: >> Thin web server (v1.2.6 codename Crazy Delicious)
2011-09-07T17:10:44+00:00 app[web.1]: >> Maximum connections set to 1024
2011-09-07T17:10:44+00:00 app[web.1]: >> Listening on 0.0.0.0:35396, CTRL+C to stop
2011-09-07T17:10:45+00:00 heroku[web.1]: State changed from starting to up
2011-09-07T17:10:46+00:00 app[web.1]: cache: [GET /users] miss
2011-09-07T17:10:46+00:00 heroku[router]: GET falling-winter-505.heroku.com/users dyno=web.1 queue=0 wait=7ms service=173ms status=500 bytes=728
2011-09-07T17:10:46+00:00 app[web.1]: cache: [GET /favicon.ico] miss, store
2011-09-07T17:10:46+00:00 heroku[router]: GET falling-winter-505.heroku.com/favicon.ico dyno=web.1 queue=0 wait=0ms service=9ms status=200 bytes=0
2011-09-07T17:54:01+00:00 app[web.1]: cache: [GET /] miss
2011-09-07T17:54:01+00:00 heroku[router]: GET falling-winter-505.heroku.com/ dyno=web.1 queue=0 wait=0ms service=3ms status=200 bytes=5907
2011-09-07T17:54:01+00:00 heroku[nginx]: 95.26.190.212 - - [07/Sep/2011:10:54:01 -0700] "GET / HTTP/1.1" 200 1865 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:6.0.2) Gecko/20100101 Firefox/6.0.2" falling-winter-505.heroku.com
2011-09-07T17:54:02+00:00 app[web.1]: cache: [GET /assets/rails.png] miss, store
2011-09-07T17:54:02+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/rails.png dyno=web.1 queue=0 wait=0ms service=12ms status=200 bytes=6646
2011-09-07T17:54:02+00:00 heroku[nginx]: 95.26.190.212 - - [07/Sep/2011:10:54:02 -0700] "GET /assets/rails.png HTTP/1.1" 200 6646 "http://falling-winter-505.heroku.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:6.0.2) Gecko/20100101 Firefox/6.0.2" falling-winter-505.heroku.com
2011-09-07T17:54:09+00:00 app[web.1]: cache: [GET /users] miss
2011-09-07T17:54:09+00:00 heroku[router]: GET falling-winter-505.heroku.com/users dyno=web.1 queue=0 wait=0ms service=14ms status=500 bytes=728
2011-09-07T17:54:09+00:00 heroku[nginx]: 95.26.190.212 - - [07/Sep/2011:10:54:09 -0700] "GET /users HTTP/1.1" 500 728 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:6.0.2) Gecko/20100101 Firefox/6.0.2" falling-winter-505.heroku.com
2011-09-07T18:01:13+00:00 app[web.1]: cache: [GET /users] miss
2011-09-07T18:01:13+00:00 heroku[router]: GET falling-winter-505.heroku.com/users dyno=web.1 queue=0 wait=0ms service=30ms status=500 bytes=728
2011-09-07T18:01:13+00:00 heroku[nginx]: 95.26.190.212 - - [07/Sep/2011:11:01:13 -0700] "GET /users HTTP/1.1" 500 728 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:6.0.2) Gecko/20100101 Firefox/6.0.2" falling-winter-505.heroku.com
2011-09-07T18:03:29+00:00 app[web.1]: cache: [GET /users] miss
2011-09-07T18:03:29+00:00 heroku[router]: GET falling-winter-505.heroku.com/users dyno=web.1 queue=0 wait=0ms service=12ms status=500 bytes=728
2011-09-07T18:03:29+00:00 heroku[nginx]: 95.26.190.212 - - [07/Sep/2011:11:03:29 -0700] "GET /users HTTP/1.1" 500 728 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:6.0.2) Gecko/20100101 Firefox/6.0.2" falling-winter-505.heroku.com
2011-09-07T18:03:42+00:00 heroku[api]: Config add RACK_ENV by g...#gmail.com
2011-09-07T18:03:42+00:00 heroku[api]: Release v9 created by g...#gmail.com
2011-09-07T18:03:42+00:00 heroku[web.1]: State changed from up to bouncing
2011-09-07T18:03:42+00:00 heroku[web.1]: State changed from bouncing to created
2011-09-07T18:03:42+00:00 heroku[web.1]: State changed from created to starting
2011-09-07T18:03:44+00:00 heroku[web.1]: Stopping process with S
2011-09-07T18:03:44+00:00 app[web.1]: >> Stopping ...
2011-09-07T18:03:44+00:00 heroku[web.1]: Process exited
2011-09-07T18:03:46+00:00 heroku[web.1]: Starting process with command `thin -p 16194 -e development -R /home/heroku_rack/heroku.ru start`
2011-09-07T18:03:49+00:00 app[web.1]: >> Thin web server (v1.2.6 codename Crazy Delicious)
2011-09-07T18:03:49+00:00 app[web.1]: >> Maximum connections set to 1024
2011-09-07T18:03:49+00:00 app[web.1]: >> Listening on 0.0.0.0:16194, CTRL+C to stop
2011-09-07T18:03:49+00:00 heroku[web.1]: State changed from starting to up
2011-09-07T18:03:52+00:00 heroku[router]: GET falling-winter-505.heroku.com/users dyno=web.1 queue=0 wait=0ms service=2057ms status=200 bytes=1677
2011-09-07T18:03:52+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/application.css dyno=web.1 queue=0 wait=0ms service=4ms status=200 bytes=314
2011-09-07T18:03:52+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/microposts.css dyno=web.1 queue=0 wait=0ms service=6ms status=200 bytes=0
2011-09-07T18:03:52+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/jquery_ujs.js dyno=web.1 queue=0 wait=0ms service=10ms status=200 bytes=13425
2011-09-07T18:03:53+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/jquery.js dyno=web.1 queue=0 wait=0ms service=26ms status=200 bytes=236203
2011-09-07T18:03:53+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/users.css dyno=web.1 queue=1 wait=30ms service=7ms status=200 bytes=0
2011-09-07T18:03:53+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/scaffolds.css dyno=web.1 queue=2 wait=40ms service=7ms status=200 bytes=1755
2011-09-07T18:03:53+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/application.js dyno=web.1 queue=0 wait=0ms service=8ms status=200 bytes=404
2011-09-07T18:03:53+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/users.js dyno=web.1 queue=0 wait=4ms service=7ms status=200 bytes=30
2011-09-07T18:04:08+00:00 heroku[router]: GET falling-winter-505.heroku.com/microposts dyno=web.1 queue=0 wait=0ms service=67ms status=200 bytes=1977
2011-09-07T18:04:08+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/application.css dyno=web.1 queue=0 wait=0ms service=3ms status=200 bytes=314
2011-09-07T18:04:08+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/scaffolds.css dyno=web.1 queue=0 wait=0ms service=2ms status=200 bytes=1755
2011-09-07T18:04:08+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/users.css dyno=web.1 queue=0 wait=0ms service=3ms status=200 bytes=0
2011-09-07T18:04:08+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/microposts.css dyno=web.1 queue=1 wait=1ms service=2ms status=200 bytes=0
2011-09-07T18:04:08+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/microposts.js dyno=web.1 queue=0 wait=0ms service=4ms status=200 bytes=30
2011-09-07T18:04:08+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/jquery.js dyno=web.1 queue=0 wait=0ms service=12ms status=200 bytes=236203
2011-09-07T18:04:08+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/jquery_ujs.js dyno=web.1 queue=0 wait=0ms service=8ms status=200 bytes=13425
2011-09-07T18:04:09+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/users.js dyno=web.1 queue=0 wait=0ms service=5ms status=200 bytes=30
2011-09-07T18:04:09+00:00 heroku[router]: GET falling-winter-505.heroku.com/assets/application.js dyno=web.1 queue=1 wait=4ms service=3ms status=200 bytes=404
2011-09-07T18:04:21+00:00 heroku[api]: Config add RACK_ENV by g...#gmail.com
2011-09-07T18:04:21+00:00 heroku[api]: Release v10 created by g...#gmail.com
2011-09-07T18:04:21+00:00 heroku[web.1]: State changed from up to bouncing
2011-09-07T18:04:21+00:00 heroku[web.1]: State changed from bouncing to created
2011-09-07T18:04:21+00:00 heroku[web.1]: State changed from created to starting
2011-09-07T18:04:23+00:00 heroku[web.1]: Stopping process with SIGTERM
2011-09-07T18:04:23+00:00 app[web.1]: >> Stopping ...
2011-09-07T18:04:23+00:00 heroku[web.1]: Process exited
2011-09-07T18:04:24+00:00 heroku[web.1]: Starting process with command `thin -p 30135 -e production -R /home/heroku_rack/heroku.ru start`
2011-09-07T18:04:28+00:00 app[web.1]: >> Thin web server (v1.2.6 codename Crazy Delicious)
2011-09-07T18:04:28+00:00 app[web.1]: >> Maximum connections set to 1024
2011-09-07T18:04:28+00:00 app[web.1]: >> Listening on 0.0.0.0:30135, CTRL+C to stop
2011-09-07T18:04:29+00:00 heroku[web.1]: State changed from starting to up
2011-09-07T18:04:30+00:00 app[web.1]: cache: [GET /microposts] miss
2011-09-07T18:04:30+00:00 heroku[router]: GET falling-winter-505.heroku.com/microposts dyno=web.1 queue=0 wait=0ms service=164ms status=500 bytes=728
2011-09-07T18:04:30+00:00 heroku[nginx]: 95.26.190.212 - - [07/Sep/2011:11:04:30 -0700] "GET /microposts HTTP/1.1" 500 728 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:6.0.2) Gecko/20100101 Firefox/6.0.2" falling-winter-505.heroku.com
My Version of Ruby is 1.9.2p290, and the version of Rails is 3.1.0.
Considering that it works in development mode but not production, I'd say the most likely culprit is your production.rb file as John Beynon suggested. The next thing I'd try is to run it in production mode locally. You should get, if nothing else, better error messages.
It appears you did not precompile your assets. Here is how to do it http://guides.rubyonrails.org/asset_pipeline.html#in-production
I know I had lots of troubles with that before. And it was an issue of Heroku not supporting sqlite3 at all. They remove your database.yml file with a new one, which uses mysql. A few things to check:
Add the mysql or mysql2 gem.
Does your app depend on data from the database? If so you'll need to find a way to import the new data into mysql as your sqlite databases won't work. I ended up using the yaml_db gem to do this (https://github.com/adamwiggins/yaml_db). And had to do some stuff with