Bug 23426 - mysqld-prepare-db-dir (code=exited, status=1/FAILURE)
Summary: mysqld-prepare-db-dir (code=exited, status=1/FAILURE)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Marc Krämer
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-08-10 21:28 CEST by Bit Twister
Modified: 2018-08-11 05:33 CEST (History)
2 users (show)

See Also:
Source RPM: mariadb-core-10.3.8-3.mga7.src.rpm
CVE:
Status comment:


Attachments

Description Bit Twister 2018-08-10 21:28:25 CEST
Description of problem:  dev0

Aug 10 09:16:32 mysqld-prepare-db-dir[810] snipped from start of each line
: Initializing MySQL database
: FATAL ERROR: Could not find /usr/share/mysql/mysql_test_db.sql
: If you compiled from source, you need to either run 'make install' to
: copy the software into the correct location ready for operation.
: If you don't want to do a full install, you can use the --srcddir
: option to only install the mysql database and privilege tables
: If you are using a binary release, you must either be at the top
: level of the extracted archive, or pass the --basedir option
: pointing to that location.
: The latest information about mysql_install_db is available at
: https://mariadb.com/kb/en/installing-system-tables-mysql_install_db

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. systemctl start mysqld
2. journalctl --no-hostname | grep mysqld
3.
Comment 1 Marja Van Waes 2018-08-10 22:28:05 CEST
assigning to registered maintainer, Cc'ing mkrämer, who, iirc, pushed mariadb in a recent past

Assignee: bugsquad => alien
CC: (none) => mageia, marja11

Comment 2 Marc Krämer 2018-08-10 23:38:35 CEST
and what is the problem with that output?
It is only occurs on the first start of mysqld. This is because we don't want to have the testdatabase in production environments.

Assignee: alien => mageia

Comment 3 Marc Krämer 2018-08-10 23:39:02 CEST
sorry. last comment was not supposed to be posted.
Comment 4 Bit Twister 2018-08-11 01:49:36 CEST
(In reply to Marc Krämer from comment #2)
> and what is the problem with that output?
> It is only occurs on the first start of mysqld. This is because we don't
> want to have the testdatabase in production environments.

I can agree it is a good security practice, and I have an expect script which runs mysql_secure_installation to remove the test database and whatnot, but
the big problem with it is,

# systemctl start mysqld
Job for mysqld.service failed because the control process exited with error code.
See "systemctl status mysqld.service" and "journalctl -xe" for details.
Bit Twister 2018-08-11 01:53:22 CEST

Severity: normal => major

Comment 5 Bit Twister 2018-08-11 05:33:36 CEST
update mariadb-core-10.3.8-4.mga7 resolved the problem.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.