On a seemingly working server you may encounter the following checking out the mysql status: Jun 15 10:32:33 host systemd[1]: Starting MariaDB 10.3.39 database server…
Kopano servers need memory optimization. There is an entire chapter written about it here: https://documentation.kopano.io/kopanocore_administrator_manual/performance_tuning.html Unfortunately Kopano open source is dead and they left their
Background On a legacy server with an older version of MariaDB, restoring to a newer Virtualmin server that run MySQL 8 might be problematic. The
Background Having a broken MySQL / MariaDB database is no fun. Broken tables can also lead to half complete backups really compounding the situation. If
Background If you have a server with sufficient RAM but you are running out of MySQL connections, you might want to look at two easy
You might encounter a situation (e.g. on AWS) where you have a new CentOS 7 server, but an old version of MariaDB 5.5 on the
Background A MySQL server stop working. You’re confused as this is a new Virtualmin installation and everything went smooth. You start troubleshooting: # service mariadb
rename table t1 to t2; Reference: https://blog.marceloaltmann.com/en-how-to-rename-table-in-mysql-pt-como-renomear-tabelas-no-mysql/
Background This article explains how to upgrade the default MariaDB 10.1 installation provided with Linux Mint 19 Tara or Tessa to MariaDB 10.3. One reason
Whilst doing this: mysql_upgrade -uusername -ppassword You get this: Could not create the upgrade info file ‘/var/lib/mysql/mysql_upgrade_info’ in the MariaDB Servers datadir, errno: 13 Solution:
Copyright 2024 © All rights Reserved