The Ultimate Guide to High Availability with MariaDB

Comments - Process: 1037 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)

2 years, 2 months ago Daniel Black
Re: Process: 1037 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE) [Answer]

Hi,

This looks like a bug and not one we've encountered before.

Can you please report a new bug on https://jira.mariadb.org? If you are willing to share the database contents you can do a private upload to https://mariadb.com/kb/en/meta/mariadb-ftp-server/.

Its failing during crash recovery however what would be useful is the original cause of the crash. This will be further back in the logs and including it in the bug report would be useful. This will be the MariaDB start up that doesn't include "Starting crash recovery"which will continue to a shutdown that doesn't say '[ERROR] Plugin 'InnoDB' init function returned error".

For your recovery I can't offer a suggestion beyond restore from backup.

 
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.