Multiple "rate-limit hit, retrying"

[thbar]

I did a simple test with one token, where I cut the wifi connection. Ultimately the connection resumes, but it seems like we have more instances of connections also trying to resume, hitting rate limits.

Here is an extract of my log file (I could send you the whole file by email if you'd like) :

ERRO[2097] error reading message from slack websocket connection  error=websocket: unexpected reserved bits 6 team=MYTEAMID
ERRO[2097] error reading message from slack websocket connection  error=websocket: unexpected reserved bits 5 team=MYTEAMID
INFO[2097] restarting client from within the read loop   team=MYTEAMID
# SNIP
ERRO[2102] error reading message from slack websocket connection  error=read tcp 10.0.1.3:50919->52.87.151.152:443: use of closed network connection team=MYTEAMID
INFO[2102] restarting client from within the read loop   team=MYTEAMID
# SNIP
INFO[2152] Sending message_new for this user and channel  channelId=SOMEID # SNIP
DEBU[2152] sending event back to client                  channel=SOMEID team=MYTEAMID timestamp=1476174981.000010
INFO[2178] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2178] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2179] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2179] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2179] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2179] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2179] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2179] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2179] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2179] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2179] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2183] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2183] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2184] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2184] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2184] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2189] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2189] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2193] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2194] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2199] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID
INFO[2200] rate-limit hit, retrying                      retry-after=60 team=MYTEAMID

I do not know if those logs should be ignored or not, which is why I'm opening that issue.

[bobics]

@thbar We're seeing the same issue, did you ever figure out a resolution?

[thbar]

@bobics I ultimately switched to a more in-house code (for other reasons), and never went much further, so I cannot help you solve this, sorry!