Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
5.5(EOL), 10.0(EOL), 10.1(EOL)
-
uname -a
Linux debian8 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09) x86_64 GNU/Linux
cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support/"
BUG_REPORT_URL="https://bugs.debian.org/"uname -a Linux debian8 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09) x86_64 GNU/Linux cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 8 (jessie)" NAME="Debian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=debian HOME_URL=" http://www.debian.org/ " SUPPORT_URL=" http://www.debian.org/support/ " BUG_REPORT_URL=" https://bugs.debian.org/ "
-
10.0.24
Description
Hello, I'm building a custom script which builds/installs/upgrades mariadb from 10.0.22 to 10.1.9. One part of this script is to run mysql_upgrade to ensure that the dbs are properly upgraded from 10.0.22 to 10.1.9.
In 10.0.22 mysql_upgrade works without issues if '/etc/my.cnf.d' doesn't exists, but seems that this is an issue with 10.1.9:
root@debian8:~# mysql_upgrade --force -u root -pMyPass -h localhost
|
mysql_upgrade: Can't read dir of '/etc/my.cnf.d' (Errcode: 2 "No such file or directory")
|
Fatal error in defaults handling. Program aborted
|
Segmentation fault
|
NOTE: I don't use /etc/my.cnf.d nor I want to.
robertalks,
I've checked that neither 10.0, nor 5.5, nor MySQL up to and including 5.7 are able to start with a non-existing include directory. It appears to be reasonable, because there is no hardcoded magic about using it – the includedir directive is a part of the cnf file, so if it's there, its use is assumed to be intentional.
When standard packages are installed, they use cnf file templates, which have this directive, but they also create the desired include directory, so there is no problem with them.
Now, I don't know how your custom packaging/installation script works, but my best guess is that it uses some pre-created cnf files provided with the source code, but doesn't do the job required to make them actually usable. From the error message, it appears that you might be using support-files/rpm/my.cnf file (which is also strange since you're on Debian).
Anyway, if you do not want to use the include dir, the solution is to generate your own cnf file rather than take an existing one.