0

I have set up a master and a slave for MariaDB using the Bitnami docker image. The replication seems going smoothly:

MariaDB [(none)]> show processlist;
+-----+-------------+--------------------+------+-------------+------+-----------------------------------------------------------------------+------------------+----------+
| Id  | User        | Host               | db   | Command     | Time | State                                                                 | Info             | Progress |
+-----+-------------+--------------------+------+-------------+------+-----------------------------------------------------------------------+------------------+----------+
|   1 | system user |                    | NULL | Daemon      | NULL | InnoDB purge coordinator                                              | NULL             |    0.000 |
|   2 | system user |                    | NULL | Daemon      | NULL | InnoDB purge worker                                                   | NULL             |    0.000 |
|   3 | system user |                    | NULL | Daemon      | NULL | InnoDB purge worker                                                   | NULL             |    0.000 |
|   4 | system user |                    | NULL | Daemon      | NULL | InnoDB purge worker                                                   | NULL             |    0.000 |
|   5 | system user |                    | NULL | Daemon      | NULL | InnoDB shutdown handler                                               | NULL             |    0.000 |
| 359 | replicator  | 172.24.19.73:60192 | NULL | Binlog Dump | 1119 | Master has sent all binlog to slave; waiting for binlog to be updated | NULL             |    0.000 |
| 362 | root        | localhost          | NULL | Query       |    0 | Init                                                                  | show processlist |    0.000 |
+-----+-------------+--------------------+------+-------------+------+-----------------------------------------------------------------------+------------------+----------+

And the slave does not report any error:


Welcome to the Bitnami mariadb container
Subscribe to project updates by watching https://github.com/bitnami/bitnami-docker-mariadb
Submit issues and feature requests at https://github.com/bitnami/bitnami-docker-mariadb/issues
Send us your feedback at containers@bitnami.com

INFO  ==> ** Starting MariaDB setup **
INFO  ==> Validating settings in MYSQL_*/MARIADB_* env vars..
INFO  ==> Initializing mariadb database...
INFO  ==> Persisted data detected. Restoring...
INFO  ==> Stopping mariadb...
INFO  ==> ** MariaDB setup finished! **

INFO  ==> ** Starting MariaDB **
2019-09-26  4:20:36 0 [Note] /opt/bitnami/mariadb/sbin/mysqld (mysqld 10.3.15-MariaDB-log) starting as process 1 ...
2019-09-26  4:20:36 0 [Note] InnoDB: Using Linux native AIO
2019-09-26  4:20:36 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-09-26  4:20:36 0 [Note] InnoDB: Uses event mutexes
2019-09-26  4:20:36 0 [Note] InnoDB: Compressed tables use zlib 1.2.8
2019-09-26  4:20:36 0 [Note] InnoDB: Number of pools: 1
2019-09-26  4:20:36 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-09-26  4:20:36 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2019-09-26  4:20:36 0 [Note] InnoDB: Completed initialization of buffer pool
2019-09-26  4:20:36 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-09-26  4:20:36 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-09-26  4:20:36 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-09-26  4:20:36 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-09-26  4:20:36 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2019-09-26  4:20:36 0 [Note] InnoDB: Waiting for purge to start
2019-09-26  4:20:36 0 [Note] InnoDB: 10.3.15 started; log sequence number 205311828; transaction id 112877
2019-09-26  4:20:36 0 [Note] InnoDB: Loading buffer pool(s) from /bitnami/mariadb/data/ib_buffer_pool
2019-09-26  4:20:36 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-09-26  4:20:36 0 [Note] Server socket created on IP: '0.0.0.0'.
2019-09-26  4:20:36 0 [Warning] 'proxies_priv' entry '@% root@nextcloud-mariadb-slave-0' ignored in --skip-name-resolve mode.
2019-09-26  4:20:36 0 [Note] Reading of all Master_info entries succeded
2019-09-26  4:20:36 0 [Note] Added new Master_info '' to hash table
2019-09-26  4:20:36 10 [Note] Slave I/O thread: Start asynchronous replication to master 'replicator@nextcloud-mariadb:3306' in log 'mysql-bin.000296' at position 304069
2019-09-26  4:20:36 0 [Note] /opt/bitnami/mariadb/sbin/mysqld: ready for connections.
Version: '10.3.15-MariaDB-log'  socket: '/opt/bitnami/mariadb/tmp/mysql.sock'  port: 3306  Source distribution
2019-09-26  4:20:36 11 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000296' at position 304069, relay log './mysql-relay-bin.000312' position: 293910
2019-09-26  4:20:36 10 [Note] Slave I/O thread: connected to master 'replicator@nextcloud-mariadb:3306',replication started in log 'mysql-bin.000296' at position 304069
2019-09-26  4:20:37 0 [Note] InnoDB: Buffer pool(s) load completed at 190926  4:20:37

However I couldn't login into the slave server as root using the same password with which I've successfully authenticated against the master server:

[root@master ~]$ kubectl exec -it nextcloud-mariadb-slave-0 -- mysql -u root -p
Enter password:
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
command terminated with exit code 1

I also tried to remove the data directory on the slave and restarted the replication, but the problem persists. Any suggestions? Thank you!

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.