Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
10.2.28, 10.1.42
-
None
-
CentOS Linux 7.7.1908
Description
Hi,
I have many server running MariaDB 10.1.x and 10.2.x
They have all stopped working after the latest update from 10.1.41 to 10.1.42 and 10.2.27 to 10.2.28
Error message as below, systemctl status mariadb.service
● mariadb.service - MariaDB 10.2.28 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
/usr/lib/systemd/system/mariadb.service.d
└─respawn.conf
Active: activating (auto-restart) (Result: signal) since Wed 2019-11-06 07:02:01 UTC; 4s ago
Docs: man:mysqld(8)
https://mariadb.com/kb/en/library/systemd/
Process: 5831 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS --basedir=/usr $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=killed, signal=ABRT)
Process: 5800 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: 5798 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Main PID: 5831 (code=killed, signal=ABRT)
Nov 06 07:02:01 xxxx.xxxx.xyz systemd[1]: Failed to start MariaDB 10.2.28 database server.
Nov 06 07:02:01 xxxx.xxxx.xyz systemd[1]: Unit mariadb.service entered failed state.
Nov 06 07:02:01 xxxx.xxxx.xyz systemd[1]: mariadb.service failed.
Attachments
Issue Links
- relates to
-
MDEV-20987 InnoDB fails to start when fts table has FK relation
- Closed