[MDEV-16893] TokuDB doesn't start after installation on CentOS 7.3 Created: 2018-08-03  Updated: 2023-04-27

Status: Stalled
Project: MariaDB Server
Component/s: Storage Engine - TokuDB
Affects Version/s: 10.3
Fix Version/s: 10.4

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by MDEV-14560 Extra engines enabled through additio... Closed

 Description    

Aug  3 13:02:53 centos73-amd64 mysqld: 2018-08-03 13:02:53 0 [Note] /usr/sbin/mysqld (mysqld 10.3.8-MariaDB) starting as process 2670 ...
 
Aug  3 13:02:53 centos73-amd64 mysqld: 2018-08-03 13:02:53 0 [ERROR] TokuDB is not initialized because jemalloc is not loaded
 
Aug  3 13:02:53 centos73-amd64 mysqld: 2018-08-03 13:02:53 0 [ERROR] Plugin 'TokuDB' init function returned error.
 
Aug  3 13:02:53 centos73-amd64 mysqld: 2018-08-03 13:02:53 0 [ERROR] Plugin 'TokuDB' registration as a STORAGE ENGINE failed.



 Comments   
Comment by Elena Stepanova [ 2018-08-03 ]

serg, FYI. It seems it happens in buildbot as well (or something else happens that prevents TokuDB from starting), it's not caught by upgrade tests because they only check that nothing disappeared after upgrade, but if both old and new version have the same problem, they won't notice.

Comment by Sergei Golubchik [ 2018-08-06 ] 

Aug 05 15:35:20 centos73-amd64 mysqld[2786]: 2018-08-05 15:35:20 0 [ERROR] TokuDB is not initialized because jemalloc is not loaded
 
Aug 05 15:35:20 centos73-amd64 mysqld[2786]: 2018-08-05 15:35:20 0 [ERROR] Plugin 'TokuDB' init function returned error.
 
Aug 05 15:35:20 centos73-amd64 mysqld[2786]: 2018-08-05 15:35:20 0 [ERROR] Plugin 'TokuDB' registration as a STORAGE ENGINE failed.

Comment by Sergei Golubchik [ 2018-08-09 ]

The log also contains

mariadb.service changed on disk. Run 'systemctl daemon-reload' to reload units.

If I do that, TokuDB starts just fine.
I expect that after MDEV-14560 one wouldn't need to do daemon-reload manually anymore.

Generated at Thu Feb 08 08:32:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.