Created
December 3, 2016 19:07
-
-
Save aqt01/21cfc95ba8057fe5bcf931a43754711a to your computer and use it in GitHub Desktop.
Heroku log error and Procfile configuration
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
>heroku logs | |
/home/shadowrain/.heroku/client/lib/heroku/jsplugin.rb:119: warning: Insecure world writable dir /opt/android-sdk in PATH, mode 040777 | |
2016-12-03T06:46:07.341875+00:00 app[web.1]: > babel-node tools/run start | |
2016-12-03T06:46:07.341876+00:00 app[web.1]: | |
2016-12-03T06:46:07.347512+00:00 app[web.1]: sh: 1: babel-node: not found | |
2016-12-03T06:46:07.360873+00:00 app[web.1]: npm ERR! Linux 3.13.0-100-generic | |
2016-12-03T06:46:07.351863+00:00 app[web.1]: | |
2016-12-03T06:46:07.361168+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "run" "start" | |
2016-12-03T06:46:07.361515+00:00 app[web.1]: npm ERR! node v5.9.1 | |
2016-12-03T06:46:07.361821+00:00 app[web.1]: npm ERR! npm v3.7.3 | |
2016-12-03T06:46:07.362029+00:00 app[web.1]: npm ERR! file sh | |
2016-12-03T06:46:07.362170+00:00 app[web.1]: npm ERR! code ELIFECYCLE | |
2016-12-03T06:46:07.362259+00:00 app[web.1]: npm ERR! errno ENOENT | |
2016-12-03T06:46:07.362438+00:00 app[web.1]: npm ERR! syscall spawn | |
2016-12-03T06:46:07.362556+00:00 app[web.1]: npm ERR! src@1.0.1 start: `babel-node tools/run start` | |
2016-12-03T06:46:07.362665+00:00 app[web.1]: npm ERR! spawn ENOENT | |
2016-12-03T06:46:07.362774+00:00 app[web.1]: npm ERR! | |
2016-12-03T06:46:07.362878+00:00 app[web.1]: npm ERR! Failed at the src@1.0.1 start script 'babel-node tools/run start'. | |
2016-12-03T06:46:07.362990+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm installed. | |
2016-12-03T06:46:07.363090+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the src package, | |
2016-12-03T06:46:07.363195+00:00 app[web.1]: npm ERR! not with npm itself. | |
2016-12-03T06:46:07.363309+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system: | |
2016-12-03T06:46:07.363408+00:00 app[web.1]: npm ERR! babel-node tools/run start | |
2016-12-03T06:46:07.363508+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with: | |
2016-12-03T06:46:07.363603+00:00 app[web.1]: npm ERR! npm bugs src | |
2016-12-03T06:46:07.363702+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via: | |
2016-12-03T06:46:07.363810+00:00 app[web.1]: npm ERR! npm owner ls src | |
2016-12-03T06:46:07.367491+00:00 app[web.1]: | |
2016-12-03T06:46:07.363907+00:00 app[web.1]: npm ERR! There is likely additional logging output above. | |
2016-12-03T06:46:07.367694+00:00 app[web.1]: npm ERR! Please include the following file with any support request: | |
2016-12-03T06:46:07.367796+00:00 app[web.1]: npm ERR! /app/npm-debug.log | |
2016-12-03T06:46:07.501447+00:00 heroku[web.1]: State changed from starting to crashed | |
2016-12-03T06:46:07.475779+00:00 heroku[web.1]: Process exited with status 1 | |
2016-12-03T12:22:21.846107+00:00 heroku[web.1]: State changed from crashed to starting | |
2016-12-03T12:22:24.981361+00:00 heroku[web.1]: Starting process with command `npm run start` | |
2016-12-03T12:22:28.435922+00:00 app[web.1]: | |
2016-12-03T12:22:28.435939+00:00 app[web.1]: > src@1.0.1 start /app | |
2016-12-03T12:22:28.435940+00:00 app[web.1]: > babel-node tools/run start | |
2016-12-03T12:22:28.435940+00:00 app[web.1]: | |
2016-12-03T12:22:28.442451+00:00 app[web.1]: sh: 1: babel-node: not found | |
2016-12-03T12:22:28.448652+00:00 app[web.1]: | |
2016-12-03T12:22:28.459420+00:00 app[web.1]: npm ERR! Linux 3.13.0-100-generic | |
2016-12-03T12:22:28.459917+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "run" "start" | |
2016-12-03T12:22:28.460474+00:00 app[web.1]: npm ERR! node v5.9.1 | |
2016-12-03T12:22:28.463006+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm installed. | |
2016-12-03T12:22:28.460893+00:00 app[web.1]: npm ERR! npm v3.7.3 | |
2016-12-03T12:22:28.461422+00:00 app[web.1]: npm ERR! code ELIFECYCLE | |
2016-12-03T12:22:28.461681+00:00 app[web.1]: npm ERR! errno ENOENT | |
2016-12-03T12:22:28.461945+00:00 app[web.1]: npm ERR! syscall spawn | |
2016-12-03T12:22:28.462159+00:00 app[web.1]: npm ERR! src@1.0.1 start: `babel-node tools/run start` | |
2016-12-03T12:22:28.461163+00:00 app[web.1]: npm ERR! file sh | |
2016-12-03T12:22:28.462360+00:00 app[web.1]: npm ERR! spawn ENOENT | |
2016-12-03T12:22:28.462575+00:00 app[web.1]: npm ERR! | |
2016-12-03T12:22:28.462785+00:00 app[web.1]: npm ERR! Failed at the src@1.0.1 start script 'babel-node tools/run start'. | |
2016-12-03T12:22:28.463212+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the src package, | |
2016-12-03T12:22:28.463616+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system: | |
2016-12-03T12:22:28.463809+00:00 app[web.1]: npm ERR! babel-node tools/run start | |
2016-12-03T12:22:28.463411+00:00 app[web.1]: npm ERR! not with npm itself. | |
2016-12-03T12:22:28.464013+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with: | |
2016-12-03T12:22:28.464210+00:00 app[web.1]: npm ERR! npm bugs src | |
2016-12-03T12:22:28.464427+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via: | |
2016-12-03T12:22:28.464638+00:00 app[web.1]: npm ERR! npm owner ls src | |
2016-12-03T12:22:28.464831+00:00 app[web.1]: npm ERR! There is likely additional logging output above. | |
2016-12-03T12:22:28.470167+00:00 app[web.1]: | |
2016-12-03T12:22:28.470448+00:00 app[web.1]: npm ERR! Please include the following file with any support request: | |
2016-12-03T12:22:28.470641+00:00 app[web.1]: npm ERR! /app/npm-debug.log | |
2016-12-03T12:22:28.569004+00:00 heroku[web.1]: State changed from starting to crashed | |
2016-12-03T12:22:28.555327+00:00 heroku[web.1]: Process exited with status 1 | |
2016-12-03T17:58:41.593135+00:00 heroku[web.1]: State changed from crashed to starting | |
2016-12-03T17:58:59.346771+00:00 heroku[web.1]: Starting process with command `npm run start` | |
2016-12-03T17:59:02.080365+00:00 heroku[web.1]: Process exited with status 1 | |
2016-12-03T17:59:01.990218+00:00 app[web.1]: | |
2016-12-03T17:59:01.990233+00:00 app[web.1]: > src@1.0.1 start /app | |
2016-12-03T17:59:01.990234+00:00 app[web.1]: > babel-node tools/run start | |
2016-12-03T17:59:01.990235+00:00 app[web.1]: | |
2016-12-03T17:59:01.995850+00:00 app[web.1]: sh: 1: babel-node: not found | |
2016-12-03T17:59:02.008609+00:00 app[web.1]: npm ERR! Linux 3.13.0-100-generic | |
2016-12-03T17:59:02.001121+00:00 app[web.1]: | |
2016-12-03T17:59:02.008959+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "run" "start" | |
2016-12-03T17:59:02.009343+00:00 app[web.1]: npm ERR! node v5.9.1 | |
2016-12-03T17:59:02.009704+00:00 app[web.1]: npm ERR! npm v3.7.3 | |
2016-12-03T17:59:02.009942+00:00 app[web.1]: npm ERR! file sh | |
2016-12-03T17:59:02.010207+00:00 app[web.1]: npm ERR! code ELIFECYCLE | |
2016-12-03T17:59:02.010426+00:00 app[web.1]: npm ERR! errno ENOENT | |
2016-12-03T17:59:02.010619+00:00 app[web.1]: npm ERR! syscall spawn | |
2016-12-03T17:59:02.010763+00:00 app[web.1]: npm ERR! src@1.0.1 start: `babel-node tools/run start` | |
2016-12-03T17:59:02.010889+00:00 app[web.1]: npm ERR! spawn ENOENT | |
2016-12-03T17:59:02.011186+00:00 app[web.1]: npm ERR! Failed at the src@1.0.1 start script 'babel-node tools/run start'. | |
2016-12-03T17:59:02.011513+00:00 app[web.1]: npm ERR! If you do, this is most likely a problem with the src package, | |
2016-12-03T17:59:02.011028+00:00 app[web.1]: npm ERR! | |
2016-12-03T17:59:02.011322+00:00 app[web.1]: npm ERR! Make sure you have the latest version of node.js and npm installed. | |
2016-12-03T17:59:02.011618+00:00 app[web.1]: npm ERR! not with npm itself. | |
2016-12-03T17:59:02.011734+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system: | |
2016-12-03T17:59:02.011848+00:00 app[web.1]: npm ERR! babel-node tools/run start | |
2016-12-03T17:59:02.011936+00:00 app[web.1]: npm ERR! You can get information on how to open an issue for this project with: | |
2016-12-03T17:59:02.012075+00:00 app[web.1]: npm ERR! npm bugs src | |
2016-12-03T17:59:02.012316+00:00 app[web.1]: npm ERR! npm owner ls src | |
2016-12-03T17:59:02.012432+00:00 app[web.1]: npm ERR! There is likely additional logging output above. | |
2016-12-03T17:59:02.012203+00:00 app[web.1]: npm ERR! Or if that isn't available, you can get their info via: | |
2016-12-03T17:59:02.016421+00:00 app[web.1]: | |
2016-12-03T17:59:02.016700+00:00 app[web.1]: npm ERR! /app/npm-debug.log | |
2016-12-03T17:59:02.016596+00:00 app[web.1]: npm ERR! Please include the following file with any support request: | |
2016-12-03T17:59:02.095293+00:00 heroku[web.1]: State changed from starting to crashed | |
[41:540] 15:06 [shadowrain@starscream] ~/apps/bookme-webapp/node-js-getting-started | |
> | |
[41:540] 15:07 [shadowrain@starscream] ~/apps/bookme-webapp/node-js-getting-started | |
> | |
[41:540] 15:07 [shadowrain@starscream] ~/apps/bookme-webapp/node-js-getting-started | |
>cat Procfile | |
web: npm run start |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment