Advertisement
Guest User

heroku logs error

a guest
Dec 16th, 2019
138
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 7.52 KB | None | 0 0
  1. 2019-12-16T07:23:01.011625+00:00 app[api]: Initial release by user will.houghton2000@gmail.com
  2. 2019-12-16T07:23:01.011625+00:00 app[api]: Release v1 created by user will.houghton2000@gmail.com
  3. 2019-12-16T07:23:01.372585+00:00 app[api]: Release v2 created by user will.houghton2000@gmail.com
  4. 2019-12-16T07:23:01.372585+00:00 app[api]: Enable Logplex by user will.houghton2000@gmail.com
  5. 2019-12-16T07:25:04.000000+00:00 app[api]: Build started by user will.houghton2000@gmail.com
  6. 2019-12-16T07:26:05.818507+00:00 app[api]: Release v3 created by user will.houghton2000@gmail.com
  7. 2019-12-16T07:26:05.818507+00:00 app[api]: Deploy 6cc1a8d3 by user will.houghton2000@gmail.com
  8. 2019-12-16T07:26:05.893861+00:00 app[api]: Scaled to web@1:Free by user will.houghton2000@gmail.com
  9. 2019-12-16T07:26:08.000000+00:00 app[api]: Build succeeded
  10. 2019-12-16T07:26:08.790253+00:00 heroku[web.1]: Starting process with command `npm start`
  11. 2019-12-16T07:26:11.601032+00:00 heroku[web.1]: State changed from starting to crashed
  12. 2019-12-16T07:26:11.605617+00:00 heroku[web.1]: State changed from crashed to starting
  13. 2019-12-16T07:26:11.489138+00:00 app[web.1]:
  14. 2019-12-16T07:26:11.489162+00:00 app[web.1]: > restful-react-from-scratch@1.0.0 start /app
  15. 2019-12-16T07:26:11.489165+00:00 app[web.1]: > run-s build server
  16. 2019-12-16T07:26:11.489167+00:00 app[web.1]:
  17. 2019-12-16T07:26:11.497276+00:00 app[web.1]: sh: 1: run-s: not found
  18. 2019-12-16T07:26:11.503795+00:00 app[web.1]: npm ERR! code ELIFECYCLE
  19. 2019-12-16T07:26:11.504283+00:00 app[web.1]: npm ERR! syscall spawn
  20. 2019-12-16T07:26:11.504656+00:00 app[web.1]: npm ERR! file sh
  21. 2019-12-16T07:26:11.505062+00:00 app[web.1]: npm ERR! errno ENOENT
  22. 2019-12-16T07:26:11.506656+00:00 app[web.1]: npm ERR! restful-react-from-scratch@1.0.0 start: `run-s build server`
  23. 2019-12-16T07:26:11.506923+00:00 app[web.1]: npm ERR! spawn ENOENT
  24. 2019-12-16T07:26:11.507187+00:00 app[web.1]: npm ERR!
  25. 2019-12-16T07:26:11.507483+00:00 app[web.1]: npm ERR! Failed at the restful-react-from-scratch@1.0.0 start script.
  26. 2019-12-16T07:26:11.507732+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
  27. 2019-12-16T07:26:11.518532+00:00 app[web.1]:
  28. 2019-12-16T07:26:11.518797+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
  29. 2019-12-16T07:26:11.519023+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2019-12-16T07_26_11_508Z-debug.log
  30. 2019-12-16T07:26:11.578465+00:00 heroku[web.1]: Process exited with status 1
  31. 2019-12-16T07:26:14.200805+00:00 heroku[web.1]: Starting process with command `npm start`
  32. 2019-12-16T07:26:17.194332+00:00 heroku[web.1]: State changed from starting to crashed
  33. 2019-12-16T07:26:17.172324+00:00 heroku[web.1]: Process exited with status 1
  34. 2019-12-16T07:26:17.075921+00:00 app[web.1]:
  35. 2019-12-16T07:26:17.075945+00:00 app[web.1]: > restful-react-from-scratch@1.0.0 start /app
  36. 2019-12-16T07:26:17.075948+00:00 app[web.1]: > run-s build server
  37. 2019-12-16T07:26:17.075950+00:00 app[web.1]:
  38. 2019-12-16T07:26:17.096686+00:00 app[web.1]: sh: 1: run-s: not found
  39. 2019-12-16T07:26:17.100674+00:00 app[web.1]: npm ERR! code ELIFECYCLE
  40. 2019-12-16T07:26:17.101196+00:00 app[web.1]: npm ERR! syscall spawn
  41. 2019-12-16T07:26:17.102013+00:00 app[web.1]: npm ERR! file sh
  42. 2019-12-16T07:26:17.102522+00:00 app[web.1]: npm ERR! errno ENOENT
  43. 2019-12-16T07:26:17.104397+00:00 app[web.1]: npm ERR! restful-react-from-scratch@1.0.0 start: `run-s build server`
  44. 2019-12-16T07:26:17.104754+00:00 app[web.1]: npm ERR! spawn ENOENT
  45. 2019-12-16T07:26:17.105123+00:00 app[web.1]: npm ERR!
  46. 2019-12-16T07:26:17.105459+00:00 app[web.1]: npm ERR! Failed at the restful-react-from-scratch@1.0.0 start script.
  47. 2019-12-16T07:26:17.105874+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
  48. 2019-12-16T07:26:17.117107+00:00 app[web.1]:
  49. 2019-12-16T07:26:17.117477+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
  50. 2019-12-16T07:26:17.117484+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2019-12-16T07_26_17_107Z-debug.log
  51. 2019-12-16T07:26:18.179239+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fullstack-boilerplate.herokuapp.com request_id=f2d8c1d4-b70a-4737-9064-9f2366f72433 fwd="103.62.49.221" dyno= connect= service= status=503 bytes= protocol=https
  52. 2019-12-16T07:26:19.066616+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=fullstack-boilerplate.herokuapp.com request_id=ac6b4572-cc3a-4364-a29d-131530e2e8eb fwd="103.62.49.221" dyno= connect= service= status=503 bytes= protocol=https
  53. 2019-12-16T07:28:54.242214+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fullstack-boilerplate.herokuapp.com request_id=a2990737-789e-4b70-b8fd-b32cb533a89b fwd="103.62.49.221" dyno= connect= service= status=503 bytes= protocol=https
  54. 2019-12-16T07:30:11.941051+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fullstack-boilerplate.herokuapp.com request_id=69b74107-4c27-440b-9be1-0f22e6410cb7 fwd="103.62.49.221" dyno= connect= service= status=503 bytes= protocol=https
  55. 2019-12-16T07:30:17.006843+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fullstack-boilerplate.herokuapp.com request_id=d3822dc7-d4f2-4783-b88b-1a346a1151c7 fwd="103.62.49.221" dyno= connect= service= status=503 bytes= protocol=https
  56. 2019-12-16T07:30:18.363463+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fullstack-boilerplate.herokuapp.com request_id=4f93b36c-2496-4f81-90bd-74ca80b01667 fwd="103.62.49.221" dyno= connect= service= status=503 bytes= protocol=https
  57. 2019-12-16T07:31:52.550379+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fullstack-boilerplate.herokuapp.com request_id=8c031f4b-802b-497a-9749-c96a30459dbe fwd="103.62.49.221" dyno= connect= service= status=503 bytes= protocol=https
  58. 2019-12-16T07:32:02.251865+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fullstack-boilerplate.herokuapp.com request_id=e44e55cb-f8f9-43fa-8cf4-315461a43e3a fwd="103.62.49.221" dyno= connect= service= status=503 bytes= protocol=https
  59. 2019-12-16T07:32:03.026273+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=fullstack-boilerplate.herokuapp.com request_id=a8e25ca2-f279-4c25-96f7-32729c59834c fwd="103.62.49.221" dyno= connect= service= status=503 bytes= protocol=https
  60. 2019-12-16T07:35:01.736473+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fullstack-boilerplate.herokuapp.com request_id=6d83029c-5d36-4257-bfe6-305d34a16239 fwd="103.62.49.221" dyno= connect= service= status=503 bytes= protocol=https
  61. 2019-12-16T07:35:04.084438+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fullstack-boilerplate.herokuapp.com request_id=16badd54-0038-4ce7-b170-1cb5e90e5b20 fwd="103.62.49.221" dyno= connect= service= status=503 bytes= protocol=https
  62. 2019-12-16T07:36:21.396638+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fullstack-boilerplate.herokuapp.com request_id=48d5e6c7-97f4-4b5c-bbd6-087edf6a19de fwd="103.62.49.221" dyno= connect= service= status=503 bytes= protocol=https
  63. 2019-12-16T07:37:29.812335+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fullstack-boilerplate.herokuapp.com request_id=168ca81a-2116-46b8-83e8-a6f3aedf6fd1 fwd="103.62.49.221" dyno= connect= service= status=503 bytes= protocol=https
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement