The Ultimate Guide to High Availability with MariaDB

Problem starting DB

You are viewing an old version of this question. View the current version here.

● mariadb.service - MariaDB 10.1.38 database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/mariadb.service.d └─migrated-from-my.cnf-settings.conf Active: failed (Result: exit-code) since Fri 2019-04-19 16:47:11 CDT; 39min ago Docs: man:mysqld(8) https://mariadb.com/kb/en/library/systemd/ Process: 1533 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE) Process: 1157 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set- Process: 1147 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 1133 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS) Main PID: 1533 (code=exited, status=1/FAILURE) Status: "MariaDB server is down"

Apr 19 16:47:09 pan-expedition mysqld[1533]: 2019-04-19 16:47:09 140388826417408 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.42-84.2 st Apr 19 16:47:09 pan-expedition mysqld[1533]: 2019-04-19 16:47:09 140387863750400 [Note] InnoDB: Dumping buffer pool(s) not yet started Apr 19 16:47:09 pan-expedition mysqld[1533]: 2019-04-19 16:47:09 140388826417408 [Note] Plugin 'FEEDBACK' is disabled. Apr 19 16:47:09 pan-expedition mysqld[1533]: 2019-04-19 16:47:09 140388826417408 [Note] Recovering after a crash using tc.log Apr 19 16:47:09 pan-expedition mysqld[1533]: 2019-04-19 16:47:09 140388826417408 [ERROR] Can't init tc log Apr 19 16:47:09 pan-expedition mysqld[1533]: 2019-04-19 16:47:09 140388826417408 [ERROR] Aborting Apr 19 16:47:11 pan-expedition systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Apr 19 16:47:11 pan-expedition systemd[1]: Failed to start MariaDB 10.1.38 database server. Apr 19 16:47:11 pan-expedition systemd[1]: mariadb.service: Unit entered failed state. Apr 19 16:47:11 pan-expedition systemd[1]: mariadb.service: Failed with result 'exit-code'. ~ ~ ~

Answer Answered by Ian Gilfillan in this comment.

You need to give more details about why there could be a crash. Corrupt data? An upgrade not completed properly?

2019-04-19 16:47:09 140388826417408 [Note] Recovering after a crash using tc.log

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.