15, MARIADB work encountered a part of the resolution method of the error

MARIADB Error Resolution method

1) service does not come up or can not be added into the cluster

Act 1:

RM-RF Mysql.sock

RM-RF Galera.cache

RM-RF Mariadb.pid

Rm-rf/var/lock/subsys/mysql

Act 2:

Put/etc/my.cnf/server.cn

Fully annotate the cluster configuration, start a standalone service, then shut down the service, add the cluster configuration, and start the service

Note: If you do not join the cluster problem, do not delete the cluster file

2) Table '. \mysql\proc ' is marked as crashed and should be repaired error

Workaround:

Locate the Bin/myisamchk tool for the MySQL installation directory and enter it at the command line:

Myisamchk-c-r/var/lib/mysql/mysql/proc. MYI

Then the Myisamchk tool will help you recover the index of the data table. Restart MySQL for problem resolution.

3) [ERROR] Found 1 prepared transactions! It means that mysqld is not shut down properly last time and critical recovery inform

ation (last Binlog or Tc.log file) is manually deleted after a crash. You has to start mysqld with--tc-heuristic-recover switch to commit

or rollback pending transactions.

160107 16:10:46 [ERROR] Aborting

Workaround

Service MySQL start--tc-heuristic-recover=rollback

4) 4160107 16:23:41 [ERROR] wsrep:gcs/src/gcs_core.cpp:long int Gcs_core_open (gcs_core_t*, const char*, const char*, BOOL ) (): 206:failed to open

Backend Connection: -98 (Address already in use)

Workaround, reinitialize this one and put

wsrep_cluster_address= IP re-emptying after "gcomm://"

5) 160106 0:42:48 [Note] Innodb:shutdown completed; Log sequence Number 1617594

160106 0:42:48 [Note]/usr/sbin/mysqld:shutdown complete

Workaround: 1, check that there are no 3306 ports or the MySQL service has started to occupy the port

2. Turn off firewall and SELinux

6) Note: MARIADBR synchronization mode has two kinds of mysqldump, rsync, it is recommended to choose the synchronization mode of rsync

Mysqldump synchronization method as long as there is a database in front of the bad, I can't even, then even if the database is repaired, I connect he will report no permissions and can never sync

Rsync synchronization mode connection regardless of the database is not bad, I am based on SSH synchronization, as long as SSH opened, all installed rsync, and so on the front database well, synchronization in the past there will be no problem

This article is from the "Wsyht blog" blog, make sure to keep this source http://wsyht2015.blog.51cto.com/9014030/1789160

15, MARIADB work encountered a part of the resolution method of the error