Socket :close isn't properly restarting bot

[dblock]

2015-12-24T13:18:48.644709+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-bot-0.5.1/lib/slack-ruby-bot/server.rb:61:in `restart!'
2015-12-24T13:18:48.644716+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-bot-0.5.1/lib/slack-ruby-bot/server.rb:61:in `restart!'
2015-12-24T13:18:48.644727+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-bot-0.5.1/lib/slack-ruby-bot/server.rb:61:in `restart!'
2015-12-24T13:18:48.644735+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-bot-0.5.1/lib/slack-ruby-bot/server.rb:61:in `restart!'
2015-12-24T13:18:48.644740+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-bot-0.5.1/lib/slack-ruby-bot/server.rb:61:in `restart!'
2015-12-24T13:18:48.644745+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-bot-0.5.1/lib/slack-ruby-bot/server.rb:61:in `restart!'
2015-12-24T13:18:48.644753+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-client-0.5.0/lib/slack/real_time/client.rb:102:in `block (2 levels) in run_loop'
2015-12-24T13:18:48.644717+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-bot-0.5.1/lib/slack-ruby-bot/server.rb:70:in `rescue in restart!'

[dblock]

It doesn't look like dblock/slack-ruby-bot@fbd06a1 fixed this :(

[dblock]

The fix above will route a restart via SlackGamebot::Service.restart! which will disable a team that was turned off via account_inactive, so it won't loop forever causing stack overflows and what not.