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

mysql_install_db freeze using config with plugin_load_add=ha_spider.so

    XMLWordPrintable

Details

    Description

      our install script looks like this

      basedir='/srv/slapgrid/slappart10/srv//runner//shared/mariadb/56de580c35c9de920a80ce14a4d4c974'
      datadir='/srv/slapgrid/slappart10/srv/runner/instance/slappart3/srv/mariadb'
      [ -e "$datadir" ] ||

      { rm -vrf "$datadir.new" "$basedir/scripts/mysql_install_db" \ --defaults-file='/srv/slapgrid/slappart10/srv/runner/instance/slappart3/etc/mysql/my.cnf' \ --skip-name-resolve \ --auth-root-authentication-method=normal \ --basedir="$basedir" --plugin_dir="$basedir/lib/plugin" \ --datadir="$datadir.new" mv -v "$datadir.new" "$datadir" }

      ODBCSYSINI='/srv/slapgrid/slappart10/srv/runner/instance/slappart3/etc' \
      LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}'/srv/slapgrid/slappart10/srv//runner//shared/unixodbc/1d4d2c49a7c6207c3cdd7305997e86dc/lib' \
      exec "$basedir/bin/mysqld" --defaults-file='/srv/slapgrid/slappart10/srv/runner/instance/slappart3/etc/mysql/my.cnf' "$@"

      When a config file is included with plugin_load_add=ha_spider.so

      Install will failed and let the mysqld in defunc state

      While without that option install script works and restarting the server with the option install the plugin, so preconfigured config like used in some cloud provisioning won't work for deploying spider from init container .

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              stephane@skysql.com VAROQUI Stephane
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.