Websocket connection closing

[Miolus]

Hi. My 2 shards bot disconnects after startup everytime. It does work for 1 h, then this happens:

Somebody knows how to fix it?

[Rapptz]

This is a logging statement from aiohttp. It just indicates the websocket is being closed. Closure is a normal part of the websocket flow in the Discord gateway -- so this isn't particularly weird though it is happening more times than I would expect for an hour.

[Miolus]

@Rapptz It does print the message multiple times, without making it possible for the bot to connect as far as on_ready. The network connection in general is working, my other big bots work, i am hosting in a datacentre. Know how to fix this?

[Rapptz]

There is no information here to actually discern anything so no, I cannot help you. These logging lines are pretty meaningless. If you want to further debug this you're free to enable logging yourself and see what the library is saying. However this is outside the scope of this issue/discussion.

[Harmon758]

Note, for the logging message itself, see https://docs.aiohttp.org/en/stable/logging.html.
Specifically, this is the aiohttp.websocket logger.
This warning was actually removed with aio-libs/aiohttp@b8ba3d0 in aiohttp v3.7.

[YuvanLohia]

is the bot working fine??

[Miolus]

Yes the code works fine, on my testbot the same code works without these connection problems, but with my big bot these problems happen.

[YuvanLohia]

so, if the code is working fine and bot is running well then leave the error

[Miolus]

probably same as as here aio-libs/aiohttp#1768

[Miolus]

@Rapptz I started logging. This is the log for the messages: 2021-01-14 07:36:38,720:WARNING:discord.gateway: Shard ID 0 has stopped responding to the gateway. Closing and restarting. 2021-01-14 07:36:38,724:WARNING:discord.gateway: Shard ID 1 has stopped responding to the gateway. Closing and restarting. 2021-01-14 07:36:40,796:INFO:discord.gateway: Websocket closed with 4000, attempting a reconnect. 2021-01-14 07:36:40,801:INFO:discord.gateway: Shard ID 0 has sent the IDENTIFY payload. 2021-01-14 07:36:40,821:INFO:discord.shard: Got a request to RESUME the websocket at Shard ID 1. 2021-01-14 07:36:40,823:WARNING:discord.state: Shard ID 3 failed to wait for chunks from a sub-bucket with length 8 2021-01-14 07:36:40,843:INFO:discord.gateway: Websocket closed with 4000, attempting a reconnect. 2021-01-14 07:36:41,141:INFO:discord.gateway: Shard ID 1 has sent the RESUME payload. 2021-01-14 07:36:41,147:INFO:discord.shard: Got a request to RESUME the websocket at Shard ID 0. 2021-01-14 07:36:41,256:INFO:discord.gateway: Shard ID 1 session has been invalidated. 2021-01-14 07:36:41,282:INFO:discord.gateway: Shard ID 0 has sent the RESUME payload. 2021-01-14 07:36:41,300:INFO:discord.shard: Got a request to IDENTIFY the websocket at Shard ID 2. 2021-01-14 07:36:41,382:INFO:discord.gateway: Shard ID 0 session has been invalidated. 2021-01-14 07:36:46,438:INFO:discord.gateway: Shard ID 2 has sent the IDENTIFY payload. 2021-01-14 07:36:46,462:INFO:discord.shard: Got a request to IDENTIFY the websocket at Shard ID 3.

[izxxr]

Hi, It almost has been a month to this issue and I'm replying late but this usually happens on API abuse (detected by discord).
If you have a while loop that literally does something every 5 minutes or less without a delay, then try to make that task a little delayed preferably, 10-30 seconds in order to fix it.
Most bots have changing presence using asyncio library, If you do too, make it a little delayed.

[Miolus]

Thanks for your reply, the problem was actually caused by not enough ram.