[MDEV-29797] ERROR 1286 (42000): Unknown storage engine 'InnoDB' Created: 2022-10-14  Updated: 2022-10-15  Resolved: 2022-10-14

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: None
Fix Version/s: N/A

Type: Bug Priority: Trivial
Reporter: thejaraj Assignee: Unassigned
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

Server version: 10.1.14-MariaDB MariaDB Server



 Description   

Team, after changing the below parameter in my.cnf, i'm facing below datafiles issues, kindl help me on furtter to fix the issue, if the parameter is disalbe, mariad db instance is not starting

default-storage-engine=MyISAM

MariaDB [zabbix]> select count(1) from triggers;
ERROR 1286 (42000): Unknown storage engine 'InnoDB'
MariaDB [zabbix]>

2022-10-14 17:00:50 140269606017216 [Note] InnoDB: Unable to open the first data file
2022-10-14 17:00:50 7f93100a18c0 InnoDB: Operating system error number 11 in a file operation.
InnoDB: Error number 11 means 'Resource temporarily unavailable'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2022-10-14 17:00:50 140269606017216 [ERROR] InnoDB: Can't open './ibdata1'
2022-10-14 17:00:50 140269606017216 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2022-10-14 17:00:50 140269606017216 [ERROR] Plugin 'InnoDB' init function returned error.
2022-10-14 17:00:50 140269606017216 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-10-14 17:00:50 140269606017216 [Note] Plugin 'FEEDBACK' is disabled.
2022-10-14 17:00:50 140269606017216 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as mysqld was configured with --with-aria-tmp-tables
2022-10-14 17:00:50 140269606017216 [ERROR] Aborting



 Comments   
Comment by Daniel Black [ 2022-10-14 ]

A mariadb instance is already running so the second instance is prevented from starting.

10.1 is out of maintenance. As a bug tracker this is for bugs in MariaDB.

Use https://mariadb.com/kb/en/getting-help-with-mariadb/ for getting help.

Generated at Thu Feb 08 10:11:22 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.