Details

    Description

      Hello,

      The Connect SE plugin can't be used after compilation.

      Previous 10.3 & 10.4 versions are not affected. The issue must have been introduced in those affected versions.

      Sample from the error log:
      (configured via config file with "log_warnings=9" and "plugin_load_add=ha_connect")

      [ERROR] mysqld: Can't open shared library '/usr/lib64/mariadb/plugin/ha_connect.so' (errno: 22, undefined symbol: _ZN6XMLDEFC1Ev)
      [ERROR] Couldn't load plugins from 'ha_connect.so'.
      [ERROR] mysqld: Can't open shared library '/usr/lib64/mariadb/plugin/ha_connect.so' (errno: 0, undefined symbol: _ZN6XMLDEFC1Ev)
      [ERROR] Couldn't load plugins from 'ha_connect.so'.
      [Note] Initializing built-in plugins
      [Note] Initializing plugins specified on the command line
      [ERROR] mysqld: Can't open shared library '/usr/lib64/mariadb/plugin/ha_connect.so' (errno: 22, undefined symbol: _ZN6XMLDEFC1Ev)
      [ERROR] Couldn't load plugins from 'ha_connect.so'.
      

      Result after running "mysql"

      # mysql
      mysql: unknown variable 'plugin_load_add=ha_connect'
      

      Also, the whole Connect testsuite fail on all affected versions:
      https://jira.mariadb.org/browse/MDEV-19786

      I won't introduce the new versions to Fedora without a fix.

      Attachments

        Activity

          mschorm Michal Schorm added a comment - May https://github.com/MariaDB/server/commit/7a9eca1191 or more likely https://github.com/MariaDB/server/commit/2cb4b152c8 be the cause?

          Are you compiling MariaDB from source? There seem to be a problem with the XML package. This new version did not change anything for the XML table type.

          bertrandop Olivier Bertrand added a comment - Are you compiling MariaDB from source? There seem to be a problem with the XML package. This new version did not change anything for the XML table type.
          mschorm Michal Schorm added a comment -

          As a source, I use tarballs, accessible via
          https:// downloads.mariadb.org/interstitial/mariadb-

          {VERSION} /source/mariadb- {VERSION}

          .tar.gz
          I re-downloaded the sources, and did hash verification. I have the same ones.

          mschorm Michal Schorm added a comment - As a source, I use tarballs, accessible via https:// downloads.mariadb.org/interstitial/mariadb- {VERSION} /source/mariadb- {VERSION} .tar.gz I re-downloaded the sources, and did hash verification. I have the same ones.
          mschorm Michal Schorm added a comment -

          To be exact - I'm the maintainer of MariaDB & MySQL packages in Fedora project - I build the Mariadb this way as usual.

          You can check the source I use here:
          https://src.fedoraproject.org/rpms/mariadb/tree/master
          (maybe mariadb.spec may come handy)

          The 10.3.21 version is not pushed (obviously - I'm working on getting it working & pushed )
          However, I changed literally nothing form the 10.3.20 verison - just bumped the version number.
          Same for 10.4.10 vs 10.4.11.

          mschorm Michal Schorm added a comment - To be exact - I'm the maintainer of MariaDB & MySQL packages in Fedora project - I build the Mariadb this way as usual. You can check the source I use here: https://src.fedoraproject.org/rpms/mariadb/tree/master (maybe mariadb.spec may come handy) The 10.3.21 version is not pushed (obviously - I'm working on getting it working & pushed ) However, I changed literally nothing form the 10.3.20 verison - just bumped the version number. Same for 10.4.10 vs 10.4.11.
          mschorm Michal Schorm added a comment -

          > This new version did not change anything for the XML table type.
          So far I tested only on Fedora Rawhide.
          You helped me relize that could be a problem in the distro ... but I just tested it on the Fedora 30 and got the same (broken) results.

          So now I'm pretty confident, it's on "your" side.

          mschorm Michal Schorm added a comment - > This new version did not change anything for the XML table type. So far I tested only on Fedora Rawhide. You helped me relize that could be a problem in the distro ... but I just tested it on the Fedora 30 and got the same (broken) results. So now I'm pretty confident, it's on "your" side.
          bertrandop Olivier Bertrand added a comment - - edited

          I think I know what happened. The new version adds a new table type TABREST that unconditionnaly can call the XML table type. If you don't have the libxml2 package installed, then the XML table type is not generated and the XMLDEF class is not there (_ZN6XMLDEFC1Ev is probably the mangled name of the C++ class XMLDEF). The bug is that this call should be conditionnal.

          Two turnaround:

          • Install the libxml2 package.
          • Don't make the TABREST table type (compile with "Compile CONNECT storage engine with REST support=NO").
          bertrandop Olivier Bertrand added a comment - - edited I think I know what happened. The new version adds a new table type TABREST that unconditionnaly can call the XML table type. If you don't have the libxml2 package installed, then the XML table type is not generated and the XMLDEF class is not there (_ZN6XMLDEFC1Ev is probably the mangled name of the C++ class XMLDEF). The bug is that this call should be conditionnal. Two turnaround: Install the libxml2 package. Don't make the TABREST table type (compile with "Compile CONNECT storage engine with REST support=NO").
          mschorm Michal Schorm added a comment -

          Thanks!

          Adding "libxml2-devel" as a BuildRequires solved the issue.

          mschorm Michal Schorm added a comment - Thanks! Adding "libxml2-devel" as a BuildRequires solved the issue.

          People

            bertrandop Olivier Bertrand
            mschorm Michal Schorm
            Votes:
            0 Vote for this issue
            Watchers:
            4 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.