3 Node Galera Cluster - MariaDB 10.4.7 Enterprise on RHEL 7.6

The galera_recovery script refers to mysqld through the path defined by @sbindir@, which is expanded at compile time:

  eval @sbindir@/mysqld $cmdline_args --user=$user --wsrep_recover \

    --disable-log-error 2> "$log_file"

https://github.com/MariaDB/server/blob/mariadb-10.1.43/scripts/galera_recovery.sh#L71

The primary systemd unit file also refers to mysqld through the path defined by @sbindir@:

ExecStart=@sbindir@/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION

https://github.com/MariaDB/server/blob/mariadb-10.1.43/support-files/mariadb.service.in#L84

I'm not sure why the path causes issues in the galera_recovery script, but the same path apparently does not cause issues in the systemd unit file.

I downloaded a binary tarball, and it does look like @sbindir@ is being expanded to different paths when you compare the galera_recovery script and the mariadb.service unit file.

galera_recovery:

  eval ./bin/mysqld $cmdline_args --user=$user --wsrep_recover \

    --disable-log-error 2> "$log_file"

mariadb.service:

ExecStart=/usr/local/mysql/bin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION

This difference in behavior seems to occur because the scripts/ directory has special CMake rules that change the paths for "standalone" installations:

# Really ugly, one script, "mysql_install_db", needs prefix set to ".",

# i.e. makes access relative the current directory. This matches

# the documentation, so better not change this.

IF(INSTALL_LAYOUT MATCHES "STANDALONE")

  SET(prefix ".")

  SET(bindir ${prefix}/${INSTALL_BINDIR})

  SET(sbindir ${prefix}/${INSTALL_SBINDIR})

  SET(scriptdir ${prefix}/${INSTALL_BINDIR})

  SET(libexecdir ${prefix}/${INSTALL_SBINDIR})

  SET(pkgdatadir ${prefix}/${INSTALL_MYSQLSHAREDIR})

  SET(localstatedir ${prefix}/data)

ELSE()

  SET(prefix "${CMAKE_INSTALL_PREFIX}")

  SET(bindir ${INSTALL_BINDIRABS})

  SET(sbindir ${INSTALL_SBINDIRABS})

  SET(scriptdir ${INSTALL_BINDIRABS})

  SET(libexecdir ${INSTALL_SBINDIRABS})

  SET(pkgdatadir ${INSTALL_MYSQLSHAREDIRABS})

  SET(localstatedir ${MYSQL_DATADIR})

ENDIF()

https://github.com/MariaDB/server/blob/mariadb-10.1.43/scripts/CMakeLists.txt#L204

Fixed, https://github.com/MariaDB/server/commit/cbf00b625a831a306fcfa450b76f580d962c75db

ok to push

Fix here: https://github.com/MariaDB/server/commit/cbf00b625a831a306fcfa450b76f580d962c75db

The bug was reported in 10.4.x, but Fix Version(s lists only 10.1.44. What exact 10.4.x version the fix is going into?

Corrected by adding the version number (10.4.13) to fix versions. Fixed for all branches starting from 10.1. Next, the patch was merged from 10.1 to all the main branches, sequentially, including 10.4: https://github.com/MariaDB/server/commit/c8e0c524af83149e77c88e9a6fd763221dea9277

Hi sysprg,

Next, the patch was merged from 10.1 to all the main branches, sequentially, including 10.4

So shouldn't "Fix Version(s)" also mention 10.2.32 and MariaDB 10.3.23?

Also, GitHub says that the commit that you linked is in MariaDB 10.1.45, but "Fix Version(s)" for this bug lists MariaDB 10.1.44. Is it also incorrect to have "MariaDB 10.1.44" in "Fix Version(s)" then?

I took a look at the source code, and it does look to me like MariaDB 10.1.44 still has the bug, while MariaDB 10.1.45 has the fix:

https://github.com/MariaDB/server/blob/mariadb-10.1.44/support-files/mariadb.service.in#L73

https://github.com/MariaDB/server/blob/mariadb-10.1.45/support-files/mariadb.service.in#L73

So the "Fix Version(s)" field for this bug should actually be "MariaDB 10.1.45, 10.2.32, MariaDB 10.3.23, MariaDB 10.4.13" and "MariaDB 10.1.44" should be completely removed from the field, right?

GeoffMontee Thanks for the clarification, I corrected the list of versions - indeed, the correction is relevant only from 10.1.45 and it was necessary to specify other versions