Description of problem:
Having the error log file in /var/log means that when missing, daemon (running as mysql:mysql) cannot re-create it. It makes troubles when rotating logs, or when an admin removes it manually. In that case, admin is responsible for re-creating the empty log file now, with proper owner and SELinux context.
I'd like to propose moving the error log to a separate directory properly owned by mysql:mysql user, so daemon can re-created when missing. It's done similarly in mariadb already.
That obviously changes default behaviour, so we should only do it in F29 and further, and document it in Release Notes.. The expected changes are the following:
* For users who have done some changes in /etc/my.cnf.d/community-mysql-server.cnf, the config will stay to use /var/log/mysqld.log
* For users who have not done any changes in /etc/my.cnf.d/community-mysql-server.cnf, or install MySQL on a fresh machine, they will use /var/log/mysql/mysqld.log
So, the impact is not that the service would not start, it's just that some monitoring tools would need to re-configure.
Michal, Norvald, what do you think?
I agree. Moving the log file to /var/log/mysql/ makes sense.
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.
community-mysql-8.0.13-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c82fc3e109
community-mysql-8.0.13-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-c82fc3e109
community-mysql-8.0.13-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.