Is it a source build or are you using binary packages, and if so, which ones?
If it's a source build, how do you build it – in-source, out-of-source, do you run make install, ...?
This is the binary build from the mariadb repository:
[root@localhost vagrant]# cat /etc/yum.repos.d/MariaDB.repo
[MariaDB]
baseurl = http://yum.mariadb.org/10.1/centos7-amd64
gpgcheck = 1
gpgkey = https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
name = MariaDB repository
[root@localhost vagrant]# rpm -q -f /bin/mysql_install_db
MariaDB-server-10.1.38-1.el7.centos.x86_64
[root@localhost vagrant]# yum list installed |fgrep MariaDB-server
Failed to set locale, defaulting to C
MariaDB-server.x86_64 10.1.38-1.el7.centos @MariaDB
I'm seeing the same issue
$ cat /etc/yum.repos.d/mariadb.repo
|
[mariadb]
|
baseurl = https://yum.mariadb.org/10.2/centos7-amd64
|
gpgcheck = 1
|
gpgkey = https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
|
name = MariaDB
|
|
|
$ rpm -q -f /bin/mysql_install_db
|
MariaDB-server-10.2.22-1.el7.centos.x86_64
|
|
|
$ yum list installed |grep MariaDB-server
|
MariaDB-server.x86_64 10.2.22-1.el7.centos @mariadb
|
Looks like this is a systematic issue?
I was able to workaround by adding this to the configuration:
[mysql_install_db]
|
basedir = /usr
|
Sadly I can't simply use that as that config file is reused across different machines with different basedirs of the installed MariaDB. 
I've since resorted to add this config via the shell
# Workaround for https://jira.mariadb.org/browse/MDEV-18526
|
if [ $HOSTNAME = 'redacted' ]
|
then
|
MYSQL_INSTALL_DB_CONFIG="--basedir=/usr"
|
fi
|
|
|
mysql_install_db $MYSQL_INSTALL_DB_CONFIG $CONFIG
|
Thanks for the report. It appears to be a problem specific to configuration created by RPMs, at least on CentOS, but probably not limited to it.
MDEV-14580 is a culprit, it doesn't take into account this configuration.
On CentOS, mysqld is installed into /usr/sbin, while all the tools are installed into /usr/bin. Further, it has a symlink /sbin -> usr/sbin.
So, additions made by MDEV-14580
- set dirname0 to /;
- check that / exists and /sbin/mysqld exists and is executable, both of which happen to be true;
- set basedir to /;
- set bindir to //sbin;
- set resolveip to //sbin/resolveip which is bound to fail later, which is probably the reason for
MDEV-18563; - set mysqld to //sbin/mysqld which is okay;
- set srcpkgdatadir and buildpkgdatadir to //share/mysql which causes the trouble described here.
Luckily, RPM installation happens to work.
Same issue happens on openSUSE / SUSE. Any idea if this will this be fixed in the next 10.2.X release?
rsalevsky, yes, that's what the Blocker status means. No new releases (from the Fix Version/s list) until it's fixed.