Clojure (Joodo) deployment on Heroku failing - heroku

I'm having some trouble getting my Joodo application to deploy to Heroku. According to the deployment instructions here http://joodoweb.com/, we can theoretically deploy without specifying a Procfile. This causes Heroku to run lein with-profile production trampoline run as the default command to launch the project. This leads to this error:
2014-04-26T19:30:46.899454+00:00 app[web.1]: Error encountered performing task 'trampoline' with profile(s): 'production'
2014-04-26T19:30:46.899525+00:00 app[web.1]: Suppressed exit
2014-04-26T19:30:46.899112+00:00 app[web.1]: No :main namespace specified in project.clj.
2014-04-26T19:30:48.275513+00:00 heroku[web.1]: Process exited with status 1
2014-04-26T19:30:49.093441+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=floating-chamber-7585.herokuapp.com request_id=de532a37-57b1-4ce2-b5c0-c056019eda6b fwd="76.171.76.49" dyno= connect= service= status=503 bytes=
2014-04-26T19:30:48.303715+00:00 heroku[web.1]: State changed from starting to crashed
I have also tried explicitly setting the Procfile to 'lein ring server' (which is what you run in development). The error then is:
2014-04-26T21:24:34.229386+00:00 app[web.1]: java.lang.Exception: No namespace: heepster.view-helpers found
2014-04-26T21:24:34.221227+00:00 app[web.1]: :request-method :get
2014-04-26T21:24:34.221229+00:00 app[web.1]: :scheme :http
2014-04-26T21:24:34.221232+00:00 app[web.1]: :server-port 80
2014-04-26T21:24:34.221235+00:00 app[web.1]: :session/key nil
2014-04-26T21:24:34.229391+00:00 app[web.1]: at joodo.views$eval_content.invoke(views.clj:48)
2014-04-26T21:24:34.221238+00:00 app[web.1]: :uri /}
2014-04-26T21:24:34.229380+00:00 app[web.1]:
2014-04-26 21:24:34.227:WARN:oejs.AbstractHttpConnection:/
2014-04-26T21:24:34.229395+00:00 app[web.1]: at joodo.views$render_in_layout.invoke(views.clj:59)
2014-04-26T21:24:34.229388+00:00 app[web.1]: at clojure.core$the_ns.invoke(core.clj:3760)
2014-04-26T21:24:34.229401+00:00 app[web.1]: at heepster.main$fn__2523.invoke(main.clj:23)
2014-04-26T21:24:34.229405+00:00 app[web.1]: at compojure.core$if_route$fn__649.invoke(core.clj:40)
2014-04-26T21:24:34.229393+00:00 app[web.1]: at joodo.views$render.invoke(views.clj:52)
2014-04-26T21:24:34.229409+00:00 app[web.1]: at compojure.core$routing$fn__667.invoke(core.clj:107)
2014-04-26T21:24:34.229413+00:00 app[web.1]: at compojure.core$routing.doInvoke(core.clj:107)
2014-04-26T21:24:34.229397+00:00 app[web.1]: at joodo.views$render_template.doInvoke(views.clj:86)
2014-04-26T21:24:34.229403+00:00 app[web.1]: at compojure.core$make_route$fn__661.invoke(core.clj:94)
Does anyone have any ideas?

Related

Liveview app reloading infinitely on heroku deployment

This might be a stupid question to ask but are there any extra steps I need to complete to deploy a phoenix liveview app to heroku?
From official documents deployment of phoenix app was successful but converting the same page into a liveview caused the page to reload infinitely
And the error I get on heroku logs are:
2022-01-18T07:35:12.424013+00:00 heroku[router]: at=info method=GET path="/" host=fast-fortress-60216.herokuapp.com request_id=0bf752c3-185a-44d4-84ce-7004f7031984 fwd="27.34.20.173" dyno=web.1 connect=0ms service=2ms status=200 bytes=4941 protocol=https
2022-01-18T07:35:13.895958+00:00 heroku[router]: at=info method=GET path="/assets/app-097a5c6ca9e10ff4881312b83e54a14f.css?vsn=d" host=fast-fortress-60216.herokuapp.com request_id=8d4e402d-cf16-4e4d-8b26-3bdcbbc6186c fwd="27.34.20.173" dyno=web.1 connect=0ms service=2ms status=200 bytes=15612 protocol=https
2022-01-18T07:35:15.191409+00:00 heroku[router]: at=info method=GET path="/live/websocket?_csrf_token=SC9hAXBiKRoOLDYALRkhCT8EBzk8LT0syDSs70xHbMfQfZyowhVUrjDs&_track_static%5B0%5D=https%3A%2F%2Ffast-fortress-60216.herokuapp.com%2Fassets%2Fapp-097a5c6ca9e10ff4881312b83e54a14f.css%3Fvsn%3Dd&_track_static%5B1%5D=https%3A%2F%2Ffast-fortress-60216.herokuapp.com%2Fassets%2Fapp-a670ca05a10bcaada1c4842b40be19a2.js%3Fvsn%3Dd&_mounts=0&vsn=2.0.0" host=fast-fortress-60216.herokuapp.com request_id=e8ef08c8-d80a-4a79-8b73-d21cc5e47d2c fwd="27.34.20.173" dyno=web.1 connect=0ms service=1ms status=403 bytes=195 protocol=https
2022-01-18T07:35:15.191230+00:00 app[web.1]: 07:35:15.191 [error] Could not check origin for Phoenix.Socket transport.
2022-01-18T07:35:15.191243+00:00 app[web.1]:
2022-01-18T07:35:15.191244+00:00 app[web.1]: Origin of the request: https://fast-fortress-60216.herokuapp.com
2022-01-18T07:35:15.191244+00:00 app[web.1]:
2022-01-18T07:35:15.191245+00:00 app[web.1]: This happens when you are attempting a socket connection to
2022-01-18T07:35:15.191246+00:00 app[web.1]: a different host than the one configured in your config/
2022-01-18T07:35:15.191246+00:00 app[web.1]: files. For example, in development the host is configured
2022-01-18T07:35:15.191246+00:00 app[web.1]: to "localhost" but you may be trying to access it from
2022-01-18T07:35:15.191247+00:00 app[web.1]: "127.0.0.1". To fix this issue, you may either:
2022-01-18T07:35:15.191247+00:00 app[web.1]:
2022-01-18T07:35:15.191248+00:00 app[web.1]: 1. update [url: [host: ...]] to your actual host in the
2022-01-18T07:35:15.191248+00:00 app[web.1]: config file for your current environment (recommended)
2022-01-18T07:35:15.191248+00:00 app[web.1]:
2022-01-18T07:35:15.191248+00:00 app[web.1]: 2. pass the :check_origin option when configuring your
2022-01-18T07:35:15.191249+00:00 app[web.1]: endpoint or when configuring the transport in your
2022-01-18T07:35:15.191249+00:00 app[web.1]: UserSocket module, explicitly outlining which origins
2022-01-18T07:35:15.191250+00:00 app[web.1]: are allowed:
2022-01-18T07:35:15.191251+00:00 app[web.1]:
2022-01-18T07:35:15.191251+00:00 app[web.1]: check_origin: ["https://example.com",
2022-01-18T07:35:15.191251+00:00 app[web.1]: "//another.com:888", "//other.com"]
Do I have to install extra buildpacks or some changes in my configs?
My bad
The solution was right there but I didn't exactly know how to implement it.
The solution is adding
config :grasruts, GrasrutsWeb.Endpoint, check_origin: ["http://localhost:4000/","https://HEROKU_APP_URL/"]

Heroku Idling because quota is exhausted

What does this mean? State changed from up to down Idling because quota is exhausted Stopping all processes with SIGTERM
My heroku app shut down and when I type heroku logs -t it give me this
State changed from crashed to starting
2019-02-27T09:41:54.000000+00:00 app[api]: Build succeeded
2019-02-27T09:41:57.263955+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 41036 -e production`
2019-02-27T09:42:08.039524+00:00 heroku[web.1]: State changed from starting to up
2019-02-27T09:42:08.050315+00:00 heroku[web.1]: Idling
2019-02-27T09:42:08.054726+00:00 heroku[web.1]: State changed from up to down
2019-02-27T09:42:08.066260+00:00 heroku[web.1]: Idling because quota is exhausted
2019-02-27T09:42:07.658395+00:00 app[web.1]: [2019-02-27 09:42:07] INFO WEBrick 1.3.1
2019-02-27T09:42:07.658431+00:00 app[web.1]: [2019-02-27 09:42:07] INFO ruby 2.3.7 (2018-03-28) [x86_64-linux]
2019-02-27T09:42:07.658737+00:00 app[web.1]: [2019-02-27 09:42:07] INFO WEBrick::HTTPServer#start: pid=4 port=41036
2019-02-27T09:42:08.831687+00:00 heroku[router]: at=info code=H82 desc="Free app running time quota exhausted" method=GET path="/" host=www.petraauto.com request_id=17318012-510b-47e2-9277-fe1a448ec3ea fwd="174.6.158.167" dyno= connect= service= status=503 bytes= protocol=http
2019-02-27T09:42:09.238077+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2019-02-27T09:42:09.270539+00:00 app[web.1]: [2019-02-27 09:42:09] FATAL SignalException: SIGTERM
2019-02-27T09:42:09.270590+00:00 app[web.1]: /app/vendor/ruby-2.3.7/lib/ruby/2.3.0/webrick/server.rb:177:in `select'
2019-02-27T09:42:09.270592+00:00 app[web.1]: /app/vendor/ruby-2.3.7/lib/ruby/2.3.0/webrick/server.rb:177:in `block in start'
2019-02-27T09:42:09.270594+00:00 app[web.1]: /app/vendor/ruby-2.3.7/lib/ruby/2.3.0/webrick/server.rb:33:in `start'
2019-02-27T09:42:09.270596+00:00 app[web.1]: /app/vendor/ruby-2.3.7/lib/ruby/2.3.0/webrick/server.rb:164:in `start'
2019-02-27T09:42:09.270597+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/rack-1.5.5/lib/rack/handler/webrick.rb:14:in `run'
2019-02-27T09:42:09.270599+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/rack-1.5.5/lib/rack/server.rb:264:in `start'
2019-02-27T09:42:09.270600+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/railties-4.1.8/lib/rails/commands/server.rb:69:in `start'
2019-02-27T09:42:09.270605+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/railties-4.1.8/lib/rails/commands/commands_tasks.rb:81:in `block in server'
2019-02-27T09:42:09.270606+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/railties-4.1.8/lib/rails/commands/commands_tasks.rb:76:in `tap'
2019-02-27T09:42:09.270608+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/railties-4.1.8/lib/rails/commands/commands_tasks.rb:76:in `server'
2019-02-27T09:42:09.270610+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/railties-4.1.8/lib/rails/commands/commands_tasks.rb:40:in `run_command!'
2019-02-27T09:42:09.270611+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/railties-4.1.8/lib/rails/commands.rb:17:in `<top (required)>'
2019-02-27T09:42:09.270613+00:00 app[web.1]: bin/rails:4:in `require'
2019-02-27T09:42:09.270615+00:00 app[web.1]: bin/rails:4:in `<main>'
2019-02-27T09:42:09.273222+00:00 app[web.1]: [2019-02-27 09:42:09] INFO going to shutdown ...
2019-02-27T09:42:09.273252+00:00 app[web.1]: [2019-02-27 09:42:09] INFO WEBrick::HTTPServer#start done.
2019-02-27T09:42:09.273368+00:00 app[web.1]: => Booting WEBrick
You've run out of time on your Free Dynos.
https://devcenter.heroku.com/articles/error-codes#h82-free-dyno-quota-exhausted
https://devcenter.heroku.com/articles/free-dyno-hours#free-dyno-hour-pool
**RECENT UPDATE
Hey your post helped me out this morning. Unfortunately, minutes later, I received an email from Salesforce.
It looks like moving forward Heroku will no longer offer the free services, such as free Dynos. I think it discontinues November 28th or so.
Give the following a read: https://blog.heroku.com/next-chapter
And prepare accordingly for your applications using free dynos!

We're sorry, but something went wrong Heroku

Don't start app at Heroku.
Migrate I was do, but it don`t work anyway... Please help my anyone
2015-07-17T08:27:11.996879+00:00 app[web.1]: => Booting Puma
2015-07-17T08:27:11.996906+00:00 app[web.1]: => Rails 4.2.1 application starting in production on http://0.0.0.0:15906
2015-07-17T08:27:11.996909+00:00 app[web.1]: => Run `rails server -h for more startup options
2015-07-17T08:27:11.996910+00:00 app[web.1]: => Ctrl-C to shutdown server
2015-07-17T08:27:16.038259+00:00 heroku[web.1]: State changed from starting to up
2015-07-17T08:27:15.924000+00:00 app[web.1]: Puma 2.11.3 starting...
2015-07-17T08:27:15.924095+00:00 app[web.1]: * Min threads: 0, max threads: 16
2015-07-17T08:27:15.924199+00:00 app[web.1]: * Environment: production
2015-07-17T08:27:15.924281+00:00 app[web.1]: * Listening on tcp://0.0.0.0:15906
2015-07-17T08:27:18.702571+00:00 heroku[router]: at=info method=GET path="/" host=shrouded-eyrie-5960.herokuapp.com request_id=7976700d-bee7-4e6f-b20a-67d60a5d5e8a fwd="176.104.8.251" dyno=web.1 connect=1ms service=210ms status=500 bytes=1669
2015-07-17T08:27:18.819798+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=shrouded-eyrie-5960.herokuapp.com request_id=23341143-bd39-46ed-a48a-736533558ccd fwd="176.104.8.251" dyno=web.1 connect=1ms service=2ms status=200 bytes=143`
This error comes from your app's code. However, your app is sending it's logs to the local filesystem, which means you don't see the exception in heroku logs.
You would need to configure your app to send logs to STDOUT or STDERR to be able to see them.
You can add the rails_12factor gem to your app, which will change your configuration to do just that.
Once you have added this gem to your app and redeployed it, the raised exception should show in your logs and you can fix in your app's code.

Dashing on Heroku giving "config.ru" error

So, I am just trying to get a simple Heroku server running Dashing up. So far, I have the dashing and gemlock committed to heroku. Whenever I open the site, I get an error. My logs give me this:
2015-03-14T04:05:37.617789+00:00 heroku[api]: Deploy 2447a74 by #gmail.com
2015-03-14T04:05:37.617789+00:00 heroku[api]: Release v8 created by #gmail.com
2015-03-14T04:05:38.099916+00:00 heroku[web.1]: State changed from crashed to starting
2015-03-14T04:05:41.184158+00:00 heroku[web.1]: Starting process with command bundle exec thin start -R config.ru -e pr
oduction -p 12627
2015-03-14T04:05:43.367997+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/lib/rack/adapter/loader.rb:32
:in read': No such file or directory - config.ru (Errno::ENOENT)
2015-03-14T04:05:43.368046+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/lib/rack/adapter/load
er.rb:32:inload'
2015-03-14T04:05:43.368055+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/lib/thin/runner.rb:20
0:in run_command'
2015-03-14T04:05:43.368051+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/lib/thin/controllers/
controller.rb:182:inload_rackup_config'
2015-03-14T04:05:43.368053+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/lib/thin/controllers/
controller.rb:72:in start'
2015-03-14T04:05:43.368064+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/bin/thin:6:in'
2015-03-14T04:05:43.368066+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/bin/thin:23:in load'
2015-03-14T04:05:43.368062+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/lib/thin/runner.rb:15
6:inrun!'
2015-03-14T04:05:43.368069+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/bin/thin:23:in `'
2015-03-14T04:05:44.164461+00:00 heroku[web.1]: State changed from starting to crashed
2015-03-14T04:05:44.157004+00:00 heroku[web.1]: Process exited with status 1
2015-03-14T04:06:01.687293+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-d
awn-3700.herokuapp.com request_id=902320e9-1789-4099-94b2-8b4431d59495 fwd="66.190.95.133" dyno= connect= service= statu
s=503 bytes=
2015-03-14T04:06:02.015965+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" hos
t=pacific-dawn-3700.herokuapp.com request_id=6563d675-9732-4a21-84f4-c486fb6d792e fwd="66.190.95.133" dyno= connect= ser
vice= status=503 bytes=
A config.ru file was never created...I'm new to Ruby and Dashing and Heroku. I've even tried creating a blank config.ru, but even more errors occur...
Found the config file in anothjer directory somehow. Popped it in, it works!

How Can I Decipher This Heroku Error Message?

I am brand-new to Heroku, so this may be a novice question. I tried pushing my app just now, and got the following message:
Application Error
An error occurred in the application and your page could not be served. Please try again in a few moments.
If you are the application owner, check your logs for details.
I opened up the log and got the message(s) below. Judging by the change in command line's text color in the Terminal, the problem seems to be when the command line goes from "heroku[api]" to "heroku[web.1]". But I can't say for sure. I would love to be able to decipher Heroku messages on my own, I just need to know where to look or how to start debugging.
Thanks, everyone!
rickthomas$ heroku logs
2013-07-09T17:33:06.459433+00:00 heroku[api]: Enable Logplex by email#gmail.com
2013-07-09T17:33:06.496133+00:00 heroku[api]: Release v2 created by email#gmail.com
2013-07-09T17:33:21+00:00 heroku[slug-compiler]: Slug compilation started
2013-07-09T17:35:17.225189+00:00 heroku[api]: Scale to web=1 by email#gmail.com
2013-07-09T17:35:17.676874+00:00 heroku[api]: Attach HEROKU_POSTGRESQL_IVORY resource by email#gmail.com
2013-07-09T17:35:17.708587+00:00 heroku[api]: Release v3 created by email#gmail.com
2013-07-09T17:35:17.786263+00:00 heroku[api]: Add DATABASE_URL config by email#gmail.com
2013-07-09T17:35:17.801350+00:00 heroku[api]: Release v4 created by email#gmail.com
2013-07-09T17:35:17.846508+00:00 heroku[api]: Deploy ca4cf14 by email#gmail.com
2013-07-09T17:35:17.861693+00:00 heroku[api]: Release v5 created by email#gmail.com
2013-07-09T17:35:17.901985+00:00 heroku[api]: Deploy ca4cf14 by email#gmail.com
2013-07-09T17:35:18+00:00 heroku[slug-compiler]: Slug compilation finished
2013-07-09T17:35:20.490635+00:00 heroku[web.1]: Starting process with command `bundle exec rackup config.ru -p 15074`
2013-07-09T17:35:21.528470+00:00 app[web.1]: The source :rubygems is deprecated because HTTP requests are insecure.
2013-07-09T17:35:21.528470+00:00 app[web.1]: Please change your source to 'https://rubygems.org' if possible, or 'http://rubygems.org' if not.
2013-07-09T17:35:22.120319+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:55:in `instance_eval'
2013-07-09T17:35:22.120319+00:00 app[web.1]: from /app/config/environment.rb:21:in `<top (required)>'
2013-07-09T17:35:22.120319+00:00 app[web.1]: from /app/config.ru:2:in `require'
2013-07-09T17:35:22.120319+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:55:in `initialize'
2013-07-09T17:35:22.120319+00:00 app[web.1]: from /app/config.ru:2:in `block in <main>'
2013-07-09T17:35:22.120508+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:40:in `parse_file'
2013-07-09T17:35:22.120319+00:00 app[web.1]: from /app/config.ru:in `<main>'
2013-07-09T17:35:22.120508+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/server.rb:199:in `app'
2013-07-09T17:35:22.120508+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/server.rb:250:in `start'
2013-07-09T17:35:22.120508+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/server.rb:141:in `start'
2013-07-09T17:35:22.120319+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:49:in `new_from_string'
2013-07-09T17:35:22.120508+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/bin/rackup:23:in `load'
2013-07-09T17:35:22.120508+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/bin/rackup:23:in `<main>'
2013-07-09T17:35:22.120319+00:00 app[web.1]: /app/config/environment.rb:21:in `require': cannot load such file -- faker (LoadError)
2013-07-09T17:35:22.120319+00:00 app[web.1]: from /app/config.ru:in `new'
2013-07-09T17:35:22.120508+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/server.rb:314:in `wrapped_app'
2013-07-09T17:35:22.120508+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/server.rb:277:in `build_app_and_options_from_config'
2013-07-09T17:35:22.120508+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/bin/rackup:4:in `<top (required)>'
2013-07-09T17:35:22.120319+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:49:in `eval'
2013-07-09T17:35:23.396333+00:00 heroku[web.1]: Process exited with status 1
2013-07-09T17:35:23.410600+00:00 heroku[web.1]: State changed from starting to crashed
2013-07-09T17:35:23.411208+00:00 heroku[web.1]: State changed from crashed to starting
2013-07-09T17:35:26.683935+00:00 heroku[web.1]: Starting process with command `bundle exec rackup config.ru -p 57539`
2013-07-09T17:35:27.666245+00:00 app[web.1]: The source :rubygems is deprecated because HTTP requests are insecure.
2013-07-09T17:35:27.666245+00:00 app[web.1]: Please change your source to 'https://rubygems.org' if possible, or 'http://rubygems.org' if not.
2013-07-09T17:35:28.270486+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:55:in `initialize'
2013-07-09T17:35:28.270736+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/bin/rackup:23:in `load'
2013-07-09T17:35:28.270486+00:00 app[web.1]: from /app/config.ru:in `new'
2013-07-09T17:35:28.270736+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/bin/rackup:23:in `<main>'
2013-07-09T17:35:28.270486+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:49:in `eval'
2013-07-09T17:35:28.270736+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/server.rb:141:in `start'
2013-07-09T17:35:28.270486+00:00 app[web.1]: /app/config/environment.rb:21:in `require': cannot load such file -- faker (LoadError)
2013-07-09T17:35:28.270736+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:40:in `parse_file'
2013-07-09T17:35:28.270486+00:00 app[web.1]: from /app/config.ru:2:in `block in <main>'
2013-07-09T17:35:28.270736+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/server.rb:199:in `app'
2013-07-09T17:35:28.270486+00:00 app[web.1]: from /app/config/environment.rb:21:in `<top (required)>'
2013-07-09T17:35:28.270486+00:00 app[web.1]: from /app/config.ru:in `<main>'
2013-07-09T17:35:28.270486+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:55:in `instance_eval'
2013-07-09T17:35:28.270736+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/server.rb:250:in `start'
2013-07-09T17:35:28.270486+00:00 app[web.1]: from /app/config.ru:2:in `require'
2013-07-09T17:35:28.270486+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:49:in `new_from_string'
2013-07-09T17:35:28.270736+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/bin/rackup:4:in `<top (required)>'
2013-07-09T17:35:28.270736+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/server.rb:277:in `build_app_and_options_from_config'
2013-07-09T17:35:28.270736+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/server.rb:314:in `wrapped_app'
2013-07-09T17:35:29.714787+00:00 heroku[web.1]: Process exited with status 1
2013-07-09T17:35:29.731620+00:00 heroku[web.1]: State changed from starting to crashed
2013-07-09T17:37:15.135194+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=boiling-scrubland-3057.herokuapp.com fwd="74.122.9.196" dyno= connect= service= status=503 bytes=
2013-07-09T17:37:15.526745+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=boiling-scrubland-3057.herokuapp.com fwd="74.122.9.196" dyno= connect= service= status=503 bytes=
2013-07-09T17:37:18.534815+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=boiling-scrubland-3057.herokuapp.com fwd="74.122.9.196" dyno= connect= service= status=503 bytes=
2013-07-09T17:37:20.075790+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=boiling-scrubland-3057.herokuapp.com fwd="74.122.9.196" dyno= connect= service= status=503 bytes=
2013-07-09T17:37:44.605357+00:00 heroku[api]: Scale to web=1 by email#gmail.com
2013-07-09T17:37:49.741821+00:00 heroku[api]: Scale to web=1 by email#gmail.com
2013-07-09T17:37:18.353741+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=boiling-scrubland-3057.herokuapp.com fwd="74.122.9.196" dyno= connect= service= status=503 bytes=
2013-07-09T17:39:03.510163+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=boiling-scrubland-3057.herokuapp.com fwd="74.122.9.196" dyno= connect= service= status=503 bytes=
2013-07-09T17:39:09.125379+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=boiling-scrubland-3057.herokuapp.com fwd="74.122.9.196" dyno= connect= service= status=503 bytes=
2013-07-09T17:39:09.188174+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=boiling-scrubland-3057.herokuapp.com fwd="74.122.9.196" dyno= connect= service= status=503 bytes=
Ricks-MacBook-Pro:even_awesomer_blog_soon_to_be_hacker_news rickthomas$
After deep-diving into the logs, the closest I could come to an error message was:
2013-07-09T17:35:22.120319+00:00 app[web.1]: /app/config/environment.rb:21:in `require': cannot load such file -- faker (LoadError)
I simply commented out the references to the "Faker" gem in my gemfile and environment.rb file, and re-deployed it to Heroku. This worked fine.
Lesson learned- Heroku and Faker don't play well together.
Might also try in your Gemfile:
gem 'faker', require: false
And then specifically require it where necessary.

Resources