Percona won't start, error message is cryptic: ([ERROR] Aborting)

I’ve got percona installed on a box and I’m using a custom config from https://tools.percona.com/. The mysql_install_db went fine and it appears that all of the necessary files were created, but the server fails to start with the following error:

[ERROR] Aborting

Not much to go on.

This is the initial startup after mysql_install_db:

120411 12:43:18 [Note] Plugin ‘FEDERATED’ is disabled.120411 12:43:18 InnoDB: The InnoDB memory heap is disabled120411 12:43:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins120411 12:43:18 InnoDB: Compressed tables use zlib 1.2.3120411 12:43:18 InnoDB: Using Linux native AIO120411 12:43:18 InnoDB: Initializing buffer pool, size = 2.0G120411 12:43:18 InnoDB: Completed initialization of buffer poolInnoDB: The first specified data file ./ibdata1 did not exist:InnoDB: a new database to be created!120411 12:43:18 InnoDB: Setting file ./ibdata1 size to 10 MBInnoDB: Database physically writes the file full: wait…120411 12:43:18 InnoDB: Log file ./ib_logfile0 did not exist: new to be createdInnoDB: Setting log file ./ib_logfile0 size to 128 MBInnoDB: Database physically writes the file full: wait…InnoDB: Progress in MB: 100120411 12:43:20 InnoDB: Log file ./ib_logfile1 did not exist: new to be createdInnoDB: Setting log file ./ib_logfile1 size to 128 MBInnoDB: Database physically writes the file full: wait…InnoDB: Progress in MB: 100InnoDB: Doublewrite buffer not found: creating newInnoDB: Doublewrite buffer createdInnoDB: 127 rollback segment(s) active.InnoDB: Creating foreign key constraint system tablesInnoDB: Foreign key constraint system tables created120411 12:43:21 InnoDB: Waiting for the background threads to start120411 12:43:22 Percona XtraDB (http://www.percona.com) 1.1.8-rel25.0 started; log sequence number 0120411 12:43:22 [ERROR] Aborting120411 12:43:22 InnoDB: Starting shutdown…120411 12:43:26 InnoDB: Shutdown completed; log sequence number 1597945120411 12:43:26 [Note]

This is a subsequent restart:

120411 12:48:17 [Note] Plugin ‘FEDERATED’ is disabled.120411 12:48:17 InnoDB: The InnoDB memory heap is disabled120411 12:48:17 InnoDB: Mutexes and rw_locks use GCC atomic builtins120411 12:48:17 InnoDB: Compressed tables use zlib 1.2.3120411 12:48:17 InnoDB: Using Linux native AIO120411 12:48:17 InnoDB: Initializing buffer pool, size = 2.0G120411 12:48:17 InnoDB: Completed initialization of buffer pool120411 12:48:17 InnoDB: highest supported file format is Barracuda.120411 12:48:17 Percona XtraDB (http://www.percona.com) 1.1.8-rel25.0 started; log sequence number 1597945120411 12:48:17 [ERROR] Aborting120411 12:48:17 InnoDB: Starting shutdown…120411 12:48:23 InnoDB: Shutdown completed; log sequence number 1597945120411 12:48:23 [Note]

Anyone have any thoughts as to what might be going on?

Thanks much for any suggestions.

Ok, I was able to figure this out through a little blind luck. I saw someone ask the almost exact same question I asked in a different forum. His output included:

[ERROR] Can’t find messagefile ‘/usr/share/errmsg.sys’

Which made me think about using this config from tools.percona.com. There is no language file specified in the config from percona, which is most likely why the error output was garbage.

Yes. In general if the system has been packaged in such a way that the defaults are not in use, then it is possible that there are some settings in the existing my.cnf file that will need to be merged into the new configuration file. I do plan to address this in the future by allowing you to input your existing configuration and having the tool help you merge the new and old ones together.