Contents
Why is MariaDB only running after reboot, times out?
MariaDB troubles, only running after reboot, times out when trying restart, not stable when running. For a baseline, I have a recently upgraded Ubuntu Server 18.04 LTS from Ubuntu 16.04 LTS. I like to manage it with Virtualmin software. On it, I operate a couple projects, like a Moodle school and a Nextcloud server.
Why is MySQL not running after a reboot?
My Virtualmin web interface for the MySQL server just said: MySQL is not running on your system – database list could not be retrieved. After clicking the Virtualmin button to restart MariaDB, the full MySQL error message was: I rebooted and MariaDB was running again.
Is there a MariaDB service unit for systemd?
MariaDB comes with a mariadb.service service unit for systemd, and a mariadb-service-convert tool that migrates the settings from my.cnf into systemd service unit settings. It even comes with a [email protected] service unit template, that allows one to run multiple servers as distinct services.
What to do if MySQL is incompatible with MariaDB?
If you previously had MySQL installed, it activated an AppArmor profile which is incompatible with MariaDB. apt-get remove –purge only removes the profile, but does not deactivate/unload it. Only manually unloading it lets MariaDB work unhindered by AppArmor. This last option worked for me (from quazgar).
Where is the error log in MariaDB located?
By default, the error log is named host-name .err and is written to the data directory. C:\\Program Files\\MariaDB x.y\\data (x.y refers to the version number)
Where is the default option file in MariaDB?
The default option file is called my.cnf. Option files contain configuration options, such as the location of the data directory mentioned above. If you’re unsure where the option file is located, see Configuring MariaDB with Option Files: Default Option File Locations for information on the default locations.