I deployed my yeoman fullstack app and I get an 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 am trying to deploy an application on heroku for the first time.Any pointers to fix this?
I have followed regular tutorials to get this up on heroky, used grunt build and grunt dist:serve and it runs just fine locally without any errors.
My logs look like this:
2016-03-31T01:04:08.910519+00:00 heroku[web.1]: State changed from starting to crashed
2016-03-31T02:27:45.799910+00:00 heroku[web.1]: State changed from crashed to starting
2016-03-31T02:27:47.434640+00:00 heroku[web.1]: Starting process with command `npm start`
2016-03-31T02:27:49.777251+00:00 app[web.1]:
2016-03-31T02:27:49.777274+00:00 app[web.1]: > angular-test#0.0.0 start /app
2016-03-31T02:27:49.777275+00:00 app[web.1]: > node server/app.js
2016-03-31T02:27:49.777275+00:00 app[web.1]:
2016-03-31T02:27:50.437299+00:00 app[web.1]: fs.js:892
2016-03-31T02:27:50.437312+00:00 app[web.1]: return binding.stat(pathModule._makeLong(path));
2016-03-31T02:27:50.437313+00:00 app[web.1]: ^
2016-03-31T02:27:50.437313+00:00 app[web.1]:
2016-03-31T02:27:50.437314+00:00 app[web.1]: Error: ENOENT: no such file or directory, stat '/app/public/favicon.ico'
2016-03-31T02:27:50.437314+00:00 app[web.1]: at Error (native)
2016-03-31T02:27:50.437315+00:00 app[web.1]: at Object.fs.statSync (fs.js:892:18)
2016-03-31T02:27:50.437316+00:00 app[web.1]: at favicon (/app/node_modules/serve-favicon/index.js:47:15)
2016-03-31T02:27:50.437316+00:00 app[web.1]: at module.exports (/app/server/config/express.js:35:13)
2016-03-31T02:27:50.437328+00:00 app[web.1]: at Object.<anonymous> (/app/server/app.js:27:28)
2016-03-31T02:27:50.437329+00:00 app[web.1]: at Module._compile (module.js:413:34)
2016-03-31T02:27:50.437330+00:00 app[web.1]: at Object.Module._extensions..js (module.js:422:10)
2016-03-31T02:27:50.437330+00:00 app[web.1]: at Module.load (module.js:357:32)
2016-03-31T02:27:50.437331+00:00 app[web.1]: at Function.Module._load (module.js:314:12)
2016-03-31T02:27:50.437331+00:00 app[web.1]: at Function.Module.runMain (module.js:447:10)
2016-03-31T02:27:50.437332+00:00 app[web.1]: at startup (node.js:142:18)
2016-03-31T02:27:50.437332+00:00 app[web.1]: at node.js:939:3
2016-03-31T02:27:50.446714+00:00 app[web.1]:
2016-03-31T02:27:50.455228+00:00 app[web.1]: npm ERR! Linux 3.13.0-79-generic
2016-03-31T02:27:50.455710+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-03-31T02:27:50.455963+00:00 app[web.1]: npm ERR! node v5.9.1
2016-03-31T02:27:50.456507+00:00 app[web.1]: npm ERR! npm v3.7.3
2016-03-31T02:27:50.456774+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2016-03-31T02:27:50.456952+00:00 app[web.1]: npm ERR! angular-test#0.0.0 start: `node server/app.js`
2016-03-31T02:27:50.457115+00:00 app[web.1]: npm ERR! Exit status 1
2016-03-31T02:27:50.457427+00:00 app[web.1]: npm ERR!
2016-03-31T02:27:50.457580+00:00 app[web.1]: npm ERR! Failed at the angular-test#0.0.0 start script 'node server/app.js'.
2016-03-31T02:27:50.457778+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm installed.
2016-03-31T02:27:50.457968+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the angular-test package,
2016-03-31T02:27:50.458168+00:00 app[web.1]: npm ERR! not with npm itself.
2016-03-31T02:27:50.458354+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2016-03-31T02:27:50.458728+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2016-03-31T02:27:50.458538+00:00 app[web.1]: npm ERR! node server/app.js
2016-03-31T02:27:50.458921+00:00 app[web.1]: npm ERR! npm bugs angular-test
2016-03-31T02:27:50.459097+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-03-31T02:27:50.460235+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-03-31T02:27:50.460234+00:00 app[web.1]: npm ERR! npm owner ls angular-test
2016-03-31T02:27:50.465300+00:00 app[web.1]:
2016-03-31T02:27:50.465522+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-03-31T02:27:50.465631+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-03-31T02:27:51.249320+00:00 heroku[web.1]: State changed from starting to crashed
2016-03-31T02:27:51.235239+00:00 heroku[web.1]: Process exited with status 1
2016-03-31T05:14:03.873070+00:00 heroku[web.1]: State changed from crashed to starting
2016-03-31T05:14:05.244594+00:00 heroku[web.1]: Starting process with command `npm start`
2016-03-31T05:14:07.170039+00:00 app[web.1]:
2016-03-31T05:14:07.170054+00:00 app[web.1]: > angular-test#0.0.0 start /app
2016-03-31T05:14:07.170055+00:00 app[web.1]: > node server/app.js
2016-03-31T05:14:07.170056+00:00 app[web.1]:
2016-03-31T05:14:07.671688+00:00 app[web.1]: fs.js:892
2016-03-31T05:14:07.671722+00:00 app[web.1]: return binding.stat(pathModule._makeLong(path));
2016-03-31T05:14:07.671723+00:00 app[web.1]: ^
2016-03-31T05:14:07.671724+00:00 app[web.1]:
2016-03-31T05:14:07.671731+00:00 app[web.1]: Error: ENOENT: no such file or directory, stat '/app/public/favicon.ico'
2016-03-31T05:14:07.671731+00:00 app[web.1]: at Error (native)
2016-03-31T05:14:07.671732+00:00 app[web.1]: at Object.fs.statSync (fs.js:892:18)
2016-03-31T05:14:07.671733+00:00 app[web.1]: at favicon (/app/node_modules/serve-favicon/index.js:47:15)
2016-03-31T05:14:07.671733+00:00 app[web.1]: at module.exports (/app/server/config/express.js:35:13)
2016-03-31T05:14:07.671734+00:00 app[web.1]: at Object.<anonymous> (/app/server/app.js:27:28)
2016-03-31T05:14:07.671734+00:00 app[web.1]: at Module._compile (module.js:413:34)
2016-03-31T05:14:07.671735+00:00 app[web.1]: at Object.Module._extensions..js (module.js:422:10)
2016-03-31T05:14:07.671735+00:00 app[web.1]: at Module.load (module.js:357:32)
2016-03-31T05:14:07.671736+00:00 app[web.1]: at Function.Module._load (module.js:314:12)
2016-03-31T05:14:07.671736+00:00 app[web.1]: at Function.Module.runMain (module.js:447:10)
2016-03-31T05:14:07.671737+00:00 app[web.1]: at startup (node.js:142:18)
2016-03-31T05:14:07.671738+00:00 app[web.1]: at node.js:939:3
2016-03-31T05:14:07.685504+00:00 app[web.1]:
2016-03-31T05:14:07.696144+00:00 app[web.1]: npm ERR! Linux 3.13.0-77-generic
2016-03-31T05:14:07.696638+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-03-31T05:14:07.696930+00:00 app[web.1]: npm ERR! node v5.9.1
2016-03-31T05:14:07.697704+00:00 app[web.1]: npm ERR! npm v3.7.3
2016-03-31T05:14:07.697991+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2016-03-31T05:14:07.698208+00:00 app[web.1]: npm ERR! angular-test#0.0.0 start: `node server/app.js`
2016-03-31T05:14:07.698406+00:00 app[web.1]: npm ERR! Exit status 1
2016-03-31T05:14:07.698612+00:00 app[web.1]: npm ERR!
2016-03-31T05:14:07.698816+00:00 app[web.1]: npm ERR! Failed at the angular-test#0.0.0 start script 'node server/app.js'.
2016-03-31T05:14:07.699013+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm installed.
2016-03-31T05:14:07.699208+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the angular-test package,
2016-03-31T05:14:07.699396+00:00 app[web.1]: npm ERR! not with npm itself.
2016-03-31T05:14:07.699601+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
2016-03-31T05:14:07.699789+00:00 app[web.1]: npm ERR! node server/app.js
2016-03-31T05:14:07.700018+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with:
2016-03-31T05:14:07.700228+00:00 app[web.1]: npm ERR! npm bugs angular-test
2016-03-31T05:14:07.700419+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via:
2016-03-31T05:14:07.700613+00:00 app[web.1]: npm ERR! npm owner ls angular-test
2016-03-31T05:14:07.700803+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
2016-03-31T05:14:07.706094+00:00 app[web.1]:
2016-03-31T05:14:07.706368+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-03-31T05:14:07.706545+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-03-31T05:14:08.424826+00:00 heroku[web.1]: State changed from starting to crashed
2016-03-31T05:14:08.402585+00:00 heroku[web.1]: Process exited with status 1
2016-03-31T08:32:27.825054+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mozzoweb.herokuapp.com request_id=28e3e7fd-8664-400b-8e78-8cf4809086ef fwd="120.59.15.145" dyno= connect= service= status=503 bytes=
2016-03-31T08:32:28.447942+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mozzoweb.herokuapp.com request_id=3989001b-7a89-4aab-8461-e81d0dff0617 fwd="120.59.15.145" dyno= connect= service= status=503 bytes=
2016-03-31T08:32:38.385147+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mozzoweb.herokuapp.com request_id=098cabd0-15ed-43f3-98b9-01c3130b1420 fwd="120.59.15.145" dyno= connect= service= status=503 bytes=
2016-03-31T08:32:39.202068+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mozzoweb.herokuapp.com request_id=003a4589-f69c-4219-86cf-5c8e85c1bfb9 fwd="120.59.15.145" dyno= connect= service= status=503 bytes=
2016-03-31T08:35:40.667394+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mozzoweb.herokuapp.com request_id=ad81d2ef-4452-434c-b8e1-bd4935b372b5 fwd="120.59.15.145" dyno= connect= service= status=503 bytes=
[10860:10860:0331/140541:ERROR:navigation_entry_screenshot_manager.cc(141)] Invalid entry with unique id: 252
2016-03-31T08:35:41.674390+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mozzoweb.herokuapp.com request_id=44245240-90ba-4836-bd79-ee37d69ddfad fwd="120.59.15.145" dyno= connect= service= status=503 bytes=
Related
I created sinatra app and trying to deploy it on Heroku. When I push heroku with git push heroku master, it looks the app is successfully deployed but then when I implement heroku open it shows application error.
I created app using sinatra with postgresql DB.
I tried many stuffs but really can't figure out what actually causes the error.
I tried
・Destroyed and recreated heroku app.
・Uninstalled bundler and installed 1.15.2 since 1.17.2 which was installed at first did not work.
・Deleted Gem file and recreated.
・Tried puma.(also modified Procfile with web: bundle exec puma -C config/puma.rb)
etc..
$ git push heroku master
Enumerating objects: 573, done.
Counting objects: 100% (573/573), done.
Delta compression using up to 4 threads
Compressing objects: 100% (559/559), done.
Writing objects: 100% (573/573), 15.77 MiB | 219.00 KiB/s, done.
Total 573 (delta 314), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Ruby app detected
remote: -----> Compiling Ruby/Rack
remote: -----> Using Ruby version: ruby-2.6.3
remote: -----> Installing dependencies using bundler 1.15.2
remote: Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
remote: Fetching gem metadata from https://rubygems.org/.........
remote: Fetching backports 3.15.0
remote: Using bundler 1.17.2
remote: Fetching mustermann 1.0.3
remote: Fetching multi_json 1.13.1
remote: Installing mustermann 1.0.3
remote: Installing multi_json 1.13.1
remote: Installing backports 3.15.0
remote: Fetching nio4r 2.5.1
remote: Installing nio4r 2.5.1 with native extensions
remote: Fetching pg 1.1.4
remote: Installing pg 1.1.4 with native extensions
remote: Fetching rack 2.0.7
remote: Installing rack 2.0.7
remote: Fetching tilt 2.0.9
remote: Installing tilt 2.0.9
remote: Fetching rack-protection 2.0.7
remote: Installing rack-protection 2.0.7
remote: Fetching sinatra 2.0.7
remote: Installing sinatra 2.0.7
remote: Fetching sinatra-contrib 2.0.7
remote: Installing sinatra-contrib 2.0.7
remote: Fetching puma 4.1.1
remote: Installing puma 4.1.1 with native extensions
remote: Bundle complete! 5 Gemfile dependencies, 12 gems now installed.
remote: Gems in the groups development and test were not installed.
remote: Bundled gems are installed into `./vendor/bundle`
remote: Removing bundler (1.15.2)
remote: Bundle completed (20.07s)
remote: Cleaning up the bundler cache.
remote: -----> Writing config/database.yml to read from DATABASE_URL
remote: -----> Detecting rake tasks
remote:
remote:
remote: -----> Discovering process types
remote: Procfile declares types -> web
remote: Default types for buildpack -> console, rake
remote:
remote: -----> Compressing...
remote: Done: 30.1M
remote: -----> Launching...
remote: Released v6
remote: https://ancient-crag-43793.herokuapp.com/ deployed to Heroku
remote:
remote: Verifying deploy... done.
To https://git.heroku.com/ancient-crag-43793.git
* [new branch] master -> master
$ heroku logs
2019-09-12T03:13:52.000000+00:00 app[api]: Build succeeded
2019-09-12T03:13:53.745451+00:00 heroku[web.1]: Starting process with command `bundle exec ruby app.rb -p 36930`
2019-09-12T03:13:56.583038+00:00 heroku[web.1]: State changed from starting to crashed
2019-09-12T03:13:56.587379+00:00 heroku[web.1]: State changed from crashed to starting
2019-09-12T03:13:56.555987+00:00 heroku[web.1]: Process exited with status 1
2019-09-12T03:13:56.503859+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `initialize': could not connect to server: Connection refused (PG::ConnectionBad)
2019-09-12T03:13:56.503879+00:00 app[web.1]: Is the server running on host "localhost" (127.0.0.1) and accepting
2019-09-12T03:13:56.503881+00:00 app[web.1]: TCP/IP connections on port 5432?
2019-09-12T03:13:56.503883+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `new'
2019-09-12T03:13:56.503885+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `connect'
2019-09-12T03:13:56.503887+00:00 app[web.1]: from app.rb:11:in `<main>'
2019-09-12T03:13:58.532988+00:00 heroku[web.1]: Starting process with command `bundle exec ruby app.rb -p 33962`
2019-09-12T03:14:01.220318+00:00 heroku[web.1]: State changed from starting to crashed
2019-09-12T03:14:01.136864+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `initialize': could not connect to server: Connection refused (PG::ConnectionBad)
2019-09-12T03:14:01.136884+00:00 app[web.1]: Is the server running on host "localhost" (127.0.0.1) and accepting
2019-09-12T03:14:01.136886+00:00 app[web.1]: TCP/IP connections on port 5432?
2019-09-12T03:14:01.136888+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `new'
2019-09-12T03:14:01.136890+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `connect'
2019-09-12T03:14:01.136892+00:00 app[web.1]: from app.rb:11:in `<main>'
2019-09-12T03:14:01.197593+00:00 heroku[web.1]: Process exited with status 1
2019-09-12T03:16:16.795355+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=ancient-crag-43793.herokuapp.com request_id=8859880d-47b9-49f9-b847-2a02099bc855 fwd="106.181.207.226" dyno= connect= service= status=503 bytes= protocol=https
2019-09-12T03:16:17.126133+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/robots.txt" host=ancient-crag-43793.herokuapp.com request_id=5d0bd878-aed7-4625-acc4-86f40c801a46 fwd="106.181.207.226" dyno= connect= service= status=503 bytes= protocol=https
2019-09-12T03:16:17.639402+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=ancient-crag-43793.herokuapp.com request_id=91cb566e-dc2c-4806-9790-3b3ba4b72ec3 fwd="106.181.207.226" dyno= connect= service= status=503 bytes= protocol=https
2019-09-12T03:20:09.313587+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=ancient-crag-43793.herokuapp.com request_id=9a8430b7-14c9-4794-9de1-69f319b7ec67 fwd="106.181.207.226" dyno= connect= service= status=503 bytes= protocol=https
2019-09-12T03:20:10.696885+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/robots.txt" host=ancient-crag-43793.herokuapp.com request_id=0a479063-1e8e-40bb-82c9-4d149150fe11 fwd="106.181.207.226" dyno= connect= service= status=503 bytes= protocol=https
2019-09-12T03:20:11.220968+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=ancient-crag-43793.herokuapp.com request_id=a74ee463-52af-458b-aab9-11181287089a fwd="106.181.207.226" dyno= connect= service= status=503 bytes= protocol=https
2019-09-12T03:38:07.360350+00:00 heroku[web.1]: State changed from crashed to starting
2019-09-12T03:38:09.195028+00:00 heroku[web.1]: Starting process with command `bundle exec ruby app.rb -p 21707`
2019-09-12T03:38:12.014593+00:00 heroku[web.1]: State changed from starting to crashed
2019-09-12T03:38:11.945704+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `initialize': could not connect to server: Connection refused (PG::ConnectionBad)
2019-09-12T03:38:11.945730+00:00 app[web.1]: Is the server running on host "localhost" (127.0.0.1) and accepting
2019-09-12T03:38:11.945732+00:00 app[web.1]: TCP/IP connections on port 5432?
2019-09-12T03:38:11.945778+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `new'
2019-09-12T03:38:11.945780+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `connect'
2019-09-12T03:38:11.945786+00:00 app[web.1]: from app.rb:11:in `<main>'
2019-09-12T03:38:11.997334+00:00 heroku[web.1]: Process exited with status 1
2019-09-12T03:42:21.000000+00:00 app[api]: Build started by user "my email address"
2019-09-12T03:42:28.853379+00:00 heroku[web.1]: State changed from crashed to starting
2019-09-12T03:42:28.539461+00:00 app[api]: Deploy 00584404 by user "my email address"
2019-09-12T03:42:28.539461+00:00 app[api]: Release v7 created by user "my email address"
2019-09-12T03:42:29.000000+00:00 app[api]: Build succeeded
2019-09-12T03:42:30.598759+00:00 heroku[web.1]: Starting process with command `bundle exec ruby app.rb -p 12078`
2019-09-12T03:42:33.295521+00:00 heroku[web.1]: State changed from starting to crashed
2019-09-12T03:42:33.282712+00:00 heroku[web.1]: Process exited with status 1
2019-09-12T03:42:33.217024+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `initialize': could not connect to server: Connection refused (PG::ConnectionBad)
2019-09-12T03:42:33.217056+00:00 app[web.1]: Is the server running on host "localhost" (127.0.0.1) and accepting
2019-09-12T03:42:33.217059+00:00 app[web.1]: TCP/IP connections on port 5432?
2019-09-12T03:42:33.217077+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `new'
2019-09-12T03:42:33.217080+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.6.0/gems/pg-1.1.4/lib/pg.rb:56:in `connect'
2019-09-12T03:42:33.217087+00:00 app[web.1]: from app.rb:11:in `<main>'
2019-09-12T03:43:03.364089+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=ancient-crag-43793.herokuapp.com request_id=f70df879-4c32-4d96-a669-266609b48f93 fwd="106.181.207.226" dyno= connect= service= status=503 bytes= protocol=https
2019-09-12T03:43:04.119899+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=ancient-crag-43793.herokuapp.com request_id=fb27aee3-f2e8-4af8-98c1-ce9479052001 fwd="106.181.207.226" dyno= connect= service= status=503 bytes= protocol=https
could not connect to server: Connection refused (PG::ConnectionBad)
Is DB somehow causing the error..?
app.rb
require 'sinatra'
require 'sinatra/reloader'
require 'sinatra/cookies'
require 'pg'
require 'bundler/setup'
Bundler.require
enable :sessions
client = PG::connect(
:host => "localhost",
:user => 'tomoyo', :password => '',
:dbname => "myapp")
I've managed to push https://github.com/hexojs/hexo to heroku but when I view app at http://warm-shelf-26895.herokuapp.com/ it failed completely.
I'm new to this can anybody tell me what went wrong and how to solve this ? TQ
$heroku logs
2016-04-08T09:04:12.913757+00:00 heroku[api]: Enable Logplex by kradzcalypse#icloud.com
2016-04-08T09:04:12.913787+00:00 heroku[api]: Release v2 created by kradzcalypse#icloud.com
2016-04-08T09:45:15.587805+00:00 heroku[api]: Scale to web=1 by kradzcalypse#icloud.com
2016-04-08T09:45:15.669657+00:00 heroku[api]: Deploy fcfe397 by kradzcalypse#icloud.com
2016-04-08T09:45:15.669657+00:00 heroku[api]: Release v3 created by kradzcalypse#icloud.com
2016-04-08T09:45:16.046236+00:00 heroku[slug-compiler]: Slug compilation started
2016-04-08T09:45:16.046251+00:00 heroku[slug-compiler]: Slug compilation finished
2016-04-08T09:45:17.763235+00:00 heroku[web.1]: Starting process with command `npm start`
2016-04-08T09:45:19.851147+00:00 app[web.1]: npm ERR! Linux 3.13.0-79-generic
2016-04-08T09:45:19.851749+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-04-08T09:45:19.852084+00:00 app[web.1]: npm ERR! node v5.10.0
2016-04-08T09:45:19.852499+00:00 app[web.1]: npm ERR! npm v3.8.3
2016-04-08T09:45:19.853761+00:00 app[web.1]:
2016-04-08T09:45:19.854672+00:00 app[web.1]: npm ERR! missing script: start
2016-04-08T09:45:19.854860+00:00 app[web.1]: npm ERR!
2016-04-08T09:45:19.855012+00:00 app[web.1]: npm ERR! If you need help, you may report this error at:
2016-04-08T09:45:19.855162+00:00 app[web.1]: npm ERR! <https://github.com/npm/npm/issues>
2016-04-08T09:45:19.862944+00:00 app[web.1]:
2016-04-08T09:45:19.863162+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-04-08T09:45:19.863322+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-04-08T09:45:20.533551+00:00 heroku[web.1]: Process exited with status 1
2016-04-08T09:45:20.555438+00:00 heroku[web.1]: State changed from starting to crashed
2016-04-08T09:45:20.555438+00:00 heroku[web.1]: State changed from crashed to starting
2016-04-08T09:45:22.881666+00:00 heroku[web.1]: Starting process with command `npm start`
2016-04-08T09:45:26.272162+00:00 app[web.1]: npm ERR! Linux 3.13.0-79-generic
2016-04-08T09:45:26.273164+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-04-08T09:45:26.273607+00:00 app[web.1]: npm ERR! node v5.10.0
2016-04-08T09:45:26.274846+00:00 app[web.1]: npm ERR! npm v3.8.3
2016-04-08T09:45:26.277179+00:00 app[web.1]:
2016-04-08T09:45:26.278900+00:00 app[web.1]: npm ERR! missing script: start
2016-04-08T09:45:26.279148+00:00 app[web.1]: npm ERR!
2016-04-08T09:45:26.279341+00:00 app[web.1]: npm ERR! If you need help, you may report this error at:
2016-04-08T09:45:26.281819+00:00 app[web.1]: npm ERR! <https://github.com/npm/npm/issues>
2016-04-08T09:45:26.292949+00:00 app[web.1]:
2016-04-08T09:45:26.293196+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-04-08T09:45:26.293328+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-04-08T09:45:27.124881+00:00 heroku[web.1]: Process exited with status 1
2016-04-08T09:45:27.140895+00:00 heroku[web.1]: State changed from starting to crashed
2016-04-08T09:45:30.487088+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=warm-shelf-26895.herokuapp.com request_id=e68542c6-df1f-45f4-9d91-db7b1d8dd946 fwd="175.140.32.164" dyno= connect= service= status=503 bytes=
2016-04-08T09:45:31.041140+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=warm-shelf-26895.herokuapp.com request_id=2de0617a-7eeb-48a9-b52d-b8a46173d937 fwd="175.140.32.164" dyno= connect= service= status=503 bytes=
2016-04-08T09:46:38.285172+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=warm-shelf-26895.herokuapp.com request_id=4b14dd49-1fdc-4875-ac22-824c5d37882e fwd="175.140.32.164" dyno= connect= service= status=503 bytes=
2016-04-08T09:46:38.945206+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=warm-shelf-26895.herokuapp.com request_id=ebf705e1-bdb6-4920-91c8-3a2c9ca6f886 fwd="175.140.32.164" dyno= connect= service= status=503 bytes=
2016-04-08T09:58:59.898426+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=warm-shelf-26895.herokuapp.com request_id=5b02691f-9a0a-417a-be78-6dad9cf03166 fwd="175.140.32.164" dyno= connect= service= status=503 bytes=
2016-04-08T09:59:00.442958+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=warm-shelf-26895.herokuapp.com request_id=eee3f185-f71b-416e-a0e8-2755b232029d fwd="175.140.32.164" dyno= connect= service= status=503 bytes=
2016-04-08T10:09:10.794586+00:00 heroku[web.1]: State changed from crashed to starting
2016-04-08T10:09:12.937261+00:00 heroku[web.1]: Starting process with command `npm start`
2016-04-08T10:09:15.021924+00:00 app[web.1]: npm ERR! Linux 3.13.0-79-generic
2016-04-08T10:09:15.022475+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
2016-04-08T10:09:15.022808+00:00 app[web.1]: npm ERR! node v5.10.0
2016-04-08T10:09:15.023416+00:00 app[web.1]: npm ERR! npm v3.8.3
2016-04-08T10:09:15.025088+00:00 app[web.1]:
2016-04-08T10:09:15.026532+00:00 app[web.1]: npm ERR! missing script: start
2016-04-08T10:09:15.026673+00:00 app[web.1]: npm ERR!
2016-04-08T10:09:15.026844+00:00 app[web.1]: npm ERR! <https://github.com/npm/npm/issues>
2016-04-08T10:09:15.026761+00:00 app[web.1]: npm ERR! If you need help, you may report this error at:
2016-04-08T10:09:15.035679+00:00 app[web.1]:
2016-04-08T10:09:15.035839+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
2016-04-08T10:09:15.035928+00:00 app[web.1]: npm ERR! /app/npm-debug.log
2016-04-08T10:09:15.765024+00:00 heroku[web.1]: State changed from starting to crashed
2016-04-08T10:09:15.740933+00:00 heroku[web.1]: Process exited with status 1
2016-04-08T10:25:12.503232+00:00 heroku[slug-compiler]: Slug compilation started
2016-04-08T10:25:12.503240+00:00 heroku[slug-compiler]: Slug compilation failed: failed to detect set buildpack heroku/nodejs
2016-04-08T10:25:12.503242+00:00 heroku[slug-compiler]: More info: https://devcenter.heroku.com/articles/buildpacks#detection-failure
2016-04-08T10:26:22.776928+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=warm-shelf-26895.herokuapp.com request_id=74d90d49-75ed-4fbc-a0c6-b463bf599c8b fwd="175.140.32.164" dyno= connect= service= status=503 bytes=
2016-04-08T10:26:23.745972+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=warm-shelf-26895.herokuapp.com request_id=59c101ef-28af-4c01-bb9a-644e86077a01 fwd="175.140.32.164" dyno= connect= service= status=503 bytes=
You should include a scripts section in your package.json specifying the correct node command you use to start your application. e.g.:
scripts": {
"test": "echo \"Error: no test specified\" && exit 1",
"start": "node app.js"
},
I cannot get my app to deploy to Heroku. So frustrating.
Here is the repository: repository link
Things I have tried:
I have updated my config.ru with everything I need per the heroku deployment page found here
I have run heroku run rake db:migrate
I have run heroku restart
I have ensured I have an updated gemfile
I double checked that I have the 'require' statements in my app.rb
Any thoughts? My error logs I am getting are below:
2014-11-02T03:46:07.404128+00:00 heroku[api]: Deploy bbe19c1 by johnsalzarulo#gmail.com
2014-11-02T03:46:07.404202+00:00 heroku[api]: Release v17 created by johnsalzarulo#gmail.com
2014-11-02T03:46:08.439283+00:00 heroku[web.1]: State changed from crashed to starting
2014-11-02T03:46:11.353727+00:00 heroku[web.1]: Starting process with command `bundle exec rackup config.ru -p 43798`
2014-11-02T03:46:13.210413+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/builder.rb:55:in `initialize'
2014-11-02T03:46:13.210411+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/builder.rb:55:in `instance_eval'
2014-11-02T03:46:13.210388+00:00 app[web.1]: /app/config.ru:1:in `require': cannot load such file -- ./gifinder (LoadError)
2014-11-02T03:46:13.210410+00:00 app[web.1]: from /app/config.ru:1:in `block in <main>'
2014-11-02T03:46:13.210424+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/server.rb:199:in `app'
2014-11-02T03:46:13.210425+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/server.rb:314:in `wrapped_app'
2014-11-02T03:46:13.210414+00:00 app[web.1]: from /app/config.ru:in `new'
2014-11-02T03:46:13.210415+00:00 app[web.1]: from /app/config.ru:in `<main>'
2014-11-02T03:46:13.210417+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/builder.rb:49:in `eval'
2014-11-02T03:46:13.210419+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/builder.rb:40:in `parse_file'
2014-11-02T03:46:13.210418+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/builder.rb:49:in `new_from_string'
2014-11-02T03:46:13.210421+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/server.rb:277:in `build_app_and_options_from_config'
2014-11-02T03:46:13.210427+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/server.rb:250:in `start'
2014-11-02T03:46:13.210430+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/lib/rack/server.rb:141:in `start'
2014-11-02T03:46:13.210432+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/gems/rack-1.5.2/bin/rackup:4:in `<top (required)>'
2014-11-02T03:46:13.210434+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/bin/rackup:23:in `load'
2014-11-02T03:46:13.210437+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.1.0/bin/rackup:23:in `<main>'
2014-11-02T03:46:13.977897+00:00 heroku[web.1]: State changed from starting to crashed
2014-11-02T03:46:13.970947+00:00 heroku[web.1]: Process exited with status 1
2014-11-02T03:46:15.252296+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=gifinder.herokuapp.com request_id=7106f663-fa15-4c74-ab8e-f5df75030a55 fwd="174.129.111.111" dyno= connect= service= status=503 bytes=
2014-11-02T03:46:42.265175+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=gifinder.herokuapp.com request_id=900cbb04-7ee9-4392-9f2f-7d4e833b15c0 fwd="24.43.108.83" dyno= connect= service= status=503 bytes=
2014-11-02T03:46:43.407062+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=gifinder.herokuapp.com request_id=ce46eed0-4a7f-4633-81ec-c826a3c90e30 fwd="24.43.108.83" dyno= connect= service= status=503 bytes=
Your config.ru file is trying to load a non-existent file with the require statement. Change this line require './gifinder' to:
require './app'
or, change the filename of app.rb to gifinder.rb. You should also follow iain's advice and remove the double Gemfile.lock because that's bound to cause problems.
Your require for HTTParty should also be lowercase. I fetched your repo and got it work on heroku by changing the require to all lowercase:
require 'httparty'
I don't know how you've done it, but you have two Gemfile.locks. I'd remove them both and re-run Bundler, and git rm the one that shouldn't be there.
Also note that Heroku now uses procfiles more extensively than previously, so get hold of Foreman and define a procfile.
In addition, when I run bundle install --binstubs --path=vendor I get this message:
Post-install message from heroku: ! The heroku gem has been
deprecated and replaced with the Heroku Toolbelt. ! Download and
install from: https://toolbelt.heroku.com ! For API access, see:
https://github.com/heroku/heroku.rb
so remove gem 'heroku', '~> 3.15.0' from the Gemfile and require 'heroku' (which was never needed in the app anyway) from app.rb. When I do that, the command bin/rackup config.ru runs the app for me on localhost:9292 just fine.
I am new to heroku and sinatra, but I have my app running locally just fine with sinatra and sqlite3. I know heroku doesn't support sqlite3, so I tried this answer: Deploy RoR to Heroku and Sqlite3 fails
When I pushed to heroku and tried to access it, I got an error. So I checked the logs. This is what I am seeing. I saw others on here with the same issue, but the resolutions have all been varied and I have tried restarting heroku:
2013-08-15T05:07:17+00:00 heroku[slug-compiler]: Slug compilation finished
2013-08-15T05:07:21.550961+00:00 heroku[web.1]: Starting process with command `bundle exec rackup config.ru -p 28820`
2013-08-15T05:07:25.339314+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/sinatra-activerecord-1.2.3/lib/sinatra/activerecord.rb:23:in `database'
2013-08-15T05:07:25.339314+00:00 app[web.1]: from /app/app.rb:7:in `<top (required)>'
2013-08-15T05:07:25.339314+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/sinatra-activerecord-1.2.3/lib/sinatra/activerecord.rb:17:in `database='
2013-08-15T05:07:25.339314+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-08-15T05:07:25.339488+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-08-15T05:07:25.339488+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-08-15T05:07:25.339314+00:00 app[web.1]: from /app/config.ru:2:in `block in <main>'
2013-08-15T05:07:25.339488+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-08-15T05:07:25.339770+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-08-15T05:07:25.339314+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_handling.rb:39:in `establish_connection'
2013-08-15T05:07:25.339488+00:00 app[web.1]: from /app/config.ru:in `<main>'
2013-08-15T05:07:25.339770+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-08-15T05:07:25.339194+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/connection_specification.rb:46:in `resolve_string_connection'
2013-08-15T05:07:25.339488+00:00 app[web.1]: from /app/config.ru:in `new'
2013-08-15T05:07:25.339770+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/bin/rackup:23:in `load'
2013-08-15T05:07:25.339194+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/connection_specification.rb:32:in `spec'
2013-08-15T05:07:25.339314+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-08-15T05:07:25.339488+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-08-15T05:07:25.339079+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/connection_specification.rb:58:in `rescue in resolve_hash_connection': Specified 'sqlite3' for database adapter, but the gem is not loaded. Add `gem 'sqlite3'` to your Gemfile. (Gem::LoadError)
2013-08-15T05:07:25.339314+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/sinatra-1.4.3/lib/sinatra/base.rb:1191:in `set'
2013-08-15T05:07:25.339079+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/activerecord-4.0.0/lib/active_record/connection_adapters/connection_specification.rb:55:in `resolve_hash_connection'
2013-08-15T05:07:25.339314+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/sinatra-1.4.3/lib/sinatra/base.rb:1917:in `block (2 levels) in delegate'
2013-08-15T05:07:25.339488+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-08-15T05:07:25.339314+00:00 app[web.1]: from /app/config.ru:2:in `require'
2013-08-15T05:07:25.339770+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-08-15T05:07:25.339770+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/bin/rackup:23:in `<main>'
2013-08-15T05:07:25.339770+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-08-15T05:07:27.328918+00:00 heroku[web.1]: Process exited with status 1
2013-08-15T05:07:27.341978+00:00 heroku[web.1]: State changed from starting to crashed
2013-08-15T05:07:28.551518+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=intense-depths-3455.herokuapp.com fwd="70.179.10.147" dyno= connect= service= status=503 bytes=
2013-08-15T05:07:29.149180+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=intense-depths-3455.herokuapp.com fwd="70.179.10.147" dyno= connect= service= status=503 bytes=
any ideas on how I can get this to work?
my config ru is:
#config.ru
require "./app"
run Sinatra::Application
and my gemfile is:
source 'https://rubygems.org'
gem "sinatra"
gem "activerecord"
gem "sinatra-activerecord"
gem "pony"
group :development do
gem "shotgun"
gem "tux"
gem "sqlite3", "~> 1.3.7", :require => "sqlite3"
end
I was able to get it to work by adding a line to use postgresql in production.
i am having this problem on my heroku server
at=error code=H14 desc="No web processes running"
i attempted to run
heroku ps:scale web=1
but receive this error
Scaling web processes... failed
! No such type as web
heroku ps:restart web.1 --app dashboardaudi88
Restarting web.1 process... done
and here are the heroku logs
heroku logs
2012-12-08T21:14:46+00:00 app[web.1]: -d, [--database=DATABASE] # Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db/sqlserver/jdbcmysql/jdbcsqlite3/jdbcpostgresql/jdbc)
2012-12-08T21:14:46+00:00 app[web.1]: [--dev] # Setup the application with Gemfile pointing to your Rails checkout
2012-12-08T21:14:46+00:00 app[web.1]: rails new APP_PATH [options]
2012-12-08T21:14:46+00:00 app[web.1]: # Default: /usr/local/bin/ruby
2012-12-08T21:14:46+00:00 app[web.1]: -m, [--template=TEMPLATE] # Path to an application template (can be a filesystem path or URL)
2012-12-08T21:14:46+00:00 app[web.1]: -f, [--force] # Overwrite files that already exist
2012-12-08T21:14:46+00:00 app[web.1]: -v, [--version] # Show Rails version number and quit
2012-12-08T21:14:46+00:00 app[web.1]: -j, [--javascript=JAVASCRIPT] # Preconfigure for selected JavaScript library
2012-12-08T21:14:46+00:00 app[web.1]: [--old-style-hash] # Force using old style hash (:foo => 'bar') on Ruby >= 1.9
2012-12-08T21:14:46+00:00 app[web.1]:
2012-12-08T21:14:46+00:00 app[web.1]: Description:
2012-12-08T21:14:46+00:00 app[web.1]: -b, [--builder=BUILDER] # Path to a application builder (can be a filesystem path or URL)
2012-12-08T21:14:46+00:00 app[web.1]: # Default: sqlite3
2012-12-08T21:14:46+00:00 app[web.1]: [--edge] # Setup the application with Gemfile pointing to Rails repository
2012-12-08T21:14:46+00:00 app[web.1]: -q, [--quiet] # Suppress status output
2012-12-08T21:14:46+00:00 app[web.1]: -h, [--help] # Show this help message and quit
2012-12-08T21:14:46+00:00 app[web.1]:
2012-12-08T21:14:46+00:00 app[web.1
]: Options:
2012-12-08T21:14:46+00:00 app[web.1]: -r, [--ruby=PATH] # Path to the Ruby binary of your choice
2012-12-08T21:14:46+00:00 app[web.1]: [--skip-gemfile] # Don't create a Gemfile
2012-12-08T21:14:46+00:00 app[web.1]: [--skip-bundle] # Don't run bundle install
2012-12-08T21:14:46+00:00 app[web.1]: -G, [--skip-git] # Skip Git ignores and keeps
2012-12-08T21:14:46+00:00 app[web.1]: -O, [--skip-active-record] # Skip Active Record files
2012-12-08T21:14:46+00:00 app[web.1]: 'rails new' runs in the .railsrc configuration file in your home directory.
2012-12-08T21:14:46+00:00 app[web.1]: -J, [--skip-javascript] # Skip JavaScript files
2012-12-08T21:14:46+00:00 app[web.1]: -p, [--pretend] # Run but do not make any changes
2012-12-08T21:14:46+00:00 app[web.1]:
2012-12-08T21:14:46+00:00 app[web.1]: -s, [--skip] # Skip files that already exist
2012-12-08T21:14:46+00:00 app[web.1]: # Default: jquery
2012-12-08T21:14:46+00:00 app[web.1]: -T, [--skip-test-unit] # Skip Test::Unit files
2012-12-08T21:14:46+00:00 app[web.1]:
2012-12-08T21:14:46+00:00 app[web.1]: Runtime options:
2012-12-08T21:14:46+00:00 app[web.1]: Example:
2012-12-08T21:14:46+00:00 app[web.1]:
2012-12-08T21:14:46+00:00 app[web.1]: rails new ~/Code/Ruby/weblog
2012-12-08T21:14:46+00:00 app[web.1]:
2012-12-08T21:14:46+00:00 app[web.1]: See the README in the newly created application to get going.
2012-12-08T21:14:46+00:00 app[web.1]: This generates a skeletal Rails installation in ~/Code/Ruby/weblog.
2012-12-08T21:14:46+00:00 app[web.1]: The 'rails new' command creates a new Rails application with a default
2012-12-08T21:14:46+00:00 app[web.1]:
2012-12-08T21:14:46+00:00 app[web.1]: Rails options:
2012-12-08T21:14:46+00:00 app[web.1]: directory structure and configuration at the path you specify.
2012-12-08T21:14:46+00:00 app[web.1]:
2012-12-08T21:14:46+00:00 app[web.1]: You can specify extra command-line arguments to be used every time
2012-12-08T21:14:46+00:00 app[web.1]: Note that the arguments specified in the .railsrc file don't affect the
2012-12-08T21:14:46+00:00 app[web.1]: defaults values shown above in this help message.
2012-12-08T21:14:47+00:00 heroku[web.1]: State changed from starting to crashed
2012-12-08T21:14:47+00:00 heroku[web.1]: Process exited with status 0
2012-12-08T21:23:59+00:00 heroku[web.1]: State changed from crashed to starting
2012-12-08T21:24:02+00:00 heroku[web.1]: Starting process with command `bundle exec rails server -p 37045`
2012-12-08T21:24:06+00:00 app[web.1]: -r, [--ruby=PATH] # Path to the Ruby binary of your choice
2012-12-08T21:24:06+00:00 app[web.1]: [--skip-bundle] # Don't run bundle install
2012-12-08T21:24:06+00:00 app[web.1]:
2012-12-08T21:24:06+00:00 app[web.1]: -m, [--template=TEMPLATE] # Path to an application template (can be a filesystem path or URL)
2012-12-08T21:24:06+00:00 app[web.1]: # Default: /usr/local/bin/ruby
2012-12-08T21:24:06+00:00 app[web.1]: -G, [--skip-git] # Skip Git ignores and keeps
2012-12-08T21:24:06+00:00 app[web.1]: # Default: sqlite3
2012-12-08T21:24:06+00:00 app[web.1]: -d, [--database=DATABASE] # Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db/sqlserver/jdbcmysql/jdbcsqlite3/jdbcpostgresql/jdbc)
2012-12-08T21:24:06+00:00 app[web.1]: -O, [--skip-active-record] # Skip Active Record files
2012-12-08T21:24:06+00:00 app[web.1]: Options:
2012-12-08T21:24:06+00:00 app[web.1]: -j, [--javascript=JAVASCRIPT] # Preconfigure for selected JavaScript library
2012-12-08T21:24:06+00:00 app[web.1]: [--edge] # Setup the application with Gemfile pointing to Rails repository
2012-12-08T21:24:06+00:00 app[web.1]: Usage:
2012-12-08T21:24:06+00:00 app[web.1]: -b, [--builder=BUILDER] # Path to a application builder (can be a filesystem path or URL)
2012-12-08T21:24:06+00:00 app[web.1]: -S, [--skip-sprockets] # Skip Sprockets files
2012-12-08T21:24:06+00:00 app[web.1]: [--old-style-hash] # Force using old style hash (:foo => 'bar') on Ruby >= 1.9
2012-12-08T21:24:06+00:00 app[web.1]: -f, [--force] # Overwrite files that already exist
2012-12-08T21:24:06+00:00 app[web.1]: [--dev] # Setup the application with Gemfile pointing to your Rails checkout
2012-12-08T21:24:06+00:00 app[web.1]: # Default: jquery
2012-12-08T21:24:06+00:00 app[web.1]: -p, [--pretend] # Run but do not make any changes
2012-12-08T21:24:06+00:00 app[web.1]: -v, [--version] # Show Rails version number and quit
2012-12-08T21:24:06+00:00 app[web.1]: -J, [--skip-javascript] # Skip JavaScript files
2012-12-08T21:24:06+00:00 app[web.1]: -q, [--quiet] # Suppress status output
2012-12-08T21:24:06+00:00 app[web.1]: -h, [--help] # Show this help message and quit
2012-12-08T21:24:06+00:00 app[web.1]: -T, [--skip-test-unit] # Skip Test::Unit files
2012-12-08T21:24:06+00:00 app[web.1]:
2012-12-08T21:24:06+00:00 app[web.1]:
2012-12-08T21:24:06+00:00 app[web.1]:
2012-12-08T21:24:06+00:00 app[web.1]: -s, [--skip] # Skip files that already exist
2012-12-08T21:24:06+00:00 app[web.1]: Description:
2012-12-08T21:24:06+00:00 app[web.1]: rails new APP_PATH [options]
2012-12-08T21:24:06+00:00 app[web.1]: The 'rails new' command creates a new Rails application with a default
2012-12
-08T21:24:06+00:00 app[web.1]: defaults values shown above in this help message.
2012-12-08T21:24:06+00:00 app[web.1]: directory structure and configuration at the path you specify.
2012-12-08T21:24:06+00:00 app[web.1]: You can specify extra command-line arguments to be used every time
2012-12-08T21:24:06+00:00 app[web.1]: 'rails new' runs in the .railsrc configuration file in your home directory.
2012-12-08T21:24:06+00:00 app[web.1]:
2012-12-08T21:24:06+00:00 app[web.1]: Note that the arguments specified in the .railsrc file don't affect the
2012-12-08T21:24:06+00:00 app[web.1]:
2012-12-08T21:24:06+00:00 app[web.1]:
2012-12-08T21:24:06+00:00 app[web.1]: Example:
2012-12-08T21:24:06+00:00 app[web.1]: [--skip-gemfile] # Don't create a Gemfile
2012-12-08T21:24:06+00:00 app[web.1]: This generates a skeletal Rails installation in ~/Code/Ruby/weblog.
2012-12-08T21:24:06+00:00 app[web.1]:
2012-12-08T21:24:06+00:00 app[web.1]: See the README in the newly created application to get going.
2012-12-08T21:24:06+00:00 app[web.1]: rails new ~/Code/Ruby/weblog
2012-12-08T21:24:06+00:00 app[web.1]: Runtime options:
2012-12-08T21:24:06+00:00 app[web.1]: Rails options:
2012-12-08T21:24:07+00:00 heroku[web.1]: State changed from starting to crashed
2012-12-08T21:24:07+00:00 heroku[web.1]: Process exited with status 0
2012-12-08T21:24:54+00:00 heroku[web.1]: State changed from crashed to starting
Make sure the Procfile doesn't have any extension! For instance if you use Procfile.txt it's gonna return "Scaling web processes... failed ! No such type as web". Delete the extension of your Procfile and it'll work!
Looking at https://devcenter.heroku.com/articles/error-codes#h14-no-web-dynos-running, you should run: heroku ps:scale web=1, which fixed the error for me