NOTE: MariaDB and MySQL packages conflict because they provide similar files. So, you can only install one of them, either MariaDB or MySQL, but not both.
find Default Password, For security reasons, MySQL generates a temporary root key. Please note that MySQL has even stricter security policies than MariaDB.
NOTE: The -d option used for _BOTH_ in the podman run command above makes the container run in the background. Use this command to monitor the output from the container:
=== Connecting to MySQL Server from within the Container
----
podman exec -it mysql mysql -uroot -p
----
you must reset the server root password by issuing this statement:
----
mysql> ALTER USER 'root'@'localhost' IDENTIFIED BY 'password';
----
=== Connecting to MariaDB Server from within the Container
----
podman exec -it mariadb bash
----
=== Reseting SQL_ROOT_PASSWORD
you must reset the server root password by issuing this statement:
----
mysql> ALTER USER 'root'@'localhost' IDENTIFIED BY 'password';
----
=== Stopping and Deleting a SQL Container
----
podman {start|stop|restart} {mysql|mariadb}
----
=== Deleting a SQL Container
----
podman rm {mysql|mariadb}
----
WARNING: you can do the same with _docker_ just change _podman_ with _docker_.
* MySQL Community -> `/etc/my.cnf.d/community-mysql-server.cnf`
* MariaDB -> `/etc/my.conf`
NOTE: you can ensure that with the following command `rpm -qc [package]`.
Navigate to the line that begins with the bind-address directive. It will look like this:
you could set this directive to a wildcard IP address, either *, ::, or 0.0.0.0:
----
bind-address = 0.0.0.0
----
After changing this line, save and close the file and then restart the MySQL service:
----
sudo systemctl restart {mysqld|mariadb}
----
=== Creating a USER
----
CREATE USER 'your_username'@'host_ip_addr' IDENTIFIED BY 'your_password';
----
NOTE: Replace your_username and your_password depending on what you want the username and password to be. Here, host_ip_addr is the hostname or IP address of the computer from where you want to connect to the MySQL/MariaDB server. You can also use % as host_ip_addr if you want to connect from any computer. It can also be something like 192.168.2.% if you want to connect from computers from the IP range 192.168.2.1 – 192.168.2.254.
=== Allow Access
----
GRANT ALL PRIVILEGES ON *.* TO 'your_username'@'%';
IDENTIFIED BY 'my-new-password' WITH GRANT OPTION;
----
#### OR ####
It is common for people to want to create a "root" user that can connect from anywhere, so as an example, we'll do just that, but to improve on it we'll create
a root user that can connect from anywhere on the local area network (LAN)
----
GRANT ALL PRIVILEGES ON *.* TO 'root'@'192.168.100.%'
IDENTIFIED BY 'my-new-password' WITH GRANT OPTION;
dnf list installed | grep -i -e maria -e mysql -e galera
----
Check parameters in configuration file:
* MySQL:
----
mysqld --print-defaults
----
* MariaDB/MySQL Comunnity:
----
/usr/libexec/mysqld --print-defaults
----
WARNING: Compatiblity between different version are not allowed Just install one of them.
=== How to Access SQL Error Logs
Oftentimes, the root cause of slowdowns, crashes, or other unexpected behavior in SQL can
In many cases, the error logs are most easily read with the less program, a command line u
if SQL isn’t behaving as expected, you can obtain more information about the source of the
* **systemctl status mysqld.service** doesn't start well, This information doesn’t explain
well what is happening?, after this command you should type `journalctl -xe -u mariadb -u mysqld`.
* Look at Log files, can be located in `/var/log/mysql/mysqld.log` for MySQL, and `/var/log/mariabd` for MariaDB.
=== How To Troubleshoot Socket Errors in SQL
SQL manages connections to the database server through the use of a socket file, a special kind of file that facilitates communications between different processes. The MySQL server’s socket file is named mysqld.sock and on Ubuntu systems it’s usually stored in the /var/run/mysqld/ directory. This file is created by the MySQL service automatically.
Sometimes, changes to your system or your SQL configuration can result in SQL being unable to read the socket file, preventing you from gaining access to your databases. The most common socket error looks like this:
----
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
----
There are a few reasons why this error may occur, and a few potential ways to resolve it.
One common cause of this error is that the SQL service is stopped or did not start to begin with, meaning that it was unable to create the socket file in the first place. To find out if this is the reason you’re seeing this error, try starting the service with _systemctl_:
----
sudo systemctl start {mysqld|mariadb}
----
Then try accessing the MySQL prompt again. If you still receive the socket error, double check the location where your MySQL installation is looking for the socket file. This information can be found in the `mysqld.cnf` file:
look for the socket parameter in the [mysqld] section of this file. It will look like this:
----
[mysqld]
user = mysql
pid-file = /var/run/mysqld/mysqld.pid
socket = /var/run/mysqld/mysqld.sock
port = 3306
----
Close this file, then ensure that the mysqld.sock file exists by running an ls command on the directory where SQL expects to find it:
----
ls -a /var/run/mysqld/
----
If the socket file exists, you will see it in this command’s output:
----
mysqld.pid mysqld.sock mysqld.sock.lock
----
if the file does not exist, the reason may be that MySQL is trying to create it, but does not have adequate permissions to do so. You can ensure that the correct permissions are in place by changing the directory’s ownership to the mysql user and group:
----
sudo chown mysql:mysql /var/run/mysqld/
----
Then ensure that the mysql user has the appropriate permissions over the directory. Setting these to 775 will work in most cases:
----
sudo chmod -R 755 /var/run/mysqld/
----
Finally, restart the MySQL service so it can attempt to create the socket file again:
----
sudo systemctl restart {mysqld|mariadb}
----
Then try accessing the MySQL prompt once again. If you still encounter the socket error, there’s likely a deeper issue with your MySQL instance, in which case you should review the error log to see if it can provide any clues.
