Hubot-rocketchat-boilerplate Disconnect Issues


We have a rocketchat integration with our software using hubot to tie it all together. We previously were using the docker image of the rocket chat hubot without issues. When we upgraded to Rocket Chat 3.9.2 we have run into several issues with the bot. First off, we had to manually apply a fix to the bot to get it working at all. Fix found in this post (Bbot isn't working anymore · Issue #19566 · RocketChat/Rocket.Chat · GitHub) for file driver.js.

After we put that fix in place with a manual install of hubot-rocketchat-boilerplate it started working again. However, now the bot disconnects periodically without any errors we can find. When it disconnects It will no longer show as “on line” and won’t respond to messages, however the hubot program/service is still running without any errors on that end. We tried combing through the Rocket Chat logs and didn’t find anything definitive.

We tried doing a manual install of the GitHub - RocketChat/hubot-rocketchat: Rocket.Chat Hubot adapter repo (different from boilerplate) as I believe that’s what the docker image was using, however we can’t find the driver.js file in that repo to do the fix, so we can’t get a manual install of that one up and running to see if it will resolve our disconnect issues.

It almost feels like a “rate limiter” type issue, since if we execute our “help” command to the bot about 30-40 times in a row, it breaks it and kicks it offline. We currently have both the API and DDP rate limiters disabled and this still occurs.

We currently have to “babysit” this bot and manually restart it throughout the day given these disconnect issues. Any help or suggestions to get the bot stable again would be much appreciated!

Server Setup Information

  • Version of Rocket.Chat Server: 3.9.2
  • Operating System: Debian 10.7 4.19.0-13-amd64
  • Deployment Method: downloaded tar and installed
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: v12.18.4
  • MongoDB Version: 3.6.21
  • Proxy: apache
  • Firewalls involved: