-
Notifications
You must be signed in to change notification settings - Fork 130
keep getting disconnected from Slack and crashes #108
Comments
Here's an update on what I've found so far. We set the logging level set to debug and I let the bot run for 3 days so that I'd have plenty of data to go through. Heroku says there were 37 crashes but I was only able to find 27 in the log. I have no idea where it got the other 10 crashes from. Anyways, our bot disconnected from Slack 30 times. 26 out of those 30 times there was a crash immediately following the disconnect. 3 of the disconnects occurred when the app was starting up. 2 of the disconnects occurred immediately after the app finished connecting to the Slack Real Time Messaging API. Some of these last 5 disconnections I mentioned also had an error about the socket URL expiring. Is there anything else that I can do on my end to help diagnose this further? |
I'm having this same issue. |
We are also seeing this issue - nothing of note in the logs except the Disconnect message. |
I am seeing something similar as well:
then a crash this message appears approx 1min after startup |
@rsanheim I was able to fix it, but I broke contracts (the user will not be auto-created, nor will the rooms be auto-created). You can check my repo here: https://github.com/Twister915/lita-slack I will do a pull request once I can implement it in such a way that it still creates the users & rooms if they don't exist. For the time being, I was using it like this in my gemfile: Hope you find that useful |
@Twister915 Have you had any luck getting this to work in a way that lets you still create the users & rooms? I reviewed your branch after your last comment. I don't have everything set up currently to where I could debug the application, but I'm happy to help where I can. This bug has been a major issue for our Slack bot and causes it to be down most of the time. |
We're suddenly getting this quite frequently as well. This thread implies that it's because our Slack size has grown significantly, and using |
I've noticed for quite a while now that our lita bot goes offline at random times. We tend to say that the bot is asleep, but this past week we changed our Heroku account over so that it's no longer on the legacy dynos. Our app now runs 24/7 so that we know it's not an issue with Heroku putting the app to sleep.
I started going through our logs for the past 24 hours and at first I thought I saw a pattern where each time the app crashed the log right before it would say
Error with code 1 received from Slack: Socket URL has expired
but as I went through more crashes I started to notice that a few didn't have that at all. I'm not sure else what to try and would gladly take any suggestions you might have! I'll post snippets from our crashes below to help you get an idea what I've been seeing.The text was updated successfully, but these errors were encountered: