Advertisement
RFlintstone

Heroku crash log support bot FC

Mar 1st, 2018
115
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.87 KB | None | 0 0
  1. 2018-03-01T12:20:03.887350+00:00 app[web.1]: Ticket #395865787</b> from Ruben @RFlintstone Language: nl: hi
  2. 2018-03-01T12:20:03.972970+00:00 app[web.1]: (node:20) UnhandledPromiseRejectionWarning: Error: 400: Bad Request: group chat was upgraded to a supergroup chat
  3. 2018-03-01T12:20:03.972974+00:00 app[web.1]: at buildConfig.then.then.then.then (/app/node_modules/telegraf/core/network/client.js:235:17)
  4. 2018-03-01T12:20:03.972979+00:00 app[web.1]: at <anonymous>
  5. 2018-03-01T12:20:03.973416+00:00 app[web.1]: (node:20) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 5)
  6. 2018-03-01T12:20:03.972982+00:00 app[web.1]: at process._tickCallback (internal/process/next_tick.js:160:7)
  7. 2018-03-01T12:20:34.423802+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
  8. 2018-03-01T12:20:34.423965+00:00 heroku[web.1]: Stopping process with SIGKILL
  9. 2018-03-01T12:20:34.499403+00:00 heroku[web.1]: Process exited with status 137
  10. 2018-03-01T12:20:34.512476+00:00 heroku[web.1]: State changed from starting to crashed
  11. 2018-03-01T12:21:52.000000+00:00 app[api]: Build started by user werdev@hotmail.com
  12. 2018-03-01T12:22:02.386243+00:00 heroku[web.1]: State changed from crashed to starting
  13. 2018-03-01T12:22:02.075116+00:00 app[api]: Deploy 3f963268 by user werdev@hotmail.com
  14. 2018-03-01T12:21:52.000000+00:00 app[api]: Build succeeded
  15. 2018-03-01T12:22:02.075116+00:00 app[api]: Release v60 created by user werdev@hotmail.com
  16. 2018-03-01T12:22:05.529821+00:00 heroku[web.1]: Starting process with command `npm start`
  17. 2018-03-01T12:22:08.571452+00:00 heroku[web.1]: Process exited with status 1
  18. 2018-03-01T12:22:08.289035+00:00 app[web.1]:
  19. 2018-03-01T12:22:08.289052+00:00 app[web.1]: > telegram-support-bot@0.10.0 start /app
  20. 2018-03-01T12:22:08.289053+00:00 app[web.1]: > node bin/support.js
  21. 2018-03-01T12:22:08.289055+00:00 app[web.1]:
  22. 2018-03-01T12:22:08.456696+00:00 app[web.1]: /app/bin/support.js:18
  23. 2018-03-01T12:22:08.456700+00:00 app[web.1]: const bot = new Telegraf(API_TOKEN)
  24. 2018-03-01T12:22:08.456702+00:00 app[web.1]: ^
  25. 2018-03-01T12:22:08.456704+00:00 app[web.1]:
  26. 2018-03-01T12:22:08.456706+00:00 app[web.1]: SyntaxError: Identifier 'bot' has already been declared
  27. 2018-03-01T12:22:08.456708+00:00 app[web.1]: at new Script (vm.js:51:7)
  28. 2018-03-01T12:22:08.456710+00:00 app[web.1]: at createScript (vm.js:138:10)
  29. 2018-03-01T12:22:08.456712+00:00 app[web.1]: at Object.runInThisContext (vm.js:199:10)
  30. 2018-03-01T12:22:08.456713+00:00 app[web.1]: at Module._compile (module.js:626:28)
  31. 2018-03-01T12:22:08.456715+00:00 app[web.1]: at Object.Module._extensions..js (module.js:673:10)
  32. 2018-03-01T12:22:08.456716+00:00 app[web.1]: at Module.load (module.js:575:32)
  33. 2018-03-01T12:22:08.456718+00:00 app[web.1]: at tryModuleLoad (module.js:515:12)
  34. 2018-03-01T12:22:08.456719+00:00 app[web.1]: at Function.Module._load (module.js:507:3)
  35. 2018-03-01T12:22:08.456721+00:00 app[web.1]: at Function.Module.runMain (module.js:703:10)
  36. 2018-03-01T12:22:08.456723+00:00 app[web.1]: at startup (bootstrap_node.js:193:16)
  37. 2018-03-01T12:22:08.467913+00:00 app[web.1]: npm ERR! code ELIFECYCLE
  38. 2018-03-01T12:22:08.468448+00:00 app[web.1]: npm ERR! errno 1
  39. 2018-03-01T12:22:08.470164+00:00 app[web.1]: npm ERR! telegram-support-bot@0.10.0 start: `node bin/support.js`
  40. 2018-03-01T12:22:08.470361+00:00 app[web.1]: npm ERR! Exit status 1
  41. 2018-03-01T12:22:08.470663+00:00 app[web.1]: npm ERR!
  42. 2018-03-01T12:22:08.470889+00:00 app[web.1]: npm ERR! Failed at the telegram-support-bot@0.10.0 start script.
  43. 2018-03-01T12:22:08.471097+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
  44. 2018-03-01T12:22:08.486648+00:00 app[web.1]:
  45. 2018-03-01T12:22:08.487365+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
  46. 2018-03-01T12:22:08.487721+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-03-01T12_22_08_472Z-debug.log
  47. 2018-03-01T12:22:08.600153+00:00 heroku[web.1]: State changed from starting to crashed
  48. 2018-03-01T12:22:08.603132+00:00 heroku[web.1]: State changed from crashed to starting
  49. 2018-03-01T12:22:11.254684+00:00 heroku[web.1]: Starting process with command `npm start`
  50. 2018-03-01T12:22:14.186539+00:00 heroku[web.1]: Process exited with status 1
  51. 2018-03-01T12:22:13.884276+00:00 app[web.1]:
  52. 2018-03-01T12:22:13.884304+00:00 app[web.1]: > telegram-support-bot@0.10.0 start /app
  53. 2018-03-01T12:22:13.884309+00:00 app[web.1]: > node bin/support.js
  54. 2018-03-01T12:22:13.884310+00:00 app[web.1]:
  55. 2018-03-01T12:22:13.971956+00:00 app[web.1]: /app/bin/support.js:18
  56. 2018-03-01T12:22:13.971960+00:00 app[web.1]: const bot = new Telegraf(API_TOKEN)
  57. 2018-03-01T12:22:13.971962+00:00 app[web.1]: ^
  58. 2018-03-01T12:22:13.971964+00:00 app[web.1]:
  59. 2018-03-01T12:22:13.971983+00:00 app[web.1]: SyntaxError: Identifier 'bot' has already been declared
  60. 2018-03-01T12:22:13.971985+00:00 app[web.1]: at new Script (vm.js:51:7)
  61. 2018-03-01T12:22:13.971987+00:00 app[web.1]: at createScript (vm.js:138:10)
  62. 2018-03-01T12:22:13.971988+00:00 app[web.1]: at Object.runInThisContext (vm.js:199:10)
  63. 2018-03-01T12:22:13.971990+00:00 app[web.1]: at Module._compile (module.js:626:28)
  64. 2018-03-01T12:22:13.971991+00:00 app[web.1]: at Object.Module._extensions..js (module.js:673:10)
  65. 2018-03-01T12:22:13.971993+00:00 app[web.1]: at Module.load (module.js:575:32)
  66. 2018-03-01T12:22:13.971995+00:00 app[web.1]: at tryModuleLoad (module.js:515:12)
  67. 2018-03-01T12:22:13.971996+00:00 app[web.1]: at Function.Module._load (module.js:507:3)
  68. 2018-03-01T12:22:13.971998+00:00 app[web.1]: at Function.Module.runMain (module.js:703:10)
  69. 2018-03-01T12:22:13.971999+00:00 app[web.1]: at startup (bootstrap_node.js:193:16)
  70. 2018-03-01T12:22:13.977409+00:00 app[web.1]: npm ERR! code ELIFECYCLE
  71. 2018-03-01T12:22:13.977820+00:00 app[web.1]: npm ERR! errno 1
  72. 2018-03-01T12:22:13.978961+00:00 app[web.1]: npm ERR! telegram-support-bot@0.10.0 start: `node bin/support.js`
  73. 2018-03-01T12:22:13.979084+00:00 app[web.1]: npm ERR! Exit status 1
  74. 2018-03-01T12:22:13.979291+00:00 app[web.1]: npm ERR!
  75. 2018-03-01T12:22:13.979444+00:00 app[web.1]: npm ERR! Failed at the telegram-support-bot@0.10.0 start script.
  76. 2018-03-01T12:22:13.979595+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
  77. 2018-03-01T12:22:13.985099+00:00 app[web.1]:
  78. 2018-03-01T12:22:13.985261+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
  79. 2018-03-01T12:22:13.985298+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2018-03-01T12_22_13_980Z-debug.log
  80. 2018-03-01T12:22:14.356130+00:00 heroku[web.1]: State changed from starting to crashed
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement