Skip to content

Instantly share code, notes, and snippets.

@valenso
Created March 11, 2016 19:55
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save valenso/78cdb3c1bf8542d7d3c3 to your computer and use it in GitHub Desktop.
Save valenso/78cdb3c1bf8542d7d3c3 to your computer and use it in GitHub Desktop.
2016-03-11T17:28:20.006310+00:00 heroku[web.1]: Restarting
2016-03-11T17:28:21.957210+00:00 heroku[web.1]: Starting process with command `bundle exec ruby telegram.rb -p 4567`
2016-03-11T17:28:24.158336+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2016-03-11T17:28:24.848390+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/telegram-bot-ruby-0.4.1/lib/telegram/bot/api.rb:49:in `call': Telegram API has returned the error. (ok: "false", error_code: "409", description: "[Error]: Conflict: terminated by other long poll or webhook") (Telegram::Bot::Exceptions::ResponseError)
2016-03-11T17:28:24.848409+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.2.0/gems/telegram-bot-ruby-0.4.1/lib/telegram/bot/client.rb:34:in `fetch_updates'
2016-03-11T17:28:24.848406+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.2.0/gems/telegram-bot-ruby-0.4.1/lib/telegram/bot/api.rb:40:in `method_missing'
2016-03-11T17:28:24.848410+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.2.0/gems/telegram-bot-ruby-0.4.1/lib/telegram/bot/client.rb:29:in `listen'
2016-03-11T17:28:24.848410+00:00 app[web.1]: from telegram.rb:11:in `block in <main>'
2016-03-11T17:28:24.848411+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.2.0/gems/telegram-bot-ruby-0.4.1/lib/telegram/bot/client.rb:22:in `run'
2016-03-11T17:28:24.848412+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.2.0/gems/telegram-bot-ruby-0.4.1/lib/telegram/bot/client.rb:10:in `run'
2016-03-11T17:28:24.848413+00:00 app[web.1]: from telegram.rb:7:in `<main>'
2016-03-11T17:28:25.809101+00:00 heroku[web.1]: Process exited with status 1
2016-03-11T17:29:22.538772+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2016-03-11T17:29:22.538772+00:00 heroku[web.1]: Stopping process with SIGKILL
2016-03-11T17:29:23.320035+00:00 heroku[web.1]: Process exited with status 137
2016-03-11T17:29:23.329744+00:00 heroku[web.1]: State changed from starting to crashed
2016-03-11T17:37:03.974446+00:00 heroku[web.1]: State changed from crashed to starting
2016-03-11T17:37:07.130135+00:00 heroku[web.1]: Starting process with command `bundle exec ruby telegram.rb -p 4567`
2016-03-11T17:38:07.764664+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2016-03-11T17:38:07.764664+00:00 heroku[web.1]: Stopping process with SIGKILL
2016-03-11T17:38:08.763309+00:00 heroku[web.1]: Process exited with status 137
2016-03-11T17:38:08.800510+00:00 heroku[web.1]: State changed from starting to crashed
2016-03-11T18:01:14.022615+00:00 heroku[web.1]: State changed from crashed to starting
2016-03-11T18:01:15.976120+00:00 heroku[web.1]: Starting process with command `bundle exec ruby telegram.rb -p 4567`
2016-03-11T18:02:16.321410+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2016-03-11T18:02:16.321410+00:00 heroku[web.1]: Stopping process with SIGKILL
2016-03-11T18:02:17.036845+00:00 heroku[web.1]: State changed from starting to crashed
2016-03-11T18:02:17.008910+00:00 heroku[web.1]: Process exited with status 137
2016-03-11T18:45:25.871347+00:00 heroku[web.1]: State changed from crashed to starting
2016-03-11T18:45:28.255219+00:00 heroku[web.1]: Starting process with command `bundle exec ruby telegram.rb -p 4567`
2016-03-11T18:46:28.798022+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2016-03-11T18:46:28.798022+00:00 heroku[web.1]: Stopping process with SIGKILL
2016-03-11T18:46:29.815335+00:00 heroku[web.1]: Process exited with status 137
2016-03-11T18:46:29.829320+00:00 heroku[web.1]: State changed from starting to crashed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment