Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-16893

TokuDB doesn't start after installation on CentOS 7.3

Details

    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.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14560 Extra engines enabled through additional config are not loaded on first installation

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            elenst Elena Stepanova added a comment -

            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.

            elenst Elena Stepanova added a comment - 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.
            serg Sergei Golubchik added a comment - 

            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.

            serg Sergei Golubchik added a comment - 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.
            serg Sergei Golubchik added a comment -

            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.

            serg Sergei Golubchik added a comment - 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.

            People

              serg Sergei Golubchik
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.