How do you undo replication on the master database

This is my first attempt to configure a master database for replication. I added the following information to the my.cnf file... [mariadb] log-bin server_id=1 log-basename=master1

Then restarted mysql with the command "service mysql restart". The restart failed with several errors pointing to the InnoDB. I restored the original version of the my.cnf file and restarted mysql. Again the restart failed with the following:

mariadb.service - MariaDB 10.1.38 database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled) Drop-In: /etc/systemd/system/mariadb.service.d └─migrated-from-my.cnf-settings.conf Active: failed (Result: exit-code) since Sun 2019-02-10 23:15:43 EST; 3min 0s ago Docs: man:mysqld(8) https://mariadb.com/kb/en/library/systemd/ Process: 10011 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE) Process: 9795 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS) Process: 9539 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Main PID: 10011 (code=exited, status=1/FAILURE) Status: "MariaDB server is down"

Feb 10 23:15:43 data01 mysqld[10011]: 2019-02-10 23:15:43 140315067881728 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data! Feb 10 23:15:43 data01 mysqld[10011]: 2019-02-10 23:15:43 140315067881728 [ERROR] Plugin 'InnoDB' init function returned error. Feb 10 23:15:43 data01 mysqld[10011]: 2019-02-10 23:15:43 140315067881728 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. Feb 10 23:15:43 data01 mysqld[10011]: 2019-02-10 23:15:43 140315067881728 [Note] Plugin 'FEEDBACK' is disabled. Feb 10 23:15:43 data01 mysqld[10011]: 2019-02-10 23:15:43 140315067881728 [ERROR] Unknown/unsupported storage engine: InnoDB Feb 10 23:15:43 data01 mysqld[10011]: 2019-02-10 23:15:43 140315067881728 [ERROR] Aborting Feb 10 23:15:43 data01 systemd[1]: mariadb.service: main process exited, code=exited, status=1/FAILURE Feb 10 23:15:43 data01 systemd[1]: Failed to start MariaDB 10.1.38 database server. Feb 10 23:15:43 data01 systemd[1]: Unit mariadb.service entered failed state. Feb 10 23:15:43 data01 systemd[1]: mariadb.service failed.

Any help on how I can resolve this is greatly appreciated...

Thanks, Mike

Answer Answered by Mike Clarke in this comment.

This problem has been resolved. There were a number of new files created (included above) as a result of updating the my.cnf file with this info "[mariadb] log-bin server_id=1 log-basename=master1". All newly created files were removed and mysql restarted.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.