hopefully you did run mysql_upgrade first on the slave as all docs in that
context saying and after that on the master
Cool!! Yeah, running mysql_upgrade did the trick. After I performed that on
the slave, that error went away. I actually did the same on both nodes
figuring it would be best to
Am 22.07.2015 um 06:39 schrieb Tim Dunphy:
Hey guys,
I'm trying to setup multi master replication using SSL under MariaDB 10.20.
I've been able to specify my client certs on the second node (db2) with no
issue and start up the mysql service
what about running mysql_upgrade *directly* after
Am 22.07.2015 um 16:24 schrieb Tim Dunphy:
Hi Reindl,
what about running mysql_upgrade *directly* after the major update
and *before* touch anything else?
That was precisely what happened. In setting up the new database
machine, puppet had installed version 5 of mariadb. Before even
Hi Reindl,
what about running mysql_upgrade *directly* after the major update and
*before* touch anything else?
That was precisely what happened. In setting up the new database machine,
puppet had installed version 5 of mariadb. Before even starting up version
of for the first time, I
Hey guys,
I'm trying to setup multi master replication using SSL under MariaDB 10.20.
I've been able to specify my client certs on the second node (db2) with no
issue and start up the mysql service.
But for some reason when I do the same on the first node (db1) the mysql
service takes a really
