Advertisement
Guest User

Untitled

a guest
May 2nd, 2017
87
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. » 2 May 2017 23:14:22.031 134 <45>1 2017-05-02T21:14:21.792463+00:00 heroku web.1 - - State changed from crashed to starting
  2. » 2 May 2017 23:14:25.652 141 <45>1 2017-05-02T21:14:24.876009+00:00 heroku web.1 - - Starting process with command `npm run start`
  3. » 2 May 2017 23:14:29.792 94 <190>1 2017-05-02T21:14:29.363041+00:00 app web.1 - -
  4. » 2 May 2017 23:14:29.792 117 <190>1 2017-05-02T21:14:29.363054+00:00 app web.1 - - > OPS4@0.0.1 start /app
  5. » 2 May 2017 23:14:29.792 147 <190>1 2017-05-02T21:14:29.363055+00:00 app web.1 - - > cross-env NODE_ENV=development gulp DEV:startServer
  6. » 2 May 2017 23:14:29.792 94 <190>1 2017-05-02T21:14:29.363056+00:00 app web.1 - -
  7. » 2 May 2017 23:14:29.792 121 <190>1 2017-05-02T21:14:29.377096+00:00 app web.1 - - sh: 1: cross-env: not found
  8. » 2 May 2017 23:14:29.792 94 <190>1 2017-05-02T21:14:29.388498+00:00 app web.1 - -
  9. » 2 May 2017 23:14:29.792 127 <190>1 2017-05-02T21:14:29.416405+00:00 app web.1 - - npm ERR! Linux 3.13.0-112-generic
  10. » 2 May 2017 23:14:29.792 178 <190>1 2017-05-02T21:14:29.416786+00:00 app web.1 - - npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "run" "start"
  11. » 2 May 2017 23:14:29.792 115 <190>1 2017-05-02T21:14:29.417078+00:00 app web.1 - - npm ERR! node v6.10.3
  12. » 2 May 2017 23:14:29.792 116 <190>1 2017-05-02T21:14:29.417279+00:00 app web.1 - - npm ERR! npm v3.10.10
  13. » 2 May 2017 23:14:29.792 110 <190>1 2017-05-02T21:14:29.417524+00:00 app web.1 - - npm ERR! file sh
  14. » 2 May 2017 23:14:29.792 118 <190>1 2017-05-02T21:14:29.417746+00:00 app web.1 - - npm ERR! code ELIFECYCLE
  15. » 2 May 2017 23:14:29.792 115 <190>1 2017-05-02T21:14:29.417991+00:00 app web.1 - - npm ERR! errno ENOENT
  16. » 2 May 2017 23:14:29.792 116 <190>1 2017-05-02T21:14:29.418232+00:00 app web.1 - - npm ERR! syscall spawn
  17. » 2 May 2017 23:14:29.792 174 <190>1 2017-05-02T21:14:29.418441+00:00 app web.1 - - npm ERR! OPS4@0.0.1 start: `cross-env NODE_ENV=development gulp DEV:startServer`
  18. » 2 May 2017 23:14:29.792 115 <190>1 2017-05-02T21:14:29.418619+00:00 app web.1 - - npm ERR! spawn ENOENT
  19. » 2 May 2017 23:14:29.792 103 <190>1 2017-05-02T21:14:29.422869+00:00 app web.1 - - npm ERR!
  20. » 2 May 2017 23:14:29.792 195 <190>1 2017-05-02T21:14:29.423306+00:00 app web.1 - - npm ERR! Failed at the OPS4@0.0.1 start script 'cross-env NODE_ENV=development gulp DEV:startServer'.
  21. » 2 May 2017 23:14:29.792 170 <190>1 2017-05-02T21:14:29.423482+00:00 app web.1 - - npm ERR! Make sure you have the latest version of node.js and npm installed.
  22. » 2 May 2017 23:14:29.792 166 <190>1 2017-05-02T21:14:29.423659+00:00 app web.1 - - npm ERR! If you do, this is most likely a problem with the OPS4 package,
  23. » 2 May 2017 23:14:29.792 123 <190>1 2017-05-02T21:14:29.423834+00:00 app web.1 - - npm ERR! not with npm itself.
  24. » 2 May 2017 23:14:29.792 150 <190>1 2017-05-02T21:14:29.424010+00:00 app web.1 - - npm ERR! Tell the author that this fails on your system:
  25. » 2 May 2017 23:14:29.833 134 <45>1 2017-05-02T21:14:29.580035+00:00 heroku web.1 - - State changed from starting to crashed
  26. » 2 May 2017 23:14:29.874 158 <190>1 2017-05-02T21:14:29.424186+00:00 app web.1 - - npm ERR! cross-env NODE_ENV=development gulp DEV:startServer
  27. » 2 May 2017 23:14:29.874 173 <190>1 2017-05-02T21:14:29.424368+00:00 app web.1 - - npm ERR! You can get information on how to open an issue for this project with:
  28. » 2 May 2017 23:14:29.874 120 <190>1 2017-05-02T21:14:29.424545+00:00 app web.1 - - npm ERR! npm bugs OPS4
  29. » 2 May 2017 23:14:29.874 158 <190>1 2017-05-02T21:14:29.424721+00:00 app web.1 - - npm ERR! Or if that isn't available, you can get their info via:
  30. » 2 May 2017 23:14:29.874 124 <190>1 2017-05-02T21:14:29.424896+00:00 app web.1 - - npm ERR! npm owner ls OPS4
  31. » 2 May 2017 23:14:29.874 151 <190>1 2017-05-02T21:14:29.425082+00:00 app web.1 - - npm ERR! There is likely additional logging output above.
  32. » 2 May 2017 23:14:29.874 94 <190>1 2017-05-02T21:14:29.434092+00:00 app web.1 - -
  33. » 2 May 2017 23:14:29.874 162 <190>1 2017-05-02T21:14:29.436940+00:00 app web.1 - - npm ERR! Please include the following file with any support request:
  34. » 2 May 2017 23:14:29.874 125 <190>1 2017-05-02T21:14:29.437103+00:00 app web.1 - - npm ERR! /app/npm-debug.log
  35. » 2 May 2017 23:14:29.918 134 <45>1 2017-05-02T21:14:29.581259+00:00 heroku web.1 - - State changed from crashed to starting
  36. » 2 May 2017 23:14:29.945 124 <45>1 2017-05-02T21:14:29.568148+00:00 heroku web.1 - - Process exited with status 1
  37. » 2 May 2017 23:14:32.453 141 <45>1 2017-05-02T21:14:32.075653+00:00 heroku web.1 - - Starting process with command `npm run start`
  38. » 2 May 2017 23:14:34.902 94 <190>1 2017-05-02T21:14:34.615796+00:00 app web.1 - -
  39. » 2 May 2017 23:14:34.904 117 <190>1 2017-05-02T21:14:34.615816+00:00 app web.1 - - > OPS4@0.0.1 start /app
  40. » 2 May 2017 23:14:34.904 147 <190>1 2017-05-02T21:14:34.615817+00:00 app web.1 - - > cross-env NODE_ENV=development gulp DEV:startServer
  41. » 2 May 2017 23:14:34.904 94 <190>1 2017-05-02T21:14:34.615818+00:00 app web.1 - -
  42. » 2 May 2017 23:14:34.904 121 <190>1 2017-05-02T21:14:34.627067+00:00 app web.1 - - sh: 1: cross-env: not found
  43. » 2 May 2017 23:14:34.904 94 <190>1 2017-05-02T21:14:34.633808+00:00 app web.1 - -
  44. » 2 May 2017 23:14:34.904 127 <190>1 2017-05-02T21:14:34.644778+00:00 app web.1 - - npm ERR! Linux 3.13.0-112-generic
  45. » 2 May 2017 23:14:34.904 178 <190>1 2017-05-02T21:14:34.645079+00:00 app web.1 - - npm ERR! argv "/app/.heroku/node/bin/node" "/app/.heroku/node/bin/npm" "run" "start"
  46. » 2 May 2017 23:14:34.904 115 <190>1 2017-05-02T21:14:34.645291+00:00 app web.1 - - npm ERR! node v6.10.3
  47. » 2 May 2017 23:14:34.904 116 <190>1 2017-05-02T21:14:34.645480+00:00 app web.1 - - npm ERR! npm v3.10.10
  48. » 2 May 2017 23:14:34.904 110 <190>1 2017-05-02T21:14:34.645670+00:00 app web.1 - - npm ERR! file sh
  49. » 2 May 2017 23:14:34.904 118 <190>1 2017-05-02T21:14:34.645864+00:00 app web.1 - - npm ERR! code ELIFECYCLE
  50. » 2 May 2017 23:14:34.906 115 <190>1 2017-05-02T21:14:34.646044+00:00 app web.1 - - npm ERR! errno ENOENT
  51. » 2 May 2017 23:14:34.906 116 <190>1 2017-05-02T21:14:34.646225+00:00 app web.1 - - npm ERR! syscall spawn
  52. » 2 May 2017 23:14:34.906 174 <190>1 2017-05-02T21:14:34.646373+00:00 app web.1 - - npm ERR! OPS4@0.0.1 start: `cross-env NODE_ENV=development gulp DEV:startServer`
  53. » 2 May 2017 23:14:34.906 115 <190>1 2017-05-02T21:14:34.646503+00:00 app web.1 - - npm ERR! spawn ENOENT
  54. » 2 May 2017 23:14:34.906 103 <190>1 2017-05-02T21:14:34.646680+00:00 app web.1 - - npm ERR!
  55. » 2 May 2017 23:14:34.906 195 <190>1 2017-05-02T21:14:34.646825+00:00 app web.1 - - npm ERR! Failed at the OPS4@0.0.1 start script 'cross-env NODE_ENV=development gulp DEV:startServer'.
  56. » 2 May 2017 23:14:34.906 170 <190>1 2017-05-02T21:14:34.647130+00:00 app web.1 - - npm ERR! Make sure you have the latest version of node.js and npm installed.
  57. » 2 May 2017 23:14:34.906 166 <190>1 2017-05-02T21:14:34.647266+00:00 app web.1 - - npm ERR! If you do, this is most likely a problem with the OPS4 package,
  58. » 2 May 2017 23:14:34.906 123 <190>1 2017-05-02T21:14:34.647393+00:00 app web.1 - - npm ERR! not with npm itself.
  59. » 2 May 2017 23:14:34.906 150 <190>1 2017-05-02T21:14:34.647524+00:00 app web.1 - - npm ERR! Tell the author that this fails on your system:
  60. » 2 May 2017 23:14:34.983 158 <190>1 2017-05-02T21:14:34.647654+00:00 app web.1 - - npm ERR! cross-env NODE_ENV=development gulp DEV:startServer
  61. » 2 May 2017 23:14:34.983 173 <190>1 2017-05-02T21:14:34.647782+00:00 app web.1 - - npm ERR! You can get information on how to open an issue for this project with:
  62. » 2 May 2017 23:14:34.983 120 <190>1 2017-05-02T21:14:34.647911+00:00 app web.1 - - npm ERR! npm bugs OPS4
  63. » 2 May 2017 23:14:34.983 158 <190>1 2017-05-02T21:14:34.648039+00:00 app web.1 - - npm ERR! Or if that isn't available, you can get their info via:
  64. » 2 May 2017 23:14:34.983 124 <190>1 2017-05-02T21:14:34.648171+00:00 app web.1 - - npm ERR! npm owner ls OPS4
  65. » 2 May 2017 23:14:34.983 151 <190>1 2017-05-02T21:14:34.648306+00:00 app web.1 - - npm ERR! There is likely additional logging output above.
  66. » 2 May 2017 23:14:34.983 94 <190>1 2017-05-02T21:14:34.652665+00:00 app web.1 - -
  67. » 2 May 2017 23:14:34.983 162 <190>1 2017-05-02T21:14:34.652874+00:00 app web.1 - - npm ERR! Please include the following file with any support request:
  68. » 2 May 2017 23:14:34.983 125 <190>1 2017-05-02T21:14:34.653015+00:00 app web.1 - - npm ERR! /app/npm-debug.log
  69. » 2 May 2017 23:14:35.058 134 <45>1 2017-05-02T21:14:34.797083+00:00 heroku web.1 - - State changed from starting to crashed
  70. » 2 May 2017 23:14:35.141 124 <45>1 2017-05-02T21:14:34.782461+00:00 heroku web.1 - - Process exited with status 1
  71. » 2 May 2017 23:14:35.890 316 <158>1 2017-05-02T21:14:35.538423+00:00 heroku router - - at=error code=H10 desc="App crashed" method=GET path="/" host=ops4-front-staging.herokuapp.com request_id=daa99efd-720b-47af-a861-b00fb7bf05ec fwd="24.135.242.8" dyno= connect= service= status=503 bytes= protocol=https Fatal
  72. » 2 May 2017 23:14:36.586 327 <158>1 2017-05-02T21:14:36.354336+00:00 heroku router - - at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=ops4-front-staging.herokuapp.com request_id=32f6da14-4793-45be-9172-445dd5c58627 fwd="24.135.242.8" dyno= connect= service= status=503 bytes= protocol=https Fatal
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement