Bug 25901

Summary:	/usr/lib64/mysql/plugin/auth_pam_tool_dir': No such file or directory
Product:	Mageia	Reporter:	Bit Twister <bittwister2>
Component:	RPM Packages	Assignee:	Marc Krämer <mageia>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	alien, jani.valimaa
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	mariadb-10.4.11-1.mga8.src.rpm	CVE:
Status comment:

Description Bit Twister 2019-12-19 18:13:12 CET

Description of problem:  mga8 dev

# systemctl status mysqld.service 
● mysqld.service - MySQL database server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2019-12-19 10:52:14 CST; 53s ago
  Process: 24329 ExecStartPre=/usr/sbin/mysqld-prepare-db-dir (code=exited, status=1/FAILURE)

# /usr/sbin/mysqld-prepare-db-dir
Initializing MySQL database
chown: cannot access '/usr/lib64/mysql/plugin/auth_pam_tool_dir': No such file or directory
Cannot change ownership of the '/usr/lib64/mysql/plugin/auth_pam_tool_dir' directory
 to the 'mysql' user. Check that you have the necessary permissions and try again.


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


How reproducible: Always


Steps to Reproduce:
1. systemctl start mysqld
2. systemctl status mysqld

Comment 1 Lewis Smith 2019-12-19 20:51:34 CET

Thank you for reporting this : a Cauldron issue.
Assigning to Marc as the active committer for mariadb; CC'ing

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

Comment 2 Lewis Smith 2019-12-19 20:54:07 CET

Sorry, wrong click in the middle of doing this:
CC alien as the registered maintainer.

Comment 3 Jani Välimaa 2019-12-20 10:13:03 CET

Moved %{_libdir}/mysql/plugin/auth_pam_tool_dir/auth_pam_tool from mariadb-bench to mariadb.

Please test with mariadb-10.4.11-2.mga8.

CC: (none) => jani.valimaa

Comment 4 Marc Krämer 2019-12-20 12:22:47 CET

thx Jani

Comment 5 Bit Twister 2019-12-20 14:31:43 CET

Thank you all for your work with Mageia and the quick fix.

mysqld service now starts correctly.

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