heroku platform error on staging-punda

staging 2012-11-01

$ git push staging newdev:master --force
Counting objects: 128, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (88/88), done.
Writing objects: 100% (88/88), 13.25 KiB, done.
Total 88 (delta 72), reused 0 (delta 0)

-----> Heroku receiving push
-----> Ruby/Rails app detected
-----> Using Ruby version: ruby-1.9.3
-----> Installing dependencies using Bundler version 1.2.1
       Running: bundle install --without development:test --path vendor/bundle --binstubs bin/ --deployment
       Fetching gem metadata from http://rubygems.org/.......
       Fetching gem metadata from http://rubygems.org/..
       Using rake (0.9.2.2)
       Using multi_json (1.3.6)
       Using activesupport (3.1.3)
       Installing builder (3.0.4)
       Using i18n (0.6.1)
       Using activemodel (3.1.3)
       Using arel (2.2.3)
       Installing tzinfo (0.3.34)
       Using activerecord (3.1.3)
       Using aasm (2.3.1) from git://github.com/dsaronin/aasm.git (at master)
       Using acl9 (0.12.0)
       Using erubis (2.7.0)
       Using rack (1.3.6)
       Installing rack-cache (1.2)
       Using rack-mount (0.8.3)
       Installing rack-test (0.6.2)
       Using hike (1.2.1)
       Using tilt (1.3.3)
       Installing sprockets (2.0.4)
       Using actionpack (3.1.3)
       Using mime-types (1.19)
       Using polyglot (0.3.3)
       Installing treetop (1.4.12)
       Installing mail (2.3.3)
       Using actionmailer (3.1.3)
       Using activeresource (3.1.3)
       Installing acts_as_tree (1.2.0)
       Installing connection_pool (0.9.2)
       Installing girl_friday (0.10.0)
       Installing airbrake (3.1.6)
       Installing xml-simple (1.1.2)
       Installing aws-s3 (0.6.3)
       Installing multi_xml (0.5.1)
       Installing httparty (0.9.0)
       Installing json (1.7.5) with native extensions
       Installing nokogiri (1.5.5) with native extensions
       Installing uuidtools (2.1.3)
       Installing aws-sdk (1.6.9)
       Using bcrypt-ruby (3.0.1)
       Installing cocaine (0.4.2)
       Using currencies (0.4.0)
       Installing countries (0.8.3)
       Installing daemons (1.1.9)
       Installing delayed_job (3.0.3)
       Installing delayed_job_active_record (0.3.3)
       Installing orm_adapter (0.4.0)
       Using rack-ssl (1.3.2)
       Using rdoc (3.12)
       Using thor (0.14.6)
       Using railties (3.1.3)
       Installing warden (1.2.1)
       Installing devise (2.1.2)
       Installing devise-encryptable (0.1.1)
       Installing eventmachine (1.0.0) with native extensions
       Installing execjs (1.4.0)
       Installing haml (3.1.7)
       Installing haml-rails (0.3.5)
       Installing icalendar (1.2.0)
       Installing jquery-rails (2.1.3)
       Using magesa (0.1.5)
       Using bundler (1.2.1)
       Using rails (3.1.3)
       Using milia (0.3.30)
       Using rest-client (1.6.7)
       Using moonshado-sms (1.1.1) from https://github.com/moonshado/moonshado-sms.git (at master)
       Installing newrelic_rpm (3.5.0.1)
       Installing paperclip (3.3.0)
       Installing pg (0.14.1) with native extensions
       Installing phony (1.8.3)
       Using rack-timeout (0.0.3)
       Using rails_sql_views (0.8.0) from git://github.com/dsaronin/rails_sql_views.git (at master)
       Using recaptcha (0.3.4)
       Installing sass (3.1.21)
       Using sass-rails (3.1.5)
       Installing thin (1.5.0) with native extensions
       Installing uglifier (1.3.0)
       Using validates_date_time (1.0.0) from https://github.com/nickstenning/validates_date_time.git (at master)
       Installing wicked_pdf (0.7.9)
       Installing will_paginate (3.0.3)
       Your bundle is complete! It was installed into ./vendor/bundle
       Post-install message from httparty:
       When you HTTParty, you must party hard!
       Post-install message from icalendar:
       PostInstall.txt
       Post-install message from newrelic_rpm:
       PLEASE NOTE:
       Developer Mode is now a Rack middleware.
       Developer Mode is no longer available in Rails 2.1 and earlier.
       However, starting in version 2.12 you can use Developer Mode in any
       Rack based framework, in addition to Rails.  To install developer mode
       in a non-Rails application, just add NewRelic::Rack::DeveloperMode to
       your middleware stack.
       If you are using JRuby, we recommend using at least version 1.4 or
       later because of issues with the implementation of the timeout library.
       Refer to the README.md file for more information.
       Please see http://github.com/newrelic/rpm/blob/master/CHANGELOG
       for a complete description of the features and enhancements available
       in version 3.5 of the Ruby Agent.
       
       Post-install message from paperclip:
       ##################################################
       #  NOTE FOR UPGRADING FROM PRE-3.0 VERSION       #
       ##################################################
       Paperclip 3.0 introduces a non-backward compatible change in your attachment
       path. This will help to prevent attachment name clashes when you have
       multiple attachments with the same name. If you didn't alter your
       attachment's path and are using Paperclip's default, you'll have to add
       `:path` and `:url` to your `has_attached_file` definition. For example:
       has_attached_file :avatar,
       :path => ":rails_root/public/system/:attachment/:id/:style/:filename",
       :url => "/system/:attachment/:id/:style/:filename"
       Cleaning up the bundler cache.
       Removing paperclip (2.4.5)
       Removing warden (1.1.0)
       Removing will_paginate (3.0.2)
       Removing orm_adapter (0.0.5)
       Removing sass (3.1.12)
       Removing treetop (1.4.10)
       Removing haml-rails (0.3.4)
       Removing thin (1.3.1)
       Removing newrelic_rpm (3.5.0)
       Removing mail (2.3.0)
       Removing jquery-rails (1.0.19)
       Removing delayed_job (2.1.4)
       Removing builder (3.0.3)
       Removing pg (0.12.0)
       Removing tzinfo (0.3.33)
       Removing eventmachine (0.12.10)
       Removing rack-test (0.6.1)
       Removing rake-compiler (0.7.9)
       Removing xml-simple (1.1.1)
       Removing execjs (1.2.13)
       Removing rack-cache (1.1)
       Removing haml (3.1.4)
       Removing sprockets (2.0.3)
       Removing airbrake (3.0.9)
       Removing countries (0.8.2)
       Removing cocaine (0.2.1)
       Removing acts_as_tree (0.1.1)
       Removing uglifier (1.2.1)
       Removing phony (1.8.0)
       Removing aws-s3 (0.6.2)
       Removing icalendar (1.1.6)
       Removing devise (1.5.3)
       Removing daemons (1.1.5)
       Removing wicked_pdf (0.7.2)
       Removing json (1.6.4)
       Removing validates_date_time (434d28dbb505)
-----> Writing config/database.yml to read from DATABASE_URL
-----> Preparing app for Rails asset pipeline
       Running: rake assets:precompile
       /tmp/build_lmtkygciphdk/vendor/ruby-1.9.3/bin/ruby /tmp/build_lmtkygciphdk/vendor/bundle/ruby/1.9.1/bin/rake assets:precompile:nondigest RAILS_ENV=production RAILS_GROUPS=assets
       Asset precompilation completed (25.44s)
-----> Rails plugin injection
       Injecting rails_log_stdout
       Injecting rails3_serve_static_assets
-----> Discovering process types
       Procfile declares types      -> web
       Default types for Ruby/Rails -> console, rake, worker
-----> Compiled slug size: 37.6MB
-----> Launching... done, v377
-----> Deploy hooks scheduled, check output in your logs
       http://staging-punda.herokuapp.com deployed to Heroku

To git@heroku.com:staging-punda.git
   00048df..905f799  newdev -> master
daudi@jabari:~/projectspace/staging-punda$ heroku restart
Restarting processes... done

2012-11-02T05:14:50+00:00 heroku[router]: GET staging-punda.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=53ms status=200 bytes=13021
2012-11-02T05:19:50+00:00 heroku[router]: GET staging-punda.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=46ms status=200 bytes=13019
2012-11-02T05:22:49+00:00 heroku[web.1]: Starting process with command `bundle exec thin start -R config.ru -p 4989 -e production`
2012-11-02T05:23:03+00:00 app[web.1]: >> Thin web server (v1.5.0 codename Knife)
2012-11-02T05:23:03+00:00 app[web.1]: >> Maximum connections set to 1024
2012-11-02T05:23:03+00:00 app[web.1]: >> Listening on 0.0.0.0:4989, CTRL+C to stop
2012-11-02T05:23:05+00:00 heroku[web.1]: State changed from starting to up
2012-11-02T05:26:37+00:00 heroku[router]: Error H99 (Platform error) -> GET staging-punda.herokuapp.com/ dyno= queue= wait= service= status=503 bytes=
2012-11-02T05:28:13+00:00 heroku[router]: Error H99 (Platform error) -> GET staging-punda.herokuapp.com/ dyno= queue= wait= service= status=503 bytes=
2012-11-02T05:29:28+00:00 heroku[router]: Error H99 (Platform error) -> GET staging-punda.herokuapp.com/ dyno= queue= wait= service= status=503 bytes=
2012-11-02T05:29:49+00:00 heroku[web.1]: State changed from up to down
2012-11-02T05:29:49+00:00 heroku[web.1]: State changed from down to starting
2012-11-02T05:29:51+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2012-11-02T05:29:53+00:00 heroku[web.1]: Process exited with status 0
2012-11-02T05:30:07+00:00 heroku[web.1]: State changed from starting to up
2012-11-02T05:31:06+00:00 heroku[router]: Error H99 (Platform error) -> GET staging-punda.herokuapp.com/ dyno= queue= wait= service= status=503 bytes=
2012-11-02T05:31:50+00:00 heroku[router]: Error H99 (Platform error) -> GET staging-punda.herokuapp.com/ dyno= queue= wait= service= status=503 bytes=
2012-11-02T05:33:50+00:00 heroku[router]: Error H99 (Platform error) -> GET staging-punda.herokuapp.com/ dyno= queue= wait= service= status=503 bytes=
2012-11-02T05:36:05+00:00 heroku[router]: Error H99 (Platform error) -> GET staging-punda.herokuapp.com/ dyno= queue= wait= service= status=503 bytes=