Details
-
Bug
-
Status: In Testing (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.5, 10.6
Description
When we used MariaDB repository installations and upgraded from 10.3 to 10.5 the installation script silently removed our my.cnf file (does NO backup!).
After the upgrade connection with clients was not possible any more (because bind_address was set back to 127.0.0.1) and replication was broken.
After restoring my.cnf configuration file everything worked fine again. So keep a backup of your my.cnf!
Before upgrade:
root@ubuntu2004:/etc/mysql# ll
|
drwxr-xr-x 2 root root 4096 Oct 18 16:01 conf.d/
|
-rw------- 1 root root 333 Oct 18 16:01 debian.cnf
|
-rwxr-xr-x 1 root root 1525 Aug 2 12:58 debian-start*
|
-rw-r--r-- 1 root root 527 Aug 2 12:58 mariadb.cnf
|
drwxr-xr-x 2 root root 4096 Aug 2 15:38 mariadb.conf.d/
|
-rw-r--r-- 1 root root 5170 Aug 2 12:58 my.cnf
|
after upgrade:
drwxr-xr-x 2 root root 4096 Oct 18 16:01 conf.d/
|
-rw------- 1 root root 333 Oct 18 16:01 debian.cnf
|
-rwxr-xr-x 1 root root 1731 Aug 3 10:29 debian-start*
|
-rw-r--r-- 1 root root 1126 Aug 3 10:29 mariadb.cnf
|
drwxr-xr-x 3 root root 4096 Oct 18 16:13 mariadb.conf.d/
|
lrwxrwxrwx 1 root root 24 Oct 18 16:13 my.cnf -> /etc/alternatives/my.cnf
|
It is pretty nasty that the file was removed at all and that it did not creates at least a backup and outputs a warning!!! At least!
Attachments
Issue Links
- duplicates
-
-
- Closed
-