Can't enable metabot in Slack settings

jasonmadrid · August 2, 2016, 7:09pm

Hello,

Great project, we’re loving it.

We’re trying to enable the Slack integration and metabot. I’ve tried with both a slack test key and with setting up a bot in Slack. Pulses work great, so we know the integration is working to that extent.

However, we can’t enable metabot. In the Slack settings panel, the switch is set to ‘Disabled’ and grayed out. We can’t click the slider to enable it.

Thank you.

sameer · August 3, 2016, 11:45pm

Huh!

Which os + browser is this on? If you have another browser can you verify that it’s broken there as well?

jasonmadrid · August 4, 2016, 12:02am

Chrome + Mac. I just tried Safari and Firefox also. Same problem.

jasonmadrid · August 4, 2016, 4:00pm

we’re getting this spammed in our metabase logs:

08-04 15:53:38 ERROR metabase.metabot :: Error connecting websocket: clj-http: status 429
08-04 15:53:39 ERROR metabase.metabot :: Error connecting websocket: clj-http: status 429
08-04 15:53:39 ERROR metabase.metabot :: Error connecting websocket: clj-http: status 429
08-04 15:53:40 ERROR metabase.metabot :: Error connecting websocket: clj-http: status 429
08-04 15:53:41 ERROR metabase.metabot :: Error connecting websocket: clj-http: status 429
08-04 15:53:42 ERROR metabase.metabot :: Error connecting websocket: clj-http: status 429
08-04 15:53:43 ERROR metabase.metabot :: Error connecting websocket: clj-http: status 429
08-04 15:53:44 ERROR metabase.metabot :: Error connecting websocket: clj-http: status 429
08-04 15:53:44 ERROR metabase.metabot :: Error connecting websocket: clj-http: status 429
08-04 15:53:45 ERROR metabase.metabot :: Error connecting websocket: clj-http: status 429
08-04 15:53:46 ERROR metabase.metabot :: Error connecting websocket: clj-http: status 429
08-04 15:53:46 ERROR metabase.metabot :: Error connecting websocket: clj-http: status 429
08-04 15:53:47 ERROR metabase.metabot :: Error connecting websocket: clj-http: status 429

sameer · August 5, 2016, 12:04am

wrt to the metabot switch, this is fixed in the patch release we just pushed (0.19.1)

codeanand · August 12, 2016, 2:56am

@sameer I seem to be have the same issue

I am running 0.19.1

08-11 22:57:07 ERROR metabase.metabot :: Error connecting websocket: Read timed out

I am a developer, if you can help me understand what is happening. I will try to fix the issue and contribute back to the repo

sameer · August 13, 2016, 1:36am

The code in question lives at

github.com

metabase/metabase/blob/master/src/metabase/metabot.clj#L247


      (do (future (try
                    (handle-slack-message event)
                    (catch Throwable t
                      (slack/post-chat-message! *channel-id* (format-exception t)))))
          nil)))))




;;; # ------------------------------------------------------------ Websocket Connection Stuff ------------------------------------------------------------


(defn- connect-websocket! []
(when-let [websocket-url (slack/websocket-url)]
  (let [socket @(aleph/websocket-client websocket-url)]
    (reset! websocket socket)
    (d/catch (s/consume (partial handle-slack-event socket (System/currentTimeMillis))
                        socket)
        (fn [error]
          (log/error (trs "Error launching metabot:") error))))))


(defn- disconnect-websocket! []
(when-let [socket @websocket]
  (reset! websocket nil)

A read timeout suggests network connectivity issues or a misconfiguration.

A status 429 (https://httpstatuses.com/429) is Metabot being rate limited. Not sure exactly what’s going on there. If you can do a bit of research on Bot tokens vs developer API tokens, and how we should listen to web sockets, that would be really useful =)