Beim Update von maria.db und auf
archlinux.org kommt dieser Hinweis:
mariadb 10.4.x update requires manual intervention (Thu, 27 Jun 2019 13:40:25 +0000)
The update to mariadb 10.4.6-1 and later changes configuration layout as recommended by upstream.The main
configuration file moved from /etc/mysql/my.cnf (and its include directory /etc/mysql/my.cnf.d/) to /etc/my.cnf
(and /etc/my.cnf.d/). Make sure to move your configuration.Instantiated services (like mariadb@foo.service) are
no longer configured in separate files (like /etc/mysql/myfoo.cnf). Instead move your configuration to
configuration blocks with group suffix in main configuration file, one for each service. A block should look
something like this:[mysqld.foo]datadir = /var/lib/mysql-foosocket = /run/mysqld/mysqld-foo.sock...Like every
mariadb feature update this requires the data directory to be updated. With the new configuration in place
run:systemctl restart mariadb.service && mariadb-upgrade -u root -p
Ich bin da grad etwas unsicher, da ich keine Anpassungen gemacht habe sollte doch auch kein manueller Eingriff nötig sein, oder?
Die Einzige cnf-Datei mit relavantem Inhalt ist enable_encryption.preset:
cat /etc/mysql/my.cnf.d/enable_encryption.preset
#
# !include this file into your my.cnf (or any of *.cnf files in /etc/mysql/my.cnf.d)
# and it will enable data at rest encryption. This is a simple way to
# ensure that everything that can be encrypted will be and your
# data will not leak unencrypted.
#
# DO NOT EDIT THIS FILE! On MariaDB upgrades it might be replaced with a
# newer version and your edits will be lost. Instead, add your edits
# to the .cnf file after the !include directive.
#
# NOTE that you also need to install an encryption plugin for the encryption
# to work. See https://mariadb.com/kb/en/mariadb/data-at-rest-encryption/#encryption-key-management
#
[mariadb]
aria-encrypt-tables
encrypt-binlog
encrypt-tmp-disk-tables
encrypt-tmp-files
loose-innodb-encrypt-log
loose-innodb-encrypt-tables