View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007925||CentOS-7||mariadb||public||2014-11-25 08:21||2014-11-25 10:18|
|Summary||0007925: Falsely reported error in MariaDB just fixed. Repo update needed.|
|Description||There has been a long standing error in MariaDB where mysql_secure_installation produces the error: /usr/local/bin/mysql_secure_installation: line 379: find_mysql_client: command not found|
The error happens as soon as the program is executed and while it actually doesn't (for all I know) cause any trouble it causes a lot of unnecessary support requests and in cases such as mine where this program is part of an installer script, makes companies look bad. The error has just been fixed and so the repo needs to be updated with the current version.
Here is the bug page linked to the comment stating it's fixed (and the bug status reflects this: https://mariadb.atlassian.net/browse/MDEV-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66018#comment-66018
|Steps To Reproduce||Install MariaDB with yum and run mysql_secure_installation|
|Additional Information||bug and fix verification here: https://mariadb.atlassian.net/browse/MDEV-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=66018#comment-66018|
Centos repos need updating.
|Tags||No tags attached.|
Looks like you are using a version of MariaDB that is not provided by CentOS. There is no /usr/local/bin/mysql_secure_installation in MariaDB packages provided by CentOS. It will also look bad for your company if you don't know whose products you are using.
Although in all honesty, the bug occurs on stock CentOS-provided MariaDB as well. https://bugzilla.redhat.com/show_bug.cgi?id=1020055 is related. When Red Hat updates their packages, the fixes will eventually trickle down to CentOS.