Your message dated Fri, 30 Aug 2019 18:32:51 +0000
with message-id <[email protected]>
and subject line Bug#928758: fixed in mariadb-10.1 10.1.41-0+deb9u1
has caused the Debian Bug report #928758,
regarding mariadb-server: mysql_install_db fails if basedir option isn't set, 
expecting resolveip to be present in /usr/sbin/
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
928758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928758
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mariadb-server
Version: 10.1.38-0+deb9u1
Severity: important

Hi,

starting with mariadb-server version 10.1.38-0+deb9u1, executing
/usr/bin/mysql_install_db fails if --basedir option isn't
explicitly set or configured accordingly via my.cnf:

| root@prx01b:~# /usr/bin/mysql_install_db --user=mysql --datadir=/tmp/foo
| Neither host 'prx01b' nor 'localhost' could be looked up with
| '/usr/sbin/resolveip'
| Please configure the 'hostname' command to return a correct
| hostname.
| If you want to solve this at a later stage, restart this script
| with the --force option
| 
| The latest information about mysql_install_db is available at
| https://mariadb.com/kb/en/installing-system-tables-mysql_install_db

While resolveip is present in /usr/bin (instead of /usr/sbin):

| root@prx01b:~# which resolveip
| /usr/bin/resolveip

Whereas it works fine with `--basedir` explicitly set to /usr:

| root@prx01b:~# /usr/bin/mysql_install_db --basedir=/usr
| Installing MariaDB/MySQL system tables in '/var/lib/mysql' ...
| 2019-05-10 15:38:34 140091769200000 [Note] /usr/sbin/mysqld (mysqld 
10.1.38-MariaDB-0+deb9u1) starting as process 24550 ...
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB: 
innodb_empty_free_list_algorithm has been changed to legacy because of small 
buffer pool size. In order to use backoff, increase buffer pool at least up to 
20MB.
| 
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB: Using mutexes to ref count 
buffer pool pages
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB: The InnoDB memory heap is 
disabled
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB: Mutexes and rw_locks use 
GCC atomic builtins
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB: GCC builtin 
__atomic_thread_fence() is used for memory barrier
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB: Compressed tables use zlib 
1.2.8
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB: Using Linux native AIO
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB: Using SSE crc32 
instructions
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB: Initializing buffer pool, 
size = 128.0M
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB: Completed initialization 
of buffer pool
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB: Highest supported file 
format is Barracuda.
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB: 128 rollback segment(s) 
are active.
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB: Waiting for purge to start
| 2019-05-10 15:38:34 140091769200000 [Note] InnoDB:  Percona XtraDB 
(http://www.percona.com) 5.6.42-84.2 started; log sequence number 1616727
| 2019-05-10 15:38:35 140091057989376 [Note] InnoDB: Dumping buffer pool(s) not 
yet started

This breaking change was caused by the following change in between
10.1.37-0+deb9u1 and 10.1.38-0+deb9u1 (see mariadb-10.1.git):

| (git)-[debian/10.1.38-0+deb9u1] % git diff debian/10.1.37-0+deb9u1.. 
scripts/mysql_install_db.sh
| diff --git a/scripts/mysql_install_db.sh b/scripts/mysql_install_db.sh
| index 0bbac8ba8..b89ea716a 100644
| --- a/scripts/mysql_install_db.sh
| +++ b/scripts/mysql_install_db.sh
| @@ -39,6 +39,9 @@ install_params=""
|  auth_root_authentication_method=normal
|  auth_root_socket_user='root'
| 
| +dirname0=`dirname $0 2>/dev/null`
| +dirname0=`dirname $dirname0 2>/dev/null`
| +
| [...]
|    fi
| +# relative from where the script was run for a relocatable install
| +elif test -n "$dirname0" -a -x "$dirname0/@INSTALL_SBINDIR@/mysqld"
| +then
| +  basedir="$dirname0"
| +  bindir="$basedir/@INSTALL_SBINDIR@"
| +  resolveip="$bindir/resolveip"
| +  mysqld="$basedir/@INSTALL_SBINDIR@/mysqld"
| +  srcpkgdatadir="$basedir/@INSTALL_MYSQLSHAREDIR@"
| +  buildpkgdatadir="$basedir/@INSTALL_MYSQLSHAREDIR@"
|  else
|    basedir="@prefix@"
|    bindir="@bindir@"

This change is causing bindir being set to bindir=/usr/sbin, while
it's supposed to be bindir=/usr/bin on Debian systems, so that
resolveip is used as /usr/bin/resolveip.

FTR: We're using multiple sections inside /etc/mysql/my.cnf
(`[mysqld1]` and `[mysqld2]`). When adding a `mysqld` section with
the following configuration to /etc/mysql/my.cnf it also works
without having to explicitly specify the `--basedir` option:

| [mysqld]
| basedir = /usr

As expected it also works in our setup when we specify the
`--defaults-group-suffix` option, like:

| root@prx01b:~# /usr/bin/mysql_install_db --defaults-group-suffix=1
| Installing MariaDB/MySQL system tables in '/var/lib/mysql' ...
| 2019-05-10 16:00:23 139685437468032 [Note] /usr/sbin/mysqld (mysqld 
10.1.38-MariaDB-0+deb9u1) starting as process 25302 ...
| [....]

But neither of this was necessary so far, and the new
mysql_install_db behavior isn't as reliable as it used to be. The
directory /usr/bin should be detected and assumed as sensible
default for bindir (instead of relying on the base path of the
«mysqld» binary inside /usr/sbin).

regards
-mika-

--- End Message ---
--- Begin Message ---
Source: mariadb-10.1
Source-Version: 10.1.41-0+deb9u1

We believe that the bug you reported is fixed in the latest version of
mariadb-10.1, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Otto Kekäläinen <[email protected]> (supplier of updated mariadb-10.1 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 02 Aug 2019 18:10:23 +0100
Source: mariadb-10.1
Binary: libmariadbclient18 libmariadbclient-dev libmariadbclient-dev-compat 
libmariadbd18 libmariadbd-dev mariadb-common mariadb-client-core-10.1 
mariadb-client-10.1 mariadb-server-core-10.1 mariadb-server-10.1 mariadb-server 
mariadb-client mariadb-plugin-connect mariadb-plugin-oqgraph 
mariadb-plugin-tokudb mariadb-plugin-mroonga mariadb-plugin-spider 
mariadb-plugin-gssapi-server mariadb-plugin-gssapi-client 
mariadb-plugin-cracklib-password-check mariadb-test mariadb-test-data
Architecture: source
Version: 10.1.41-0+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian MySQL Maintainers <[email protected]>
Changed-By: Otto Kekäläinen <[email protected]>
Description:
 libmariadbclient-dev - MariaDB database development files
 libmariadbclient-dev-compat - MariaDB database development files 
(libmysqlclient compatibility)
 libmariadbclient18 - MariaDB database client library
 libmariadbd-dev - MariaDB embedded database, development files
 libmariadbd18 - MariaDB embedded database, shared library
 mariadb-client - MariaDB database client (metapackage depending on the latest 
vers
 mariadb-client-10.1 - MariaDB database client binaries
 mariadb-client-core-10.1 - MariaDB database core client binaries
 mariadb-common - MariaDB common metapackage
 mariadb-plugin-connect - Connect storage engine for MariaDB
 mariadb-plugin-cracklib-password-check - CrackLib Password Validation Plugin 
for MariaDB
 mariadb-plugin-gssapi-client - GSSAPI authentication plugin for MariaDB client
 mariadb-plugin-gssapi-server - GSSAPI authentication plugin for MariaDB server
 mariadb-plugin-mroonga - Mroonga storage engine for MariaDB
 mariadb-plugin-oqgraph - OQGraph storage engine for MariaDB
 mariadb-plugin-spider - Spider storage engine for MariaDB
 mariadb-plugin-tokudb - TokuDB storage engine for MariaDB
 mariadb-server - MariaDB database server (metapackage depending on the latest 
vers
 mariadb-server-10.1 - MariaDB database server binaries
 mariadb-server-core-10.1 - MariaDB database core server files
 mariadb-test - MariaDB database regression test suite
 mariadb-test-data - MariaDB database regression test suite - data files
Closes: 928758
Changes:
 mariadb-10.1 (10.1.41-0+deb9u1) stretch; urgency=medium
 .
   * SECURITY UPDATE: New upstream version 10.1.41. Includes fixes for the
     following security vulnerabilities:
     - CVE-2019-2737
     - CVE-2019-2739
     - CVE-2019-2740
     - CVE-2019-2805
   * Previous release 10.1.39
     includes fixes for the following security vulnerabilities:
     - CVE-2019-2627
     - CVE-2019-2614
   * Amend previous changelog entries to include newly released CVE numbers.
   * Gitlab-CI: Sync latest version from Debian Sid but with Stretch adaptions
   * Uses respolveip from correct path as per upstream fix (Closes: #928758)
Checksums-Sha1:
 d844df14abec60db8c532a97c31969d56798e249 4530 mariadb-10.1_10.1.41-0+deb9u1.dsc
 5c948cb6da3fa9d30a44e7b0e3a2b678728613a3 63615288 
mariadb-10.1_10.1.41.orig.tar.gz
 e21589d9e452f46c9b2f9134214d0ce91e8e546d 181 
mariadb-10.1_10.1.41.orig.tar.gz.asc
 57f0f1d98cabc377e01180d9f553ced026f03605 230668 
mariadb-10.1_10.1.41-0+deb9u1.debian.tar.xz
 029c93b6a2153ace19ef561cad0c4a78eb87f14e 9224 
mariadb-10.1_10.1.41-0+deb9u1_source.buildinfo
Checksums-Sha256:
 34bbcf9ace859cb643b1255e8be4d0741ba11e429e1d1b7210fb5d7e2daaa9c8 4530 
mariadb-10.1_10.1.41-0+deb9u1.dsc
 2b47c3afdae81eab2b9c29ba6a10328acb8d07166e8112744f6d704cc70100f2 63615288 
mariadb-10.1_10.1.41.orig.tar.gz
 71f6ef742254a40eefe0d580e71717f69e79472db84960467929fcdff73405bc 181 
mariadb-10.1_10.1.41.orig.tar.gz.asc
 50abd9acf083b4bf559e04db5251d932a3d40a0e87fbb93985413c3a616c6076 230668 
mariadb-10.1_10.1.41-0+deb9u1.debian.tar.xz
 ae2addc10734cce2de71d633b4f67dc5fa48693a1aa1e0915ff92e1e0402c9ba 9224 
mariadb-10.1_10.1.41-0+deb9u1_source.buildinfo
Files:
 325ab0c01593e74b78fb8c0ca84db79d 4530 database optional 
mariadb-10.1_10.1.41-0+deb9u1.dsc
 61734660cf7c1f3152e1824efba575ee 63615288 database optional 
mariadb-10.1_10.1.41.orig.tar.gz
 8bdea87e38392d43b76c68de2e229d00 181 database optional 
mariadb-10.1_10.1.41.orig.tar.gz.asc
 09cfb5f120f04d9834d5ec2ccb4db9d4 230668 database optional 
mariadb-10.1_10.1.41-0+deb9u1.debian.tar.xz
 1a32423892ba020e8ee5d00a42be9f80 9224 database optional 
mariadb-10.1_10.1.41-0+deb9u1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmbRSsR88dMO0U+RvvthEn87o2ogFAl1lo9UACgkQvthEn87o
2ojNehAAtcspQofLOBs68uB6BsRDAB+c5H1s66cBaPSFy0HA9vd2H0gzwoYHAuwV
Z1zm2t1hOFKan3bEdvz2CLSqoCKrTD8TW/5PmZTWoP9ywwsR0tigS/X6PaqHxdY8
928nbz2PYEyVhMD7fcC5TXjxogUWymH2G93BQ87UrAKiUteDAQtE5WOeof8n6ewb
1TaVIL+SD9pCsDm2+h5FE4KEjZBkeh3mZCDatvUzYPVkTFfZFW2gYdJn758jPaRX
ud9WHRqDCq/qfBJPF0MZgy+TIcJ3M+3taUQZbbHOUtO0LjYCPhI3A3bjy5jNY4/c
iGOpnYTatlUWDwnNfqZ2C7HlJb2mDBm6KiQNn/404eKDDhRC+USqyxPIlx6RMKyw
m+4lcNkKZmxltMXdPVCtI0hn+FSu1JKo74QGFvhGwhJnVO3NxL0AoA5xHvMv3Vm7
d8qUCf3OG4085pCw4+8wxNGUz9+Dk4oWy49X5L+XQqXz5OfjfKXM5w4LQjzaMBTt
rBv3QLOL/nCtr+TlHk+2dKx05YFy4hRklvZ8Yr5Hn59k4V0H3Dxk/qiElS2MNfmA
tTNyAu+v2uqrKNJITNYrwhiFwbaDxfmpdyh0x5gzQkpvdaLfm3PVKKEef9+NGn8s
Ibw7EPBfLuOmxLiQ6We5/sAddAHcuZ0aVe2LT8n+itAsPH93CTc=
=T8ZF
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to