Skip to content
GitLab
Open
Issue created by Dave Cadwallader@geekdaveContributor

Slack Bot won't come online

Thanks so much for this project! Looks like exactly what my team needs.

This might be a n00b kind of problem, but I'm unable to get my Slackbot to come online.

I used the Heroku install. Here's what I did so far:

Set up PagerDuty:

pagerbot_admin

Set up Slack:

pagerbot_admin

Set up plugins (I only enabled the ones that didn't require inputs for now):

pagerbot_admin

Deployed by switching off the web app and switching on the bot app.

I can see the bot in Slack but it won't come online:

slack_-_walmart_labs

Here are the logs when I start up the bot:

Feb 09 08:58:01 test-pagerbot heroku/router:  at=error code=H14 desc="No web processes running" method=GET path="/api/bot" host=xxxxxxxxxx.herokuapp.com request_id=xxxxxxxxxxxxxxxx
Feb 09 08:58:02 test-pagerbot heroku/router:  at=error code=H14 desc="No web processes running" method=GET path="/views/bot.html" host=xxxxxxxxxx.herokuapp.com request_id=xxxxxxxxxxxxxxxx
Feb 09 08:58:07 test-pagerbot heroku/router:  at=error code=H14 desc="No web processes running" method=GET path="/" host=xxxxxxxxxx.herokuapp.com request_id=xxxxxxxxxxxxxxxx
Feb 09 08:58:16 test-pagerbot app/api:  Scaled to bot@1:Free console@0:Free rake@0:Free web@1:Free by user dcadwallader@gmail.com 
Feb 09 08:58:17 test-pagerbot heroku/bot.1:  State changed from crashed to down 
Feb 09 08:58:18 test-pagerbot app/api:  Scaled to bot@0:Free console@0:Free rake@0:Free web@1:Free by user dcadwallader@gmail.com 
Feb 09 08:58:18 test-pagerbot heroku/web.1:  Starting process with command `bundle exec ruby lib/pagerbot.rb web` 
Feb 09 08:58:20 test-pagerbot app/web.1:  fatal: Not a git repository (or any parent up to mount point /app) 
Feb 09 08:58:20 test-pagerbot app/web.1:  Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). 
Feb 09 08:58:21 test-pagerbot app/web.1:  2017-02-09 16:58:20.898531 I [4:70187052317060] PagerBot -- Starting application -- {:is_admin=>true, :argv=>["web"]} 
Feb 09 08:58:21 test-pagerbot app/web.1:  == Sinatra (v1.4.8) has taken the stage on 56160 for production with backup from Thin 
Feb 09 08:58:21 test-pagerbot heroku/web.1:  State changed from starting to up 
Feb 09 08:58:22 test-pagerbot app/web.1:  216.207.42.140 - - [09/Feb/2017:16:58:22 +0000] "GET / HTTP/1.1" 200 3634 0.0066 
Feb 09 08:58:22 test-pagerbot heroku/router:  at=info method=GET path="/" host=xxxxxxxxxx.herokuapp.com request_id=xxxxxxxxxxxxxxxx
Feb 09 08:58:22 test-pagerbot heroku/router:  at=info method=GET path="/api/bot" host=xxxxxxxxxx.herokuapp.com request_id=xxxxxxxxxxxxxxxx
Feb 09 08:58:23 test-pagerbot heroku/router:  at=info method=GET path="/views/bot.html" host=xxxxxxxxxx.herokuapp.com request_id=xxxxxxxxxxxxxxxx
Feb 09 08:58:23 test-pagerbot app/web.1:  216.207.42.140 - - [09/Feb/2017:16:58:22 +0000] "GET /views/bot.html HTTP/1.1" 200 5226 0.0016 
Feb 09 08:58:23 test-pagerbot heroku/router:  at=info method=GET path="/api/bot" host=xxxxxxxxxx.herokuapp.com request_id=xxxxxxxxxxxxxxxx
Feb 09 08:58:23 test-pagerbot app/web.1:  216.207.42.140 - - [09/Feb/2017:16:58:22 +0000] "GET /api/bot HTTP/1.1" 200 225 0.0421 
Feb 09 08:58:23 test-pagerbot app/web.1:  216.207.42.140 - - [09/Feb/2017:16:58:22 +0000] "GET /api/bot HTTP/1.1" 200 225 0.0289 
Feb 09 08:58:23 test-pagerbot heroku/router:  at=info method=GET path="/api/pagerduty" host=xxxxxxxxxx.herokuapp.com request_id=xxxxxxxxxxxxxxxx
Feb 09 08:58:23 test-pagerbot app/web.1:  2017-02-09 16:58:23.123269 I [4:70187065891660] (592.9ms) PagerBot::AdminPage -- Checking pagerduty connectivity. 
Feb 09 08:58:23 test-pagerbot app/web.1:  216.207.42.140 - - [09/Feb/2017:16:58:23 +0000] "GET /api/pagerduty HTTP/1.1" 200 93 0.6625 
Feb 09 08:58:27 test-pagerbot heroku/router:  at=info method=POST path="/api/bot" host=xxxxxxxxxx.herokuapp.com request_id=xxxxxxxxxxxxxxxx
Feb 09 08:58:28 test-pagerbot app/web.1:  216.207.42.140 - - [09/Feb/2017:16:58:27 +0000] "POST /api/bot HTTP/1.1" 200 235 0.0285 
Feb 09 08:58:30 test-pagerbot heroku/router:  at=info method=GET path="/api/plugins" host=xxxxxxxxxx.herokuapp.com request_id=xxxxxxxxxxxxxxxx
Feb 09 08:58:30 test-pagerbot app/web.1:  216.207.42.140 - - [09/Feb/2017:16:58:30 +0000] "GET /api/plugins HTTP/1.1" 200 1994 0.0637 
Feb 09 08:58:33 test-pagerbot heroku/router:  at=info method=GET path="/api/users" host=xxxxxxxxxx.herokuapp.com request_id=xxxxxxxxxxxxxxxx
Feb 09 08:58:33 test-pagerbot app/web.1:  2017-02-09 16:58:32.930503 I [4:70187065890220] (533.7ms) PagerBot::DataStore -- Fetching collection from pagerduty. 
Feb 09 08:58:33 test-pagerbot app/web.1:  2017-02-09 16:58:32.930681 I [4:70187065890220] PagerBot::DataStore -- Added to users: [] 
Feb 09 08:58:33 test-pagerbot app/web.1:  2017-02-09 16:58:32.932656 I [4:70187065890220] PagerBot::DataStore -- Removed from users: [] 
Feb 09 08:58:33 test-pagerbot app/web.1:  2017-02-09 16:58:32.937218 I [4:70187065890220] PagerBot::DataStore -- Refreshed collection. -- {:collection_name=>"users", :total=>8, :added=>0, :removed=>0} 
Feb 09 08:58:33 test-pagerbot app/web.1:  216.207.42.140 - - [09/Feb/2017:16:58:32 +0000] "GET /api/users HTTP/1.1" 200 10615 0.5806 
Feb 09 08:59:10 test-pagerbot app/api:  Scaled to bot@1:Free console@0:Free rake@0:Free web@1:Free by user dcadwallader@gmail.com 
Feb 09 08:59:12 test-pagerbot heroku/bot.1:  Starting process with command `bundle exec ruby lib/pagerbot.rb` 
Feb 09 08:59:13 test-pagerbot heroku/bot.1:  State changed from starting to up 
Feb 09 08:59:15 test-pagerbot app/bot.1:  fatal: Not a git repository (or any parent up to mount point /app) 
Feb 09 08:59:15 test-pagerbot app/bot.1:  Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). 
Feb 09 08:59:16 test-pagerbot app/bot.1:  2017-02-09 16:59:15.911067 I [4:70183564769660] PagerBot -- Starting application -- {:is_admin=>false, :argv=>[]} 
Feb 09 08:59:16 test-pagerbot app/bot.1:  2017-02-09 16:59:15.988586 I [4:70183564769660] PagerBot::PluginManager -- Loading plugin. -- {:name=>"add_alias", :class=>"PagerBot::Plugins::AddAlias", :config=>{}} 
Feb 09 08:59:16 test-pagerbot app/bot.1:  2017-02-09 16:59:15.989743 I [4:70183564769660] PagerBot::PluginManager -- Loading plugin. -- {:name=>"reload", :class=>"PagerBot::Plugins::Reload", :config=>{}} 
Feb 09 08:59:16 test-pagerbot app/bot.1:  2017-02-09 16:59:15.990276 I [4:70183564769660] PagerBot::PluginManager -- Loading plugin. -- {:name=>"schedule_override", :class=>"PagerBot::Plugins::ScheduleOverride", :config=>{}} 
Feb 09 08:59:16 test-pagerbot app/bot.1:  2017-02-09 16:59:15.991089 I [4:70183564769660] PagerBot::PluginManager -- Loading plugin. -- {:name=>"switch_shift", :class=>"PagerBot::Plugins::SwitchShift", :config=>{}} 
Feb 09 08:59:23 test-pagerbot app/bot.1:  W, [2017-02-09T16:59:22.459558 #4]  WARN -- : You are setting a key that conflicts with a built-in method Slack::Messages::Message#presence defined at /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-client-0.7.8/lib/slack/messages/message.rb:4. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method. 
Feb 09 08:59:23 test-pagerbot app/bot.1:  W, [2017-02-09T16:59:22.463755 #4]  WARN -- : You are setting a key that conflicts with a built-in method Slack::Messages::Message#presence defined at /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-client-0.7.8/lib/slack/messages/message.rb:4. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method. 
Feb 09 08:59:23 test-pagerbot app/bot.1:  W, [2017-02-09T16:59:22.466233 #4]  WARN -- : You are setting a key that conflicts with a built-in method Slack::Messages::Message#presence defined at /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-client-0.7.8/lib/slack/messages/message.rb:4. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method. 
Feb 09 08:59:23 test-pagerbot app/bot.1:  W, [2017-02-09T16:59:22.538811 #4]  WARN -- : You are setting a key that conflicts with a built-in method Slack::Messages::Message#presence defined at /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-client-0.7.8/lib/slack/messages/message.rb:4. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method. 
Feb 09 08:59:23 test-pagerbot app/bot.1:  W, [2017-02-09T16:59:22.540161 #4]  WARN -- : You are setting a key that conflicts with a built-in method Slack::Messages::Message#presence defined at /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-client-0.7.8/lib/slack/messages/message.rb:4. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method. 
Feb 09 08:59:23 test-pagerbot app/bot.1:  W, [2017-02-09T16:59:22.542076 #4]  WARN -- : You are setting a key that conflicts with a built-in method Slack::Messages::Message#presence defined at /app/vendor/bundle/ruby/2.2.0/gems/slack-ruby-client-0.7.8/lib/slack/messages/message.rb:4. This can cause unexpected behavior when accessing the key via as a property. You can still access the key via the #[] method.

Hopefully I'm just doing something silly. Thanks again for your work on this!