Spontaneous Connection reset by peer errors #10

New Issue

2020-05-21T12:16:37-04:00

Bsian commented

2020-05-21 12:16:37 -04:00

(Migrated from gitlab.libraryofcode.org)

BUG REPORT

Brief Description: At random points, but at least a few times per day, the bot will throw a ws close code of 1006, Connection reset by peer. This causes a lot of spam in the error channel out of nowhere.

Priority: (1-5, 5 being the most urgent) 3

We realistically have 2 options we can take, and 3 possible:

Ignore the errors, possibly suppressing them.
Do some very serious debugging to see where the issue is coming from. ~~At the moment, we cannot tell if this is due to some sort of cloudflare proxy, though we have been receiving a couple of those as well~~ Cloudflare proxy isn't an issue since we do not use one
Rewrite the whole bot to match the structure and framework of the Cloud Services bot, which will be released in a new major.

~~Unless we are certain option 2 is being caused by a cloudflare proxy, then we will only have options 1 and 3 that we can do easily~~
Option 1 should be avoided though, since it is still technically an unclean closure of the websocket connection to Discord.
Option 3 also would take some time as testing is required to make sure everything works the same way.

Opinions would be greatly appreciated. Leave a comment in this issue and share your thoughts

# BUG REPORT **Brief Description:** At random points, but at least a few times per day, the bot will throw a ws close code of 1006, Connection reset by peer. This causes a lot of spam in the error channel out of nowhere. **Priority:** (1-5, 5 being the most urgent) 3 We realistically have 2 options we can take, and 3 possible: 1. Ignore the errors, possibly suppressing them. 2. Do some very serious debugging to see where the issue is coming from. ~~At the moment, we cannot tell if this is due to some sort of cloudflare proxy, though we have been receiving a couple of those as well~~ Cloudflare proxy isn't an issue since we do not use one 3. Rewrite the whole bot to match the structure and framework of the Cloud Services bot, which will be released in a new major. ~~Unless we are certain option 2 is being caused by a cloudflare proxy, then we will only have options 1 and 3 that we can do easily~~ Option 1 should be avoided though, since it is still technically an unclean closure of the websocket connection to Discord. Option 3 also would take some time as testing is required to make sure everything works the same way. Opinions would be greatly appreciated. Leave a comment in this issue and share your thoughts

DedShotTM commented

2020-05-22 19:10:32 -04:00

(Migrated from gitlab.libraryofcode.org)

I think we could start by trying to find from where the issue comes from

Bsian commented

2020-05-22 21:25:46 -04:00

(Migrated from gitlab.libraryofcode.org)

I've already been trying to do some debugging from Eris, unfortunately WS code 1006 doesn't give a reason why the connection was uncleanly closed.

Bsian commented

2020-05-22 21:27:14 -04:00

(Migrated from gitlab.libraryofcode.org)

changed the description

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: engineering/community-relations#10