Created
April 6, 2014 01:21
-
-
Save tlongren/10000240 to your computer and use it in GitHub Desktop.
Heroku Log from Let's Chat
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
| 2014-04-05T06:54:17.117537+00:00 app[web.1]: npm ERR! Additional logging details can be found in: | |
| 2014-04-05T06:54:17.117613+00:00 app[web.1]: npm ERR! /app/npm-debug.log | |
| 2014-04-05T06:54:18.178863+00:00 heroku[web.1]: Process exited with status 1 | |
| 2014-04-05T06:54:18.189317+00:00 heroku[web.1]: State changed from starting to crashed | |
| 2014-04-05T09:42:26.222103+00:00 heroku[web.1]: State changed from crashed to starting | |
| 2014-04-05T09:42:29.369075+00:00 heroku[web.1]: Starting process with command `npm start` | |
| 2014-04-05T09:42:32.399772+00:00 app[web.1]: | |
| 2014-04-05T09:42:32.399772+00:00 app[web.1]: > lcb@0.0.1 start /app | |
| 2014-04-05T09:42:32.399772+00:00 app[web.1]: > nodejs app.js | |
| 2014-04-05T09:42:32.399772+00:00 app[web.1]: | |
| 2014-04-05T09:42:32.426168+00:00 app[web.1]: sh: nodejs: not found | |
| 2014-04-05T09:42:32.435405+00:00 app[web.1]: | |
| 2014-04-05T09:42:32.453678+00:00 app[web.1]: npm ERR! lcb@0.0.1 start: `nodejs app.js` | |
| 2014-04-05T09:42:32.454454+00:00 app[web.1]: npm ERR! Exit status 127 | |
| 2014-04-05T09:42:32.456215+00:00 app[web.1]: npm ERR! This is most likely a problem with the lcb package, | |
| 2014-04-05T09:42:32.461367+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system: | |
| 2014-04-05T09:42:32.462167+00:00 app[web.1]: npm ERR! npm owner ls lcb | |
| 2014-04-05T09:42:32.462431+00:00 app[web.1]: npm ERR! There is likely additional logging output above. | |
| 2014-04-05T09:42:32.463362+00:00 app[web.1]: npm ERR! command "/app/vendor/node/bin/node" "/app/vendor/node/bin/npm" "start" | |
| 2014-04-05T09:42:32.464098+00:00 app[web.1]: npm ERR! node -v v0.10.26 | |
| 2014-04-05T09:42:32.461658+00:00 app[web.1]: npm ERR! nodejs app.js | |
| 2014-04-05T09:42:32.455388+00:00 app[web.1]: npm ERR! Failed at the lcb@0.0.1 start script. | |
| 2014-04-05T09:42:32.460809+00:00 app[web.1]: npm ERR! not with npm itself. | |
| 2014-04-05T09:42:32.455017+00:00 app[web.1]: npm ERR! | |
| 2014-04-05T09:42:32.462998+00:00 app[web.1]: npm ERR! System Linux 3.8.11-ec2 | |
| 2014-04-05T09:42:32.461895+00:00 app[web.1]: npm ERR! You can get their info via: | |
| 2014-04-05T09:42:32.464579+00:00 app[web.1]: npm ERR! npm -v 1.4.3 | |
| 2014-04-05T09:42:32.463768+00:00 app[web.1]: npm ERR! cwd /app | |
| 2014-04-05T09:42:32.472923+00:00 app[web.1]: npm ERR! /app/npm-debug.log | |
| 2014-04-05T09:42:32.465451+00:00 app[web.1]: npm ERR! code ELIFECYCLE | |
| 2014-04-05T09:42:32.471226+00:00 app[web.1]: npm ERR! | |
| 2014-04-05T09:42:32.472581+00:00 app[web.1]: npm ERR! Additional logging details can be found in: | |
| 2014-04-05T09:42:32.474851+00:00 app[web.1]: npm ERR! not ok code 0 | |
| 2014-04-05T09:42:33.936397+00:00 heroku[web.1]: State changed from starting to crashed | |
| 2014-04-05T09:42:33.922678+00:00 heroku[web.1]: Process exited with status 1 | |
| 2014-04-05T15:42:14.003844+00:00 heroku[web.1]: State changed from crashed to starting | |
| 2014-04-05T15:42:16.639258+00:00 heroku[web.1]: Starting process with command `npm start` | |
| 2014-04-05T15:42:18.447243+00:00 app[web.1]: > lcb@0.0.1 start /app | |
| 2014-04-05T15:42:18.447243+00:00 app[web.1]: | |
| 2014-04-05T15:42:18.447243+00:00 app[web.1]: > nodejs app.js | |
| 2014-04-05T15:42:18.447243+00:00 app[web.1]: | |
| 2014-04-05T15:42:18.474947+00:00 app[web.1]: sh: nodejs: not found | |
| 2014-04-05T15:42:18.477466+00:00 app[web.1]: | |
| 2014-04-05T15:42:18.484477+00:00 app[web.1]: npm ERR! lcb@0.0.1 start: `nodejs app.js` | |
| 2014-04-05T15:42:18.484759+00:00 app[web.1]: npm ERR! Exit status 127 | |
| 2014-04-05T15:42:18.484955+00:00 app[web.1]: npm ERR! | |
| 2014-04-05T15:42:18.485113+00:00 app[web.1]: npm ERR! Failed at the lcb@0.0.1 start script. | |
| 2014-04-05T15:42:18.485715+00:00 app[web.1]: npm ERR! This is most likely a problem with the lcb package, | |
| 2014-04-05T15:42:18.485867+00:00 app[web.1]: npm ERR! not with npm itself. | |
| 2014-04-05T15:42:18.486027+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system: | |
| 2014-04-05T15:42:18.486194+00:00 app[web.1]: npm ERR! nodejs app.js | |
| 2014-04-05T15:42:18.486379+00:00 app[web.1]: n | |
| pm ERR! You can get their info via: | |
| 2014-04-05T15:42:18.486514+00:00 app[web.1]: npm ERR! npm owner ls lcb | |
| 2014-04-05T15:42:18.486616+00:00 app[web.1]: npm ERR! There is likely additional logging output above. | |
| 2014-04-05T15:42:18.486934+00:00 app[web.1]: npm ERR! System Linux 3.8.11-ec2 | |
| 2014-04-05T15:42:18.487126+00:00 app[web.1]: npm ERR! command "/app/vendor/node/bin/node" "/app/vendor/node/bin/npm" "start" | |
| 2014-04-05T15:42:18.487258+00:00 app[web.1]: npm ERR! cwd /app | |
| 2014-04-05T15:42:18.487368+00:00 app[web.1]: npm ERR! node -v v0.10.26 | |
| 2014-04-05T15:42:18.487482+00:00 app[web.1]: npm ERR! npm -v 1.4.3 | |
| 2014-04-05T15:42:18.489322+00:00 app[web.1]: npm ERR! | |
| 2014-04-05T15:42:18.487575+00:00 app[web.1]: npm ERR! code ELIFECYCLE | |
| 2014-04-05T15:42:18.489579+00:00 app[web.1]: npm ERR! Additional logging details can be found in: | |
| 2014-04-05T15:42:18.489772+00:00 app[web.1]: npm ERR! /app/npm-debug.log | |
| 2014-04-05T15:42:18.490046+00:00 app[web.1]: npm ERR! not ok code 0 | |
| 2014-04-05T15:42:19.940373+00:00 heroku[web.1]: Process exited with status 1 | |
| 2014-04-05T15:42:19.980725+00:00 heroku[web.1]: State changed from starting to crashed | |
| 2014-04-05T19:08:39.165393+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=yell.longren.io request_id=1b426eed-bfda-48f2-a276-0831d7e8d7c6 fwd="192.0.149.42" dyno= connect= service= status=503 bytes= | |
| 2014-04-05T19:08:39.624024+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=yell.longren.io request_id=1e598ecd-8ed1-4a39-8f0d-914525a865d0 fwd="192.0.149.42" dyno= connect= service= status=503 bytes= | |
| 2014-04-05T21:49:04.306211+00:00 heroku[web.1]: State changed from crashed to starting | |
| 2014-04-05T21:49:07.755855+00:00 app[web.1]: | |
| 2014-04-05T21:49:07.755855+00:00 app[web.1]: > lcb@0.0.1 start /app | |
| 2014-04-05T21:49:07.755855+00:00 app[web.1]: > nodejs app.js | |
| 2014-04-05T21:49:07.755855+00:00 app[web.1]: | |
| 2014-04-05T21:49:07.768173+00:00 app[web.1]: sh: nodejs: not found | |
| 2014-04-05T21:49:07.769963+00:00 app[web.1]: | |
| 2014-04-05T21:49:07.775258+00:00 app[web.1]: npm ERR! lcb@0.0.1 start: `nodejs app.js` | |
| 2014-04-05T21:49:07.778161+00:00 app[web.1]: npm ERR! Exit status 127 | |
| 2014-04-05T21:49:07.778161+00:00 app[web.1]: npm ERR! | |
| 2014-04-05T21:49:07.778161+00:00 app[web.1]: npm ERR! Failed at the lcb@0.0.1 start script. | |
| 2014-04-05T21:49:07.778161+00:00 app[web.1]: npm ERR! This is most likely a problem with the lcb package, | |
| 2014-04-05T21:49:07.778161+00:00 app[web.1]: npm ERR! not with npm itself. | |
| 2014-04-05T21:49:07.778161+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system: | |
| 2014-04-05T21:49:07.778161+00:00 app[web.1]: npm ERR! nodejs app.js | |
| 2014-04-05T21:49:07.778161+00:00 app[web.1]: npm ERR! You can get their info via: | |
| 2014-04-05T21:49:07.778161+00:00 app[web.1]: npm ERR! npm owner ls lcb | |
| 2014-04-05T21:49:07.778161+00:00 app[web.1]: npm ERR! There is likely additional logging output above. | |
| 2014-04-05T21:49:07.778366+00:00 app[web.1]: npm ERR! System Linux 3.8.11-ec2 | |
| 2014-04-05T21:49:07.778366+00:00 app[web.1]: npm ERR! command "/app/vendor/node/bin/node" "/app/vendor/node/bin/npm" "start" | |
| 2014-04-05T21:49:07.778366+00:00 app[web.1]: npm ERR! cwd /app | |
| 2014-04-05T21:49:07.778366+00:00 app[web.1]: npm ERR! node -v v0.10.26 | |
| 2014-04-05T21:49:07.778366+00:00 app[web.1]: npm ERR! npm -v 1.4.3 | |
| 2014-04-05T21:49:07.778366+00:00 app[web.1]: npm ERR! code ELIFECYCLE | |
| 2014-04-05T21:49:07.779047+00:00 app[web.1]: npm ERR! Additional logging details can be found in: | |
| 2014-04-05T21:49:07.779181+00:00 app[web.1]: npm ERR! /app/npm-debug.log | |
| 2014-04-05T21:49:07.779393+00:00 app[web.1]: npm ERR! not ok code 0 | |
| 2014-04-05T21:49:09.109323+00:00 heroku[web.1]: State changed from starting to crashed | |
| 2014-04-05T21:49:09.095662+00:00 heroku[web.1]: Process exited with status 1 | |
| 2014-04-05T21:49:06.679818+00:00 heroku[web.1]: Starting process with command `npm start` | |
| 2014-04-05T21:49:07.778946+00:00 app[web.1]: npm ERR! | |
| 2014-04-06T00:58:59.933173+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=yell.longren.io request_id=4d1105cf-f296-474d-aa58-0365c338b3bf fwd="192.0.149.42" dyno= connect= service= status=503 bytes= | |
| 2014-04-06T00:58:59.438977+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=yell.longren.io request_id=8f7d21a6-63bd-4802-a44d-6d5b374e323b fwd="192.0.149.42" dyno= connect= service= status=503 bytes= |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment