Home >Database >Mysql Tutorial >How to solve mysql 113 error

How to solve mysql 113 error

藏色散人
藏色散人Original
2023-02-14 09:54:452709browse

Mysql 113 error solution: 1. Turn off the firewall of the remote machine, or allow the 3306 port number in the firewall; 2. Set the database to allow remote access, through the statement "grant privilegesCode on dbName.tableName to username@host identified by "password";" Just authorize the corresponding host.

How to solve mysql 113 error

The operating environment of this tutorial: centos7 system, MySQL5.7 version, Dell G3 computer.

mysql 113 error how to solve it?

113 Error mysql_mysql adding, authorizing, deleting users and connecting to the database Can't connect to MySQL server on '192.168.31.106' (113) Error troubleshooting...

centos7 below Operate mysql to add, authorize, and delete users

Add users

Log in to the database as root user and run the following command:

create user test identified by '123456789';

The user test was created above, and the password is 123456789. We can see the new user information in the mysql.user table

+------+----------------+-------------------------------------------+
| user | host | password |
+------+----------------+-------------------------------------------+
| test | % | *CC67043C7BCFF5EEA5566BD9B1F3C74FD9A5CF5D |
+------+----------------+-------------------------------------------+

Authorization

Command format: grant privilegesCode on dbName.tableName to username@host identified by "password";

MariaDB [test]> grant all privileges on test.* to 'test'@'%' identified by '123456789';
Query OK,0 rows affected (0.00sec)
MariaDB [test]>flush privileges;
Query OK,0 rows affected (0.00 sec)

The above statement gives all operating permissions of the test table to user test, and the password is 123456789. Similarly, we can view the information of mysql.user

select user,host,password, Select_priv,Insert_priv, Update_priv ,Delete_priv from user where user='test';+------+----------------+-------------------------------------------+-------------+-------------+-------------+-------------+
| user | host | password | Select_priv | Insert_priv | Update_priv | Delete_priv |
+------+----------------+-------------------------------------------+-------------+-------------+-------------+-------------+
| test | % | *CC67043C7BCFF5EEA5566BD9B1F3C74FD9A5CF5D | Y | Y | Y | Y |
+------+----------------+-------------------------------------------+-------------+-------------+-------------+-------------+
1 rows in set (0.00 sec)

You can also use the show grants command to view the authorized permissions. Information

show grants for 'test';+--------------------------------------------------------------------------------------------------------------+
| Grants for test@% |
+--------------------------------------------------------------------------------------------------------------+
| GRANT ALL PRIVILEGES ON *.* TO 'test'@'%' IDENTIFIED BY PASSWORD '*CC67043C7BCFF5EEA5566BD9B1F3C74FD9A5CF5D' |
| GRANT ALL PRIVILEGES ON `test`.* TO 'test'@'%' |
+--------------------------------------------------------------------------------------------------------------+
2 rows in set (0.00 sec)

privilegesCode indicates the type of permission granted. The following types are commonly used [1]:

all privileges: all permissions.

select: Read permission.

delete: delete permission.

update: Update permissions.

create: Create permission.

drop: Delete database and data table permissions.

dbName.tableName indicates the specific library or table to which permissions are granted. The following options are commonly used:

.: Grant permissions to all databases of this database server.

dbName.*: Grant permissions to all tables in the dbName database.

dbName.dbTable: Grant permissions to the dbTable table in database dbName.

username@host indicates the granted user and the IP address that allows the user to log in. The Host has the following types:

localhost: The user is only allowed to log in locally, not remotely.

%: Allow remote login from any machine except this machine.

192.168.52.32: A specific IP indicates that the user is only allowed to log in from a specific IP.

password specifies the login page of the user.

flush privileges means refreshing permission changes.

Change password

update mysql.user set password = password('123') where user = 'test' and host = '%';
flush privileges;

Delete user

drop user test@'%';

The drop user command will delete the user and the corresponding permissions. After executing the command, you will find the mysql.user table and mysql.db table The corresponding records have disappeared.

Summary

When we deploy the code, we need to create a user and grant permissions to operate the database. Then we can use the command:

grant privilegesCode on dbName.tableName to username@host identified by "password";

Need to pay attention What is important is that when we operate permissions, we need to select the host, which is the address that is allowed to be accessed, such as

localhost: the user is only allowed to log in locally, not remotely.

%: Allow remote login from any machine except this machine.

192.168.52.32: A specific IP indicates that the user is only allowed to log in from a specific IP.

At the same time, when everything is ready, when we access it on another machine, if the following error occurs:

# mysql -h192.168.31.106 -utest -p;
Enter password:
ERROR2003 (HY000): Can't connect to MySQL server on'192.168.31.106'(113)

Error troubleshooting

1. OK Turn off the firewall of the remote machine, or allow the 3306 port number in the firewall

2. Make sure the database allows remote access, and use the statement grant privilegesCode on dbName.tableName to username@host identified by "password"; authorize the corresponding host. That's it.

Recommended learning: "MySQL Video Tutorial"

The above is the detailed content of How to solve mysql 113 error. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn