> give me this is the error.log after restart the mariadb with sudo systemctl restart mariadb.service
There are NO error logs as the mariadb does start well without any errors. So you mean that when you restart the replica (slave) server, it automatically tries to resume replication and connects to the primary (master) server, but fails to connect, and thus the error message? Connection and replication are ok but one one way. About the GRANT's: I tested several versions of the MariaDB and discovered all kind of flaws, now have version 12 latest and replication works with only replication as GRANT, for all the other ones I needed to add the mentioned GRANTS The intention is, as put in the BUG description, that two different databases will be mirrored. Those two different databases are NOT on the same master, but one on e the master and one on the slave. Master and slave is not the correct way to describe it as both are master for one database For this I wanted to use semi synchronous replication see link https://mariadb.com/docs/server/ha-and-performance/standard-replication/semisynchronous-replication I thought that this way I could reach my goal, but in practice only one database (from VM1 to VM2) could be mirrored As I thought this is a bug I reported this. If you know a way to solve my issue I am happy to hear your suggestion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2127679 Title: Internal MariaDB error code: 1045 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb/+bug/2127679/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
