Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconnect on Fatal Error #125

Open
Fabbok1x opened this issue Apr 17, 2020 · 1 comment
Open

Reconnect on Fatal Error #125

Fabbok1x opened this issue Apr 17, 2020 · 1 comment

Comments

@Fabbok1x
Copy link

Hey,
just wondering if it was possible to recover from a fatal error such as Packet was received in wrong sequence / Same slave already existing?
Currently it seems to stop as a whole once a fatal error has been thrown.
Anything to attempt a reconnection would be greatly appreciated.

Regards

@vasyas
Copy link

vasyas commented Sep 14, 2020

Need this very bad. Any known possible workarounds?

If not, any clues where to start to fix it?

P.S. Getting this sometimes on MySQL 8 on Amazon RDS:

Error: Cannot enqueue Query after fatal error.
    at Protocol._validateEnqueue (/home/server/server/shared-server/node_modules/mysql/lib/protocol/Protocol.js:212:16)
    at Protocol._enqueue (/home/server/server/shared-server/node_modules/mysql/lib/protocol/Protocol.js:138:13)
    at Connection.query (/home/server/server/shared-server/node_modules/mysql/lib/Connection.js:201:25)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants