MariaDB Triage Document

MariaDB Triage Document

The Triage document is the first point of call when troubleshooting MariaDB issues.

A related document called MariaDB extended is the same document with an in-depth explanation.

####### Mariadb online checks #########

Elavate to root

sudo su

Check Mariadb is running

ps –ef | grep mysqld

Disk I/O status

iostat –x 5

Verify Connection to Master

netstat –a

Login to MariaDB

mysql

Check Replication status

SHOW SLAVE STATUS\G

Check mariaDB uptime

SHOW GLOBAL STATUS LIKE 'uptime';

List Long running Process

SHOW PROCESSLIST\G

Check status of INNODB

SHOW ENGINE INNODB SATUS \G

Check all Engine Status

SHOW ENGINES\G

Check Warning Errors

SHOW WARNINGS;

SHOW WARNINGS\G

Check SQL Mode

SELECT @@sql_mode;

To exit mariadb

Exit

######### MariaDB offline checks  #################

Check error logs

journalctl -xeu mariadb.service

systemctl status mariadb.service

Check Stop start Mariadb

systemctl status mariadb.service

systemctl stop mariadb.service

systemctl start mariadb.service

Check Configaration

cat /etc/my.cnf

cat /etc/my.cnf.d/mariadb-server.cnf

#### Missing Drives  ###############

cat /etc/fstab

sudo mount -a

#### MariaDB replication communication failed check #######

Firwal configaration

sudo firewall-cmd --zone=public --add-port=3306/tcp --permanent

sudo firewall-cmd --zone=public --add-port=4567/tcp --permanent

sudo firewall-cmd --reload

Issue: Slave_IO_State: Reconnecting after a failed master event read

 It may happen when Master was not up at the time when Slave tried to connect.

You may ignore it and just wait. Make sure that both of them are up.

To force reconnection use:

Stop slave;

Start slave;

If you need more information go check file:

less /var/lib/mysql/<hostname>.err

and you may find usefull:

less /var/log/messages