API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Oct 19th, 2015
137
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.05 KB | None | 0 0
raw download clone embed print report
  1. $ heroku logs -t
  2. 2015-10-19T23:33:13.140163+00:00 app[web.1]: npm ERR! file sh
  3. 2015-10-19T23:33:13.140398+00:00 app[web.1]: npm ERR! code ELIFECYCLE
  4. 2015-10-19T23:33:13.140615+00:00 app[web.1]: npm ERR! errno ENOENT
  5. 2015-10-19T23:33:13.140822+00:00 app[web.1]: npm ERR! syscall spawn
  6. 2015-10-19T23:33:13.141014+00:00 app[web.1]: npm ERR! cafe@1.0.0 build: `browserify client/browser.js | uglifyjs -cm > server/static/bundle.js`
  7. 2015-10-19T23:33:13.144599+00:00 app[web.1]: npm ERR!
  8. 2015-10-19T23:33:13.144294+00:00 app[web.1]: npm ERR! spawn ENOENT
  9. 2015-10-19T23:33:13.144879+00:00 app[web.1]: npm ERR! Failed at the cafe@1.0.0 build script 'browserify client/browser.js | uglifyjs -cm > server/static/bundle.js'.
  10. 2015-10-19T23:33:13.145202+00:00 app[web.1]: npm ERR! This is most likely a problem with the cafe package,
  11. 2015-10-19T23:33:13.145462+00:00 app[web.1]: npm ERR! not with npm itself.
  12. 2015-10-19T23:33:13.145730+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
  13. 2015-10-19T23:33:13.145970+00:00 app[web.1]: npm ERR! browserify client/browser.js | uglifyjs -cm > server/static/bundle.js
  14. 2015-10-19T23:33:13.146233+00:00 app[web.1]: npm ERR! You can get their info via:
  15. 2015-10-19T23:33:13.146496+00:00 app[web.1]: npm ERR! npm owner ls cafe
  16. 2015-10-19T23:33:13.151425+00:00 app[web.1]:
  17. 2015-10-19T23:33:13.146773+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
  18. 2015-10-19T23:33:13.183065+00:00 app[web.1]: npm ERR! Linux 3.13.0-63-generic
  19. 2015-10-19T23:33:13.183879+00:00 app[web.1]: npm ERR! node v4.2.1
  20. 2015-10-19T23:33:13.183573+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
  21. 2015-10-19T23:33:13.185814+00:00 app[web.1]: npm ERR!
  22. 2015-10-19T23:33:13.184830+00:00 app[web.1]: npm ERR! npm v2.14.7
  23. 2015-10-19T23:33:13.185155+00:00 app[web.1]: npm ERR! code ELIFECYCLE
  24. 2015-10-19T23:33:13.185362+00:00 app[web.1]: npm ERR! cafe@1.0.0 start: `npm run build && node server/server.js`
  25. 2015-10-19T23:33:13.185570+00:00 app[web.1]: npm ERR! Exit status 1
  26. 2015-10-19T23:33:13.186007+00:00 app[web.1]: npm ERR! Failed at the cafe@1.0.0 start script 'npm run build && node server/server.js'.
  27. 2015-10-19T23:33:13.186466+00:00 app[web.1]: npm ERR! not with npm itself.
  28. 2015-10-19T23:33:13.186219+00:00 app[web.1]: npm ERR! This is most likely a problem with the cafe package,
  29. 2015-10-19T23:33:13.186667+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
  30. 2015-10-19T23:33:13.186896+00:00 app[web.1]: npm ERR! npm run build && node server/server.js
  31. 2015-10-19T23:33:13.187088+00:00 app[web.1]: npm ERR! You can get their info via:
  32. 2015-10-19T23:33:13.187300+00:00 app[web.1]: npm ERR! npm owner ls cafe
  33. 2015-10-19T23:33:13.187504+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
  34. 2015-10-19T23:33:13.191576+00:00 app[web.1]:
  35. 2015-10-19T23:33:13.191926+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
  36. 2015-10-19T23:33:13.192127+00:00 app[web.1]: npm ERR! /app/npm-debug.log
  37. 2015-10-19T23:33:14.168122+00:00 heroku[web.1]: Process exited with status 1
  38. 2015-10-19T23:33:14.353875+00:00 heroku[web.1]: State changed from starting to crashed
  39. 2015-10-19T23:33:15.861332+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fathomless-gorge-5826.herokuapp.com request_id=a650b474-9974-4c47-85f4-870571710707 fwd="104.180.156.100" dyno= connect= service= status=503 bytes=
  40. 2015-10-19T23:33:16.183891+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=fathomless-gorge-5826.herokuapp.com request_id=8918f9e9-ebd1-40b5-8d1d-d3e40d10b7da fwd="104.180.156.100" dyno= connect= service= status=503 bytes=
  41. 2015-10-19T23:39:33.797788+00:00 heroku[api]: Deploy 26a2aaa by leptone55@gmail.com
  42. 2015-10-19T23:39:33.797845+00:00 heroku[api]: Release v7 created by leptone55@gmail.com
  43. 2015-10-19T23:39:33.856556+00:00 heroku[slug-compiler]: Slug compilation started
  44. 2015-10-19T23:39:33.856565+00:00 heroku[slug-compiler]: Slug compilation finished
  45. 2015-10-19T23:39:34.832696+00:00 heroku[web.1]: State changed from crashed to starting
  46. 2015-10-19T23:39:36.553594+00:00 heroku[web.1]: Starting process with command `npm start`
  47. 2015-10-19T23:39:39.020050+00:00 app[web.1]:
  48. 2015-10-19T23:39:39.020070+00:00 app[web.1]: > cafe@1.0.0 start /app
  49. 2015-10-19T23:39:39.020072+00:00 app[web.1]: > npm run build && node server/server.js
  50. 2015-10-19T23:39:39.020073+00:00 app[web.1]:
  51. 2015-10-19T23:39:39.931479+00:00 app[web.1]:
  52. 2015-10-19T23:39:39.931483+00:00 app[web.1]: > cafe@1.0.0 build /app
  53. 2015-10-19T23:39:39.931485+00:00 app[web.1]: > browserify client/browser.js | uglifyjs -cm > server/static/bundle.js
  54. 2015-10-19T23:39:39.941847+00:00 app[web.1]: sh: 1: uglifyjs: not found
  55. 2015-10-19T23:39:39.931485+00:00 app[web.1]:
  56. 2015-10-19T23:39:41.155506+00:00 app[web.1]:
  57. 2015-10-19T23:39:41.163400+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "run" "build"
  58. 2015-10-19T23:39:41.176000+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
  59. 2015-10-19T23:39:41.176174+00:00 app[web.1]: npm ERR! /app/npm-debug.log
  60. 2015-10-19T23:39:41.190656+00:00 app[web.1]:
  61. 2015-10-19T23:39:41.200078+00:00 app[web.1]: npm ERR! Failed at the cafe@1.0.0 start script 'npm run build && node server/server.js'.
  62. 2015-10-19T23:39:41.162961+00:00 app[web.1]: npm ERR! Linux 3.13.0-63-generic
  63. 2015-10-19T23:39:41.164442+00:00 app[web.1]: npm ERR! node v4.2.1
  64. 2015-10-19T23:39:41.164879+00:00 app[web.1]: npm ERR! file sh
  65. 2015-10-19T23:39:41.164660+00:00 app[web.1]: npm ERR! npm v2.14.7
  66. 2015-10-19T23:39:41.165075+00:00 app[web.1]: npm ERR! code ELIFECYCLE
  67. 2015-10-19T23:39:41.165494+00:00 app[web.1]: npm ERR! syscall spawn
  68. 2015-10-19T23:39:41.165679+00:00 app[web.1]: npm ERR! cafe@1.0.0 build: `browserify client/browser.js | uglifyjs -cm > server/static/bundle.js`
  69. 2015-10-19T23:39:41.165296+00:00 app[web.1]: npm ERR! errno ENOENT
  70. 2015-10-19T23:39:41.166028+00:00 app[web.1]: npm ERR!
  71. 2015-10-19T23:39:41.165838+00:00 app[web.1]: npm ERR! spawn ENOENT
  72. 2015-10-19T23:39:41.166217+00:00 app[web.1]: npm ERR! Failed at the cafe@1.0.0 build script 'browserify client/browser.js | uglifyjs -cm > server/static/bundle.js'.
  73. 2015-10-19T23:39:41.166470+00:00 app[web.1]: npm ERR! This is most likely a problem with the cafe package,
  74. 2015-10-19T23:39:41.166646+00:00 app[web.1]: npm ERR! not with npm itself.
  75. 2015-10-19T23:39:41.166832+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
  76. 2015-10-19T23:39:41.167032+00:00 app[web.1]: npm ERR! browserify client/browser.js | uglifyjs -cm > server/static/bundle.js
  77. 2015-10-19T23:39:41.167418+00:00 app[web.1]: npm ERR! npm owner ls cafe
  78. 2015-10-19T23:39:41.167215+00:00 app[web.1]: npm ERR! You can get their info via:
  79. 2015-10-19T23:39:41.167607+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
  80. 2015-10-19T23:39:41.196267+00:00 app[web.1]: npm ERR! Linux 3.13.0-63-generic
  81. 2015-10-19T23:39:41.175283+00:00 app[web.1]:
  82. 2015-10-19T23:39:41.196719+00:00 app[web.1]: npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "start"
  83. 2015-10-19T23:39:41.198045+00:00 app[web.1]: npm ERR! code ELIFECYCLE
  84. 2015-10-19T23:39:41.196990+00:00 app[web.1]: npm ERR! node v4.2.1
  85. 2015-10-19T23:39:41.198454+00:00 app[web.1]: npm ERR! Exit status 1
  86. 2015-10-19T23:39:41.197792+00:00 app[web.1]: npm ERR! npm v2.14.7
  87. {
  88. 2015-10-19T23:39:41.198248+00:00 app[web.1]: npm ERR! cafe@1.0.0 start: `npm run build && node server/server.js`
  89. 2015-10-19T23:39:41.199650+00:00 app[web.1]: npm ERR!
  90. 2015-10-19T23:39:41.201557+00:00 app[web.1]: npm ERR! This is most likely a problem with the cafe package,
  91. 2015-10-19T23:39:41.201733+00:00 app[web.1]: npm ERR! not with npm itself.
  92. 2015-10-19T23:39:41.201877+00:00 app[web.1]: npm ERR! Tell the author that this fails on your system:
  93. 2015-10-19T23:39:41.202046+00:00 app[web.1]: npm ERR! npm run build && node server/server.js
  94. 2015-10-19T23:39:41.202202+00:00 app[web.1]: npm ERR! You can get their info via:
  95. 2015-10-19T23:39:41.202363+00:00 app[web.1]: npm ERR! npm owner ls cafe
  96. 2015-10-19T23:39:41.243489+00:00 app[web.1]:
  97. 2015-10-19T23:39:41.202519+00:00 app[web.1]: npm ERR! There is likely additional logging output above.
  98. 2015-10-19T23:39:41.243832+00:00 app[web.1]: npm ERR! Please include the following file with any support request:
  99. 2015-10-19T23:39:41.244039+00:00 app[web.1]: npm ERR! /app/npm-debug.log
  100. 2015-10-19T23:39:42.079214+00:00 heroku[web.1]: State changed from starting to crashed
  101. 2015-10-19T23:39:42.063129+00:00 heroku[web.1]: Process exited with status 1
  102. 2015-10-19T23:39:43.153974+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fathomless-gorge-5826.herokuapp.com request_id=e43eff98-206f-449b-9b21-380c4fdf0a92 fwd="104.180.156.100" dyno= connect= service= status=503 bytes=
  103. 2015-10-19T23:39:43.409178+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=fathomless-gorge-5826.herokuapp.com request_id=2f967383-eec7-41be-91d9-c4b0b1c70bd5 fwd="104.180.156.100" dyno= connect= service= status=503 bytes=
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!