[MDEV-18495] my.cnf created as my.cnf.dpkg-new due to alternatives symlink Created: 2019-02-06  Updated: 2019-03-14  Resolved: 2019-03-14

Status: Closed
Project: MariaDB Server
Component/s: Configuration, Packaging
Affects Version/s: 10.2.21
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: David Gräfrath Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

Ubuntu Xenial


 Description   

The mariadb-server-10.2 package tries to install /etc/mysql/my.cnf, but that is already a symbolic link to /etc/alternatives/my.cnf. As a result, my.cnf is created as my.cnf.dpkg-new and hence NOT loaded when the server starts. As a result, the bind-address=127.0.0.1 directive will NOT be in effect and the server will listen on all interfaces.

This was a fresh install, not an upgrade from mysql. Only the mysql-common package was already installed due to other packages depending on it (postfix I think).

Is there a workaround for this problem? I don't want to just replace the symlink by force.

 Comments   
Comment by Elena Stepanova [ 2019-02-14 ]

What kind of a workaround do you have in mind?
The package installation finds a configuration file which it didn't install, and leaves it the user to decide whether to keep the old (possibly custom) configuration, or use the new one, or to merge the two. It seems reasonable – at the end, somebody has to make this decision, and it better be the owner. I don't think most users would be happy about a script overriding their configuration automatically.

Generated at Thu Feb 08 08:44:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.