[MDEV-22833] Ubuntu 20 and default setup issue Created: 2020-06-08 Updated: 2021-03-10 Resolved: 2021-03-10 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Configuration, Platform Debian |
| Affects Version/s: | 10.3 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Oleksandr Marushchenko | Assignee: | Otto Kekäläinen |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
mysql Ver 15.1 Distrib 10.3.22-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2 Distributor ID: Ubuntu |
||
| Description |
|
At default setup Ubuntu creates this file: its a symlink: So, then you trying to change something in config files you have zero reaction, and you cant debug it by service mariadb restart - it restarts and everything works, but config is ingored because of this:
So you can spend a hours to guess that is going on. |
| Comments |
| Comment by Otto Kekäläinen [ 2020-07-08 ] |
|
Which version are you running? What does `dpkg -l | grep mariadb` show? You could try uninstalling and purging and re-installing. Most likely you have some manual changes in /etc/mysql that causes this. You can also review yourself what `find /etc/mysql -ls` shows. |
| Comment by Oleksandr Marushchenko [ 2020-07-08 ] |
Ubuntu 20.04 LTS (GNU/Linux 5.4.0-37-generic x86_64)
It was absolutely clean install from fresh Ubuntu in DigitalOcean. I found how to fix it - i was need to remove the /etc/mysql/my.cnf link and create the real file instead, but the default setup is broken - you cant change anything in config because of World-writable config. It can be the maintainer problem - i just didn't found where to make report to them. |
| Comment by Otto Kekäläinen [ 2020-07-08 ] |
|
This is surely does not look like a clean install. A clean install Somebody or something created that file and it is the root cause to |
| Comment by Faustin Lammler [ 2021-03-10 ] |
|
wokenlex can you confirm and can we close this issue then? |
| Comment by Oleksandr Marushchenko [ 2021-03-10 ] |
|
I didn't tried it after that. It's look like it was issue with mysql_secure_installation, what was runned as root. I think you can close, because it's not directly related to mariadb. |