-
-
Notifications
You must be signed in to change notification settings - Fork 70
Heartbeat/Websocket connection error #351
Comments
Note: it's been running for hours. I figure it's a reconnect issue. |
I noticed that once the voice client have connected it updates a variable I believe this is the issue, and that has now been patched here: 4a4d9ae If the issue persists. Please comment so and I will open up the issue. |
Do you have more of the logs? What has been happening before?
…On Tue, 8 Dec 2020, 02:28 Christian Baldwin, ***@***.***> wrote:
After about 16 hours or so.....I've been getting the opcode 2 error
again, v0.22
[image: image]
<https://user-images.githubusercontent.com/39172279/101426328-c2f02780-38ca-11eb-8e58-bcecd1759f08.png>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#351 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB346VHO4WLEVBFXAZOPRP3STV6MXANCNFSM4UBPKTNQ>
.
|
It would be great to see more of the logs, before you get opcode 2 errors to verify that disgord detects the resume condition. There should be a message with "might try to resume. Increase timeout by". Can you please provide that section of the logs? |
I haven't been using the logger, i'll enable it and supply you with more robust logs when it occurs again, sorry I should have done that before commenting again, my apologies! |
So the picture you linked is not from the v0.22 instance? If you have to restart it, can you also upgrade to disgord v0.23.1 =) |
it is |
yes, i'll update, enable logger and report back as soon as it happens |
If you're able to it would be great if you could store debug logs. Note that there's going to be a lot of stuff so it should be stored in a file. |
I closed this because I'm unable to reproduce it. |
Lies |
Describe the bug
Every so often during music playback it appears the websocket connection gets interrupted
Expected behavior
For the websocket connection to successfully reconnect on heartbeat
Error messages
The text was updated successfully, but these errors were encountered: