Bug#848616: mysql_install_db creates unusable root user
> > as the deadline for uploading any affected packages for stretch is > > approaching, something really needs to be done. > > I hear this is fixed in mariadb-10.1, see #851131. Can you test again on an > up-to-date sid? Hopefully python3-testing.mysqld can be updated now. Yep, works, thanks! -nik -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Hundeshagenstr. 26 · 53225 Bonn Mobile: +49-1520-1981389 · https://www.dominik-george.de/ Teckids e.V. · FrOSCon e.V. Fellowship of the FSFE · Piratenpartei Deutschland Opencaching Deutschland e.V. · Debian Maintainer LPIC-3 Linux Enterprise Professional (Security) signature.asc Description: PGP signature
Bug#848616: mysql_install_db creates unusable root user
On Thu, 12 Jan 2017 13:21:03 +0100 Dominik George wrote: > Hi, > > as the deadline for uploading any affected packages for stretch is > approaching, something really needs to be done. I hear this is fixed in mariadb-10.1, see #851131. Can you test again on an up-to-date sid? Hopefully python3-testing.mysqld can be updated now. Cheers, Emilio
Bug#848616: mysql_install_db creates unusable root user
Hi, as the deadline for uploading any affected packages for stretch is approaching, something really needs to be done. This bug makes mariadb unfit as a drop-in replacement for mysql, and fixing it would mean a simple build config change for the maintainers. Doing so would result in mostly everyone being able to fix their packages in time, and I do not see any issues with the old behaviour. If the MySQL/MariaDB maintainers do not see an issue with all of that, should we file an urgent issue with the tech-ctte? Cheers, Nik -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Hundeshagenstr. 26 · 53225 Bonn Mobile: +49-1520-1981389 · https://www.dominik-george.de/ Teckids e.V. · FrOSCon e.V. Fellowship of the FSFE · Piratenpartei Deutschland Opencaching Deutschland e.V. · Debian Maintainer LPIC-3 Linux Enterprise Professional (Security) signature.asc Description: PGP signature
Bug#848616: mysql_install_db creates unusable root user
Package: mariadb-server-10.0 Version: 10.0.28-2 Severity: serious mysql_install_db fails to create a working root user when run as non-root or maybe with a custom datadir. This is serious because various packages use this to set up a temporary mysqld to test themselves. Repro steps: ch@d:~ % mktemp -d /tmp/tmp.WiS7YFCukw ch@d:~ % mysql_install_db --no-defaults --datadir=/tmp/tmp.WiS7YFCukw --force --skip-name-resolve Installing MariaDB/MySQL system tables in '/tmp/tmp.WiS7YFCukw' ... 161219 0:18:34 [Note] /usr/sbin/mysqld (mysqld 10.0.28-MariaDB-2) starting as process 11914 ... 161219 0:18:34 [Note] InnoDB: Using mutexes to ref count buffer pool pages 161219 0:18:34 [Note] InnoDB: The InnoDB memory heap is disabled 161219 0:18:34 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 161219 0:18:34 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 161219 0:18:34 [Note] InnoDB: Compressed tables use zlib 1.2.8 161219 0:18:34 [Note] InnoDB: Using Linux native AIO 161219 0:18:34 [Note] InnoDB: Using CPU crc32 instructions 161219 0:18:34 [Note] InnoDB: Initializing buffer pool, size = 128.0M 161219 0:18:34 [Note] InnoDB: Completed initialization of buffer pool 161219 0:18:34 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created! 161219 0:18:34 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB 161219 0:18:34 [Note] InnoDB: Database physically writes the file full: wait... 161219 0:18:34 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB 161219 0:18:34 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB 161219 0:18:34 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 161219 0:18:34 [Warning] InnoDB: New log files created, LSN=45781 161219 0:18:34 [Note] InnoDB: Doublewrite buffer not found: creating new 161219 0:18:34 [Note] InnoDB: Doublewrite buffer created 161219 0:18:34 [Note] InnoDB: 128 rollback segment(s) are active. 161219 0:18:34 [Warning] InnoDB: Creating foreign key constraint system tables. 161219 0:18:34 [Note] InnoDB: Foreign key constraint system tables created 161219 0:18:34 [Note] InnoDB: Creating tablespace and datafile system tables. 161219 0:18:34 [Note] InnoDB: Tablespace and datafile system tables created. 161219 0:18:34 [Note] InnoDB: Creating zip_dict and zip_dict_cols system tables. 161219 0:18:34 [Note] InnoDB: zip_dict and zip_dict_cols system tables created. 161219 0:18:34 [Note] InnoDB: Waiting for purge to start 161219 0:18:34 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.32-79.0 started; log sequence number 0 161219 0:18:34 [Note] InnoDB: FTS optimize thread exiting. 161219 0:18:34 [Note] InnoDB: Starting shutdown... 161219 0:18:35 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool 161219 0:18:37 [Note] InnoDB: Shutdown completed; log sequence number 1623569 OK Filling help tables... 161219 0:18:37 [Note] /usr/sbin/mysqld (mysqld 10.0.28-MariaDB-2) starting as process 11940 ... 161219 0:18:37 [Note] InnoDB: Using mutexes to ref count buffer pool pages 161219 0:18:37 [Note] InnoDB: The InnoDB memory heap is disabled 161219 0:18:37 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 161219 0:18:37 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 161219 0:18:37 [Note] InnoDB: Compressed tables use zlib 1.2.8 161219 0:18:37 [Note] InnoDB: Using Linux native AIO 161219 0:18:37 [Note] InnoDB: Using CPU crc32 instructions 161219 0:18:37 [Note] InnoDB: Initializing buffer pool, size = 128.0M 161219 0:18:37 [Note] InnoDB: Completed initialization of buffer pool 161219 0:18:37 [Note] InnoDB: Highest supported file format is Barracuda. 161219 0:18:37 [Note] InnoDB: 128 rollback segment(s) are active. 161219 0:18:37 [Note] InnoDB: Waiting for purge to start 161219 0:18:37 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.32-79.0 started; log sequence number 1623569 161219 0:18:37 [Note] InnoDB: FTS optimize thread exiting. 161219 0:18:37 [Note] InnoDB: Starting shutdown... 161219 0:18:38 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool 161219 0:18:40 [Note] InnoDB: Shutdown completed; log sequence number 1623579 OK To start mysqld at boot time you have to copy support-files/mysql.server to the right place for your system PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER ! To do so, start the server, then issue the following commands: '/usr/bin/mysqladmin' -u root password 'new-password' '/usr/bin/mysqladmin' -u root -h password 'new-password' Alternatively you can run: '/usr/bin/mysql_secure_installation' which will also give you the option of removing the test databases and anonymous user created by default. This is strongly recommended for production servers. See the MariaDB Knowledgebase at http://mariadb.com/kb or the MySQL manual for more instructions. You can start the Mari
