You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
Hi I am using the botkit v 0.5.8
I am getting this stale connection error for my chatbot on slack..i have set the reconnect config to true and tried to debug the issue. It was able to reconnect the first time, but again there was a stale connection, the reconnect attempts failed and the bot went down. Below is the error log:
error: Error: Stale RTM connection, closing RTM
inside bot.closeRTM slackbot_worker.js
inside bot.closeRTM slackbot_worker.js pingTimeoutId[object Object]
** The RTM api just closed
*** 2017-09-11T12:53:13-07:00 ** The RTM api just closed
info: ** API CALL: https://slack.com/api/chat.postMessage
inside if(err && retryEnabled) slackbot_worker.js err is Error: Stale RTM connection, closing RTMretryEnabled is true
Error in Botkit Studio Stats: { [Error: connect ENETDOWN 159.203.98.199:443 - Local (10.254.186.86:62550)]
code: 'ENETDOWN',
errno: 'ENETDOWN',
syscall: 'connect',
address: '159.203.98.199',
port: 443 }
inside the reconnect function
notice: ** BOT ID: whizbot ...reconnect attempt #1 of true being made after 1000ms
inside bot.startRTM function slack_worker.js
info: ** API CALL: https://slack.com/api/rtm.start
startRTM is called from reconnect
error inside startRTM, calling reconnect again errError: getaddrinfo ENOTFOUND slack.com slack.com:443destroyed false
error: ** BOT ID: whizbot ...reconnect failed after #2 attempts and 1000ms
After this the bot was down. Could some one provide some suggestion to keep the bot alive forever.
The text was updated successfully, but these errors were encountered:
Hi I am using the botkit v 0.5.8
I am getting this stale connection error for my chatbot on slack..i have set the reconnect config to true and tried to debug the issue. It was able to reconnect the first time, but again there was a stale connection, the reconnect attempts failed and the bot went down. Below is the error log:
error: Error: Stale RTM connection, closing RTM
inside bot.closeRTM slackbot_worker.js
inside bot.closeRTM slackbot_worker.js pingTimeoutId[object Object]
** The RTM api just closed
*** 2017-09-11T12:53:13-07:00 ** The RTM api just closed
info: ** API CALL: https://slack.com/api/chat.postMessage
inside if(err && retryEnabled) slackbot_worker.js err is Error: Stale RTM connection, closing RTMretryEnabled is true
Error in Botkit Studio Stats: { [Error: connect ENETDOWN 159.203.98.199:443 - Local (10.254.186.86:62550)]
code: 'ENETDOWN',
errno: 'ENETDOWN',
syscall: 'connect',
address: '159.203.98.199',
port: 443 }
inside the reconnect function
notice: ** BOT ID: whizbot ...reconnect attempt #1 of true being made after 1000ms
inside bot.startRTM function slack_worker.js
info: ** API CALL: https://slack.com/api/rtm.start
startRTM is called from reconnect
error inside startRTM, calling reconnect again errError: getaddrinfo ENOTFOUND slack.com slack.com:443destroyed false
error: ** BOT ID: whizbot ...reconnect failed after #2 attempts and 1000ms
After this the bot was down. Could some one provide some suggestion to keep the bot alive forever.
The text was updated successfully, but these errors were encountered: