[MDEV-21548] [ERROR] Aria engine is not enabled or did not start Created: 2020-01-21  Updated: 2022-02-22  Resolved: 2020-01-21

Status: Closed
Project: MariaDB Server
Component/s: Server, Storage Engine - Aria
Affects Version/s: 10.5.0
Fix Version/s: 10.5.1

Type: Bug Priority: Critical
Reporter: Michal Schorm Assignee: Vladislav Vaintroub
Resolution: Fixed Votes: 0
Labels: None
Environment:

Fedora Rawhide

Attachments: File build.log    
Issue Links:
Relates
relates to MDEV-27918 Enabling shared libs breaks build on ... Closed
relates to MDEV-27826 Mariabackup is linked against libsql_... Closed

 Description   

Hello,
Fedora maintainer of MariaDB & MySQL packages here.

As a part of an early feedback, I tried to pack the MariaDB 10.5.0-Alpha, to check for possible issues.
The build seems OK.
After I also packed the new shared dynamic library 'libsql_builtins', I was able to install the produced RPM packages too.

However, I can't start the server beacuse of the Aria error.
It's not just the produced packages, later installed on a test machine though, when I tried to run the testsuite during the build, every test failed with the same error.

In short, the error (in the error log) is:

2020-01-21 10:53:21 0 [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
 
2020-01-21 10:53:21 0 [ERROR] Aborting

I tried some tips in the internet - like deleting the old aria log files and the 'aria_log_control' file, however it didn't help.

When I run the first 'systemctl start mariadb' ( = the datadir and logdir are both empty at that moment), the service will fail with:

...
 
mysql-prepare-db-dir[25044]: Installation of system tables failed!  Examine the logs in ...
 
...
 
{code:bash}
 
And the error log (configured with 'log_warnings=9') holds:
 
{code:bash}
 
2020-01-21 11:06:03 0 [Warning] You need to use --log-bin to make --binlog-format work.
 
ERROR: 1932  Table 'information_schema.(temporary)' doesn't exist in engine
 
2020-01-21 11:06:04 0 [ERROR] Aborting

On the second run ('systemctl start mariadb' again), the result is different.
Journal says:

systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE

and in the error log was added following:

2020-01-21 11:06:54 0 [Warning] You need to use --log-bin to make --binlog-format work.
 
2020-01-21 11:06:54 0 [Note] Initializing built-in plugins
 
2020-01-21 11:06:54 0 [Note] Initializing plugins specified on the command line
 
2020-01-21 11:06:54 0 [Note] Loaded 'ha_connect.so' with offset 0x7f7a2424a000
 
2020-01-21 11:06:54 0 [Note] Loaded 'ha_oqgraph.so' with offset 0x7f7a24212000
 
2020-01-21 11:06:54 0 [Note] Loaded 'ha_rocksdb.so' with offset 0x7f7a10d89000
 
2020-01-21 11:06:54 0 [Note] Loaded 'ha_tokudb.so' with offset 0x7f7a10bd0000
 
2020-01-21 11:06:54 0 [Note] RocksDB: 2 column families found
 
2020-01-21 11:06:54 0 [Note] RocksDB: Column Families at start:
 
2020-01-21 11:06:54 0 [Note]   cf=default
 
2020-01-21 11:06:54 0 [Note]     write_buffer_size=67108864
 
2020-01-21 11:06:54 0 [Note]     target_file_size_base=67108864
 
2020-01-21 11:06:54 0 [Note]   cf=__system__
 
2020-01-21 11:06:54 0 [Note]     write_buffer_size=67108864
 
2020-01-21 11:06:54 0 [Note]     target_file_size_base=67108864
 
2020-01-21 11:06:54 0 [Note] RocksDB: Table_store: loaded DDL data for 0 tables
 
2020-01-21 11:06:54 0 [Note] RocksDB: global statistics using get_sched_indexer_t indexer
 
2020-01-21 11:06:54 0 [Note] MyRocks storage engine plugin has been successfully initialized.
 
2020-01-21 11:06:54 0 [Note] InnoDB: Using Linux native AIO
 
2020-01-21 11:06:54 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
 
2020-01-21 11:06:54 0 [Note] InnoDB: Uses event mutexes
 
2020-01-21 11:06:54 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
 
2020-01-21 11:06:54 0 [Note] InnoDB: Number of pools: 1
 
2020-01-21 11:06:54 0 [Note] InnoDB: Using SSE2 crc32 instructions
 
2020-01-21 11:06:54 0 [Note] mysqld: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
 
2020-01-21 11:06:54 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
 
2020-01-21 11:06:54 0 [Note] InnoDB: Completed initialization of buffer pool
 
2020-01-21 11:06:54 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
 
2020-01-21 11:06:54 0 [Note] InnoDB: 128 rollback segments are active.
 
2020-01-21 11:06:54 0 [Note] InnoDB: Creating shared tablespace for temporary tables
 
2020-01-21 11:06:54 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
 
2020-01-21 11:06:54 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
 
2020-01-21 11:06:54 0 [Note] InnoDB: 10.5.0 started; log sequence number 61420; transaction id 21
 
2020-01-21 11:06:54 0 [Note] CONNECT: Version 1.06.0010 June 01, 2019
 
2020-01-21 11:06:54 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
 
2020-01-21 11:06:54 0 [Note] InnoDB: Buffer pool(s) load completed at 200121 11:06:54
 
2020-01-21 11:06:54 0 [Note] Plugin 'FEEDBACK' is disabled.
 
2020-01-21 11:06:54 0 [Note] Initializing installed plugins
 
2020-01-21 11:06:54 0 [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
 
2020-01-21 11:06:54 0 [ERROR] Aborting

Everything seems fine to me there, until the Aria problem.

—

Maybe you can spot something usefull in the build.log

—

I wanted to compare my RPMs to your RPMs, but the list you have is incomplete for F31
http://sgp1.mirrors.digitalocean.com/mariadb//mariadb-10.5.0/yum/fedora31-amd64/
I will examine the F30 RPMs instead.

 Comments   
Comment by Sergei Golubchik [ 2020-01-21 ]

it's probably related to the "new shared dynamic library libsql_builtins" that you've mentioned. I don't think there should be a new dynamic library. Looking at the code I believe it's supposed to be static and it was introduced purely as an internal build optimization, not to have a new user visible entity. Aria is part of that library and, supposedly that's why you're getting an error.

And it's caused by your -DBUILD_SHARED_LIBS:BOOL=ON. I don't think it should affect libsql_builtins.

Comment by Michal Schorm [ 2020-01-22 ]

I confirm that this simple patch solved the issue.

MariaDB 10.5.0 now can be build on all Fedora primary architectures, RPMs can be installed and ran, testsuite passes in a usual range.

Generated at Thu Feb 08 09:07:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.