-
Notifications
You must be signed in to change notification settings - Fork 53
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
Error: A slave with the same server_uuid/server_id as this slave has connected to the master; #21
Comments
This is probably a MySQL error related to the binlog state. I don't think it will stop the app from working properly tho. |
Yes, I think is working ok.
I am restarting the app every day …
So not sure ...
… On 29 Aug 2019, at 19:44, Rodrigo Gomes da Silva ***@***.***> wrote:
This is probably a MySQL error related to the binlog state. I don't think it will stop the app from working properly tho.
Do you think you missed any event due to this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#21?email_source=notifications&email_token=AAYZAHWMO3X63V6BYOBOGBLQHADI5A5CNFSM4ISBEJI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5PIZ2Y#issuecomment-526290155>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAYZAHQZR2XFM7MU4R3O3CLQHADI5ANCNFSM4ISBEJIQ>.
|
Same problem for me. |
Yes. I need to start more than every day and found another way to do what I need it. So for the moment not using sqlevents |
In my case, the error occurred when I restart the triggers (your "startTrigers" function). For a moment it creates a conflict with the precendet instance (or something of similar...). But the real problem is the disconnection from the server that, in my case, happens every 8 hours (my server is an amazonAWS one). If I force to restart the entire script, when an CONNECTION_ERROR occurred, I don't get the topic error. So I belive it's a instances problem. I recreate a new MySQLEvents instance too. |
Sorry for not being able to help. I'm deeply involved in some COVID-19 urgent projects and it's sucking my time to the bone. |
Hopefully someone has a solution, otherwise this library is useless after the first time it disconnects. Looks like the control connection gets disconnected after the wait_timeout but the binlog connection remains. Try to pass it a new connection as above returns the "slave with same server_id" error. |
You can try to force the instance to stop before restart the connection.
This is my code and I don't get the topic error anymore.
|
Unfortunately, I've not managed to get instance.stop() to work in any iteration, I always end up with 'UnhandledPromiseRejectionWarning: Error: Cannot enqueue Quit after fatal error.' |
please don't flame me, i'm really new with nodejs, i don't know exactly what i'm doing.
is this totally wrong? |
Hi, I have this error before, my environment was a master and some slave database, there is replication from slave-db to master-db and if I using mysql-events plugin to connect from another vm, it get error (A slave with the same server_uuid/server_id as this slave has connected....) |
Hi @rodrigogs,
Has been working great!
But looking at the log error I saw a new one:
I have 2 databases (Production, Development )
And have 2 listeners that gives this error
My Code Dev
My Code Prod
Same code for both
Do I have to change something?
The text was updated successfully, but these errors were encountered: