mysql 5.7 post installation notes indicates a change of configuration files from a single /etc/mysql/my.cnf to multiple /etc/mysql/mysql.d/*.cnf files. mysql-init-scripts still refer to the single /etc/mysql/my.cnf file. After upgrading from 5.7 to 5.7, I can no longer start mysql server. # /etc/init.d/mysql start * Caching service dependencies ... [ ok ] * Checking mysqld configuration for mysql ... /etc/init.d/mysql: line 186: /sbin/mysqld: No such file or directory * mysql config check failed [ !! ] * ERROR: mysql failed to start
Please post the output of $(emerge --info dev-db/mysql dev-db/mysql-init-scripts).
We don't have the whole story here. /etc/mysql/my.cnf should still exist to pull in all of the /etc/mysql/mysql.d/*.cnf files. If a user fails to move their custom changes to that new directory and accept the changed file, I'm not sure of the outcome. The /etc/mysql/my.cnf should have one, uncommented line: !includedir /etc/mysql/mysql.d
(In reply to Brian Evans from comment #2) > We don't have the whole story here. > > /etc/mysql/my.cnf should still exist to pull in all of the > /etc/mysql/mysql.d/*.cnf files. > > If a user fails to move their custom changes to that new directory and > accept the changed file, I'm not sure of the outcome. > > The /etc/mysql/my.cnf should have one, uncommented line: > > !includedir /etc/mysql/mysql.d The second part (about keeping the file around with just the one include line) was not at all clear to me. I do not remember seeing that line. I simply updated the files in /etc/mysql/mysql.d and removed the /etc/mysql/my.cnf file. I will try the upgrade again.
I reinstalled Mysql 5.7 tonight. However, this time, the /etc/mysql/my.cnf was not upgraded and I never got the warning about having to rebuilding anything linking with libmysqlclient.so.18. I had to had copy the my.cnf-5.7 file into place and re-run the revdep rebuild command. It is running. Perhaps the issue is that I read the info message the first time and though that the my.cnf was going away and only the individual files were going to be used. Also, no idea why the second time upgrading from 5.6 to 5.7 didn't give the usual upgrade steps (installing the new my.cnf file and telling the user to run revdeb rebuild).
(In reply to Dyweni from comment #4) > I reinstalled Mysql 5.7 tonight. > > However, this time, the /etc/mysql/my.cnf was not upgraded and I never got > the warning about having to rebuilding anything linking with > libmysqlclient.so.18. I see nothing wrong here. Keep in mind that config protect feature probably knows that you have already seen configuration file from 5.7 when you *re-install*. If you want to start over use emerge's "noconfmem" parameter. Regarding missing libmysqlclient warning: Beginning with MySQL 5.7, we are masking "client-libs" USE flag. Therefore the code responsible for showing the rebuild warning you know from previous versions won't be called anymore... Closing as invalid for now because given on the information you gave us it looks like you just missed elog after first upgrade and also portage's hint that you have pending configuration changes (e.g. you forgot to call dispatch-conf or etc-update).
